• 12 Posts
  • 620 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle






  • Vote privacy can be tricky in an environment where every vote gets sent to thousands of instances and needs to be verified as legit via the ActivityPub protocol.

    Piefed does a good job of this I think. If vote privacy is enabled, they create a second account that is used only for votes. Other instances see the votes and can validate them against the vote account but it’s not tied to the actual user (except in their home server database).

    A benefit of this is that the vote account for the user is always the same, so you can still track vote manipulation, and ban the vote account if needed.




  • Dave@lemmy.nztomemes@lemmy.worldThis is a PSMA!
    link
    fedilink
    arrow-up
    15
    ·
    1 month ago

    I went M-Disc. Need a special burner and disks cost me $30NZD each or about $18USD for 100GB.

    They are write once (I fucked up two early on) but they should last 100+ years. I burnt about 1TB, and made two copies (one for offsite storage). It was not cheap.







  • It says

    As these installation methods are used for the development of Home Assistant, it will still be technically possible to update them. We still would recommend migrating to a supported method, but that’s your choice.

    And then towards the end:

    Will the developer documentation on these things remain?
    Yes, those will remain. The developer documentation for running Home Assistant’s Core Python application directly in a Python virtual environment will remain. This is how we develop. This proposal is about removing end-user documentation and support.

    How I read it is that these methods are actively used for development so will still be maintained and updated, including developer documentation because developers will continue to need to use these methods.


  • If you read the Home Assistant official announcement, it basically says all the different methods were confusing to new people so they will remove them from end user support documentation and won’t take support questions from people using these methods.

    However, outside the deprecation of 32bit OSs (which they point out a large portion are on 64bit capable hardware), they are still going to be documenting the other methods in the developer documentation.

    I honestly think this is the right move. Their time is being wasted by confusing new users, and supporting 32 bit OSs is literally preventing the development of new functionality. If you want to use a Python environment instead of docker, the developer documentation is there to support advanced users.