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

help-circle








  • I have a different argument for why Meta could kill the Fediverse. Even before they engage on Embrace Extend Extinguish strategy, the simple fact that Meta will have an extremely large user base from the start may kill financially the rest of Fediverse.

    All projects that embrace ActivityPub are not prepared to deal with the volume of data that a Meta’s facebook-like or twitter-like project would bring.

    In a best case scenario it would force the development of current Fediverse projects to focus on sustentability earlier than necessary, and the missing features would be delayed. And that alone would cause problems to the future of such projects.

    On the other hand, the smaller nodes would see the storage costs rising fast and would be at a higher risk of dying simply because they would not be able to pay.







  • How low the barrier is depends on how good is your prior knowledge. If you are a millennial that remember the internet before Facebook, it’s probably very easy to understand the gist. For older people who never got into how computers work, or younger people that only saw the internet through smartphone apps, that barrier may be higher than we feel.





  • arthur@lemmy.ziptoPrivacy@lemmy.mlWTF IS THIS?
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I am not certainly sure what point you are trying to make? Yes, this is acceptable as there is no better way to avoid cheaters on PC platform. 🤷

    I’m not sure about this one. For sure it’s the most cost-effective method to avoid cheaters, but not the “best” way.

    Using statistics on the server side could be less intrusive. Checking file integrity on every run could be an option. Honeypots that are visible only for cheaters already happened with success to detect them.

    There are possible strategies.