• 0 Posts
  • 14 Comments
Joined 9 months ago
cake
Cake day: January 3rd, 2024

help-circle


  • Your voice-print is worth protecting.

    There’s already retirement funds activating “my voice is my password” by default, now. (You can, and absolutely should opt-out, if yours does.) And you can’t change your voice-print if it gets leaked. (Maybe with a professional voice coach, you could…)

    Personally, I would change employers over this, if I had the option.

    I think we’re heading towards having a group of citizens with compromised voice-prints leaked to the dark web, who have a harder time day to day through no fault of their own. Like the early SSN breach sufferers, history tells us that society says “it’s a shame”, and tries to protect the next generation properly, but doesn’t recompense those hurt by the early bullshit.

    While job searching, I would also request an accomodation, and not use the voice system. It’s much easier for the employer to retain a secretary for you, than to deal with the legal hassles that will come up if they try to fire you for not using their legal-gray-area solution.

    Even granted the accommodation, I would be looking for my next job though.



  • An RSS feed is such a simple plain text file. I can’t imagine using a dedicated solution for it.

    If I needed a dedicated RSS Feed, I would be inclined to generate it with CRON job, and Jinja2 file, and about 3 lines of Python code.

    What I typically do use is an extension for my current static site generator. At the moment, that’s EleventyJS. But I’m only using that to create RSS because it’s already creating the rest of my website.






  • It gets weird fast, because before privacy controls in the Lemmy source code mean anything, we need trusted third party verification of a server’s patch level, and security controls.

    That can be done, and I think Lemmy has a shot at getting to that point, but it’ll be awhile.

    In the meantime, I suspect the Lemmy developers are hesitant to add and advertise features that you can’t be sure are actually correctly enabled on your instance.

    But yeah, let’s not let perfect be the enemy of moving toward better.

    Edit: Assuming you completely trust your instance admin, we could start adding some basic privacy to actions taken on your home instance.

    But as soon as the user starts interacting via federation, all bets are off - because the federated instance may he malicious.

    I think we might see one or more “trusted fediverse” groups emerge in the next few years, with instance admins making commitments to security controls, moderation, code of conduct, etc.

    So, in theory, the lemmy software could start implementing privacy controls that allow users to limit their visibility to whichever part of the fediverse their instance admin has marked as highly trusted.

    But even then, there’s risks from bad actors on highly trusted instances that still allow open signups.

    Anyway, I totally agree with you. It’s just a genuinely complex problem.


  • I’ve had this happen when I had too many USB devices plugged into it. It was having power underrun, and acting unresponsive while trying to compensate. I solved it with a powered USB hub.

    Edit: I’ve had pairing it with an off brand power brick cause the same problem, too. Apparently the 3 and later Pi really want better power quality regulation, and some of the cheapo bricks I had lying around - while providing the right Volts and Amps, didn’t control the variation well enough for the modern Pi computer.