github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-07 02:03:55 -05:00
Code Issues 85 Packages Projects Releases 24 Wiki Activity

[GH-ISSUE #431] Notes in "privacy_security.qmd" #1423

New Issue
Closed
opened 2026-04-11 07:48:44 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-11 07:48:44 -05:00
Owner
Copy Link

Originally created by @BravoBaldo on GitHub (Sep 3, 2024).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/431

In "privacy_security.qmd",

  • (Please Note: some parts are personal opinions!)
  • "analysis for move reviews" ---> "analysis for movIe reviews"
  • "14.5.3 Fault-injection Attacks", search "skip the jmp end instruction" --> must be "skip the jmp end instruction" (This is pure nitpicking!!!)
  • "Researchers could use it to control brakes and other components" --> "An attackers could use it ...."
  • "In June, a class action lawsuit was"...which year?
  • "Some researchers demonstrate a real-life" --> "Some researchers have demonstrated a real example" ???
  • " from occurring and causing any harm" missing final dot (or missed other words!)
  • Search "multipartymultiparty" is a duplication?
  • "Optimized hardware and parallelization can HELP but not eliminate this issue." --> (suggestion) "Optimized hardware and parallelization can ALLEVIATE, but not eliminate, this issue."
  • "The random SPITS ensure" ...maybe outputs ???
  • The acronym MPC, (which I assume stands for "Multi-Party Communication"), is not explicitly defined anywhere.
  • Last paragraph before "Summary": "Additional pitfalls of synthetic data include amplified biases, LABELING DIFFICULTIES, ...." In my opinion, labeling is a trivial thing if you are the one generating the sample yourself!
Originally created by @BravoBaldo on GitHub (Sep 3, 2024). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/431 In "privacy_security.qmd", - (Please Note: some parts are personal opinions!) - - "analysis for move reviews" ---> "analysis for movIe reviews" - "14.5.3 Fault-injection Attacks", search "skip the `jmp` end instruction" --> must be "skip the `jmp end` instruction" (This is pure nitpicking!!!) - "Researchers could use it to control brakes and other components" --> "An attackers could use it ...." - "In June, a class action lawsuit was"...which year? - "Some researchers demonstrate a real-life" --> "Some researchers have demonstrated a real example" ??? - " from occurring and causing any harm" missing final dot (or missed other words!) - Search "multipartymultiparty" is a duplication? - "Optimized hardware and parallelization can HELP but not eliminate this issue." --> (suggestion) "Optimized hardware and parallelization can ALLEVIATE, but not eliminate, this issue." - "The random SPITS ensure" ...maybe outputs ??? - The acronym MPC, (which I assume stands for "Multi-Party Communication"), is not explicitly defined anywhere. - Last paragraph before "Summary": "Additional pitfalls of synthetic data include amplified biases, LABELING DIFFICULTIES, ...." In my opinion, labeling is a trivial thing if you are the one generating the sample yourself!
GiteaMirror added the area: book label 2026-04-11 07:48:44 -05:00
GiteaMirror commented 2026-04-11 07:48:45 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Sep 4, 2024):

Thank you for the feedback! Will fix.

<!-- gh-comment-id:2328056917 --> @profvjreddi commented on GitHub (Sep 4, 2024): Thank you for the feedback! Will fix.
GiteaMirror commented 2026-04-11 07:48:45 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Sep 4, 2024):

I update the labeling one to be mislabeling, cause that does happen. But the other ones are good; some of these mistakes (even across other chapters) are coming from my use of Grammarly to fix mistakes but i had automated some checking, and some clicks got messed up is what I am seeing from some of your edit suggestions. Thanks for catching all these.

<!-- gh-comment-id:2328068707 --> @profvjreddi commented on GitHub (Sep 4, 2024): I update the labeling one to be mislabeling, cause that does happen. But the other ones are good; some of these mistakes (even across other chapters) are coming from my use of Grammarly to fix mistakes but i had automated some checking, and some clicks got messed up is what I am seeing from some of your edit suggestions. Thanks for catching all these.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label area: book
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#1423
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?