• 0 Posts
  • 337 Comments
Joined 5 months ago
cake
Cake day: February 18th, 2024

help-circle



  • One more point: a well structured law would likely lower the administrative burden on affected parties as well.

    Service providers are asking because they genuinely need to know, and because medical information is pretty much the only area where there are comprehensive regulations on data protection. They could absolutely be held responsible for the negligence of allowing a known infected system to infect them. A known compromised system is known to be compromised until you’ve fully evaluated the attack vector, the scope of access, and taken steps to prevent that attack from happening again.

    But because there isn’t a legally standardized mechanism to report security issues, vendors are rolling their own. Many of them would be perfectly satisfied accepting an official, standard, form, especially is there was some language that made it clear that acceptance of the form for reports was enough of a “best practice” to limit their liability if the system infected them after the fact.







  • The letters aren’t required by any law

    They should be.

    If you touch any personal information in any way (let alone medical), touching any known compromised system without very clear documentation of how the compromise happened, how it was resolved, and very clear process changes to make sure it doesn’t happen again should be a massive fine per user you service, plus treble actual damages. It’s gross negligence.

    Having clear documentation of an attack isn’t red tape. It’s the absolute bare minimum.



  • Both.

    There are absolutely a meaningful number of people who are strongly opposed to profanity, and are not OK with their phone correcting to it, a much larger number of people who only wish to use profanity in certain contexts, and specific profanities (slurs) that absolutely can do real damage with a single use.

    They don’t correct away from profanity, but they don’t correct to it either. That’s a reasonable stance. The reason it doesn’t work well with the swipe keyboards is because they’re using the “correct” feature every time without biasing to the manual input, because that’s the only to get decent results out of a bad input method like swipe.


  • The issue is that accidental profanity (by allowing the board to correct to that language) does significant harm to their reputation and will genuinely make some meaningful portion of their userbase not use them. Regular touch screen keyboards already use invisible prediction magic to make the typing experience better, and swipe leans harder than that into their text prediction.

    It’s not as easy as you’d think to train two models to both correct to profanity and completely exclude profanity.