• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle


  • Totally agreed, but there are pros and cons.

    File - harder to steal but once stolen hacker can bruteforce it as much as it wants. Web service - with proper rate limits (and additional IP whitelist so you can only sync on VPN/local network) - its harder to bruteforce. (But yes, you (sometimes) have also full copy locally in the local client, but …)

    If it was only for me I probably would also go with KeePass as you will not update the same db at the same time, but with with multiple users it’s getting unmanageable.

    I just got triggered as those CVEs are not that bad due to the nature that the app encrypts stuff on the client side so web server is more like shared file storage, while your answer suggested to switch to a solution that doesn’t work for a lot of people (as we already tried that).





  • Over all I upvote posts if its something I would like to know about.

    In this case its good to know that there was some limit issue that (as on the page say) is already resolved.

    If it was intentionally done or not we will never know, but its good to know if it would happen again that there is some limit.

    I upvote because:

    • even if it was some wrongly implemented limit in this case, the shadow banning/hidding posts (or like in this case blocking follow) will happen in the future on all large platforms, it’s human nature to abuse it if you can get away with it
    • I dont like big central platforms, I rather would like to have a transparent/open platform but I know it will never happen as servers costs money and people like “free” and convenient stuff so platforma will keep monetizing people activity
    • if it could be even slightly true I rather have as many (affected) people know about it that there was an issue with follow and now it is resolved so they can retry to follow