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

help-circle

  • From my PoV it’s probably many of these projects are effectively public good spaces. Hosting a code repository has become less of an esoteric thing and turning into a public good benefit (like a physical library but virtual for code). Spaces like Reddit and Twitter are todays analogous of a public discussion forum in a park or at a bar.

    Internet tools have become so ubiquitous they are critical to serve public needs and public benefits. However these internet spaces are increasingly commercialized and privatized, which runs against them being valuable public goods (see the difference between Wikipedia, run primarily for public benefit, and Wikia/Fandom).


  • Yep lemmy.world is live (stress) testing in production. It has its benefits, like when a set of patches were committed to vastly improve performance that was a big problem on a huge instance like lemmy.world but not on the smaller ones, and its downsides with all the random issues that pop up which happen when testing live in production.




  • Yep since the first party app’s primary goal is to generate revenue (over actually providing a good user experience), it’s packed full of everything to achieve revenue generation:

    • Ads
    • Tons of tracking to figure out how long you viewed something, what you clicked on, and so on to build an advertising profile that can be sold
    • Obtrusive Ads
    • Lots of suggested/recommended stuff to get you to keep your eyeballs on the app longer
    • Ads masquerading as real submissions
    • Paid promotions

    Third party apps don’t have revenue generation as their sole highest priority (if at all), so naturally they strip out all of that stuff which makes for a terrible user experience.


  • One of the great things about lemmy.world’s insane user count growth is actual live stress testing of Lemmy software. Instead of having an open question of how Lemmy might scale with large instances, there’s now real world production systems providing that opportunity.

    The technical issues will pass, but the notion that merely spreading out the load will alleviate them is probably just treating the symptom than the cause.

    I suppose from my PoV I see this as very much live testing in production and have adjusted my expectations around that instead of anticipating a wholly seamless experience.


  • Yep.

    So I have one primary account on Lemmy.world and then have additional accounts localized to those instances.

    For the time being things are a bit of a hassle because there’s no good way to migrate from one instance to another and bring your data with you, and the underlying lemmy software is still in development.

    Effectively we’re doing this in production!


  • Yea unfortunately the nature of Federation means that instances (servers) are dissociated from each other but nonetheless communicate with each other via a standardized protocol. Consequently, there is nothing stopping one instance from saying they want to stop communicating with another instance

    In some situations that makes sense. For example, if you are running an instance and don’t want to get people/content from another instance that posts incredibly hateful messages, you can choose to defederate from that instance.

    In other situations it creates complications. For example, if you are on a somewhat popular instance (like Lemmy.world) but then get defederated from an instance you want to participate in (like Beehaw.org), even if the defederation came from justifiable reasons, you will need a Beehaw account in order to view that content as you won’t be able to access new content from Beehaw.org using your Lemmy.world account.

    For the most part, in pragmatic terms what this really means is if one wants to participate in the most active instances, they’ll probably want an account on an instance that federates with the biggest instances.