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

help-circle
  • Of course there’s more to this than “corpo bad”, it’s the economic system that drives these businesses to focus on profit over the quality of the user experience–but I think that’s the core to all the “corpo bad” arguments when you really boil them down. These websites and services have become so ubiquitous for two reasons:

    The first reason, is that people tend towards simplification, if you can give them a centralized location where they can have all their needs met, they prefer it to the effort it takes to use multiple locations/services. A great example is the popularity and convenience of stores like Walmart or Costco where you can do all of your shopping in one quick go. Facebook, Reddit, Twitter, and even YouTube to a lesser degree all offer these one-stop-shop kind-of models by allowing you to connect with a vast amount of people, discuss a large number of topics, and view multiple forms of media. So, unless they have a good reason to remain diversified, people tend towards simplification.

    The second reason is also psychological in nature. These companies, (whom we will refer to as FaRT), have designed and redesigned their entire systems to drive up refresh rates, click-through rates, and otherwise increase advertising visibility. In addition to hacking the addiction mechanisms, and the desire for people to feel important, they take it even further using deception and “dark UI”. Even when you utilize many of the adblocking systems, for example, FaRT inject advertising content directly into the same stream of other user content(the best example is direct corpo sponsorship of big name YouTube content creators, but at-least that money goes directly to the creators). Plus, advertisers are getting much, much better at disguising this content so that you are less likely to skip it before seeing it.

    So it’s a two-sided coin, a major part of the problem is that “corpo bad”, and now that they’re taking it to a degree of harming the public experience for profits (which is why cable television died), it’s our responsibility to step out of our comfort zones and show them that we are willing to inconvenience ourselves a little for a better UX.




  • Here’s the biggest factor in all of Spez’s deceit, Apollo is an afterthought. 3PAs are smaller businesses, and I’m betting that he didn’t want to outright make enemies of industrial giants like Microsoft and Google (that would be incredibly stupid), so my guess is that Spez is running with the whole claim that he doesn’t want to subsidize the profits of 3PAs to avoid pissing off the people who could ruin him. However, in no unclear terms, he wants to convert his biggest API users, the ones who demand dedicated server pools, into income streams. He wants to sell our content, as his own:

    Huffman said Reddit’s back-end infrastructure includes separate server pools solely dedicated to handling the scraping that Google and Microsoft do from Reddit every day.

    “Reddit represents one of the largest data sets of just human beings talking about interesting things,” Huffman said. “We are not in the business of giving that away for free.”

    https://www.npr.org/2023/06/15/1182457366/reddit-ceo-steve-huffman-its-time-we-grow-up-and-behave-like-an-adult-company




  • For today’s pop-quiz, please derive the airspeed velocity of an unladen projectile buncat when the velocity is perpendicular to the gravitational force. I would like your answers on my desk in 15 minutes or you will be disallowed from the shrubbery room and therefore disqualified from the Knights Who Say “Ekke Ekke Ekke Ekke Ptang Zoo Boing” for the rest of the semester.


  • I think #1 is a great idea, but it would take a lot of work and would probably be a pain to phase-in and phase-out across all platforms, but I do think it’s a good idea, at least to offer as an option. While I am loathe to mention anything cryptocurrency and NFT-related, creating a simplified distributed ledger and smart contract system that would propagate through federated communities seems like an interesting idea. Alternatively, creating a way for users to specify their other usernames on other servers in a small bio in a profile page could be a possible compromise.

    Your point #2 also sounds great, but I don’t think this should be allowed between communities on defederated instances, because there’s laws in many countries that can classify the act of hosting/providing certain content to be criminal. Therefore, if say if server_a resides in country_a, and country_a allows piracy, and server_b in country_b, and country_b considers it a criminal act to propagate certain information about piracy, the server_a/piracy and server_b/piracy might have different restrictions to discuss piracy. However, a less-informed mod may attempt to federate server_a/piracy and server_b/piracy, and insodoing accidentally make the owner/host of server_a unknowingly complicit in a criminal act.

    I’m not a lawyer, and of course this is not intended to be legal advice, but I think that the effort would better be spent on implementing a solution to the decentralized identity problem, than the de-fragmentation of similar communities.

    One other nugget to consider, assuming we were to replace Reddit, and the sum of the users on the fediverse were to achieve similar numbers to Reddit’s glory days–we would definitely be scraped for AI training data. By keeping the communities fractured, that makes it far more difficult for a company to easily scrape all the information needed. While it might be trivial right now, in the ideally decentralized structure that the fediverse would take, it would take a lot more requests for a server to chase out every strand on every network.

    Perhaps in this sense, it might be wise for instances to allow specific community defederation(ie, where server_a and server_b are federated, but server_a does not allow server_b/piracy to propagate(this may already be possible, IDK)), but I do not think it would be wise to allow community to community federation.

    TL;DR: #1 is a great idea, OP, and it could be implemented in a simplified distributed ledger that propagates through federated communities, and uses a simplified smart-contract–or the problem could be solved by a compromise that allows users to specify their usernames for other instances in a small public bio. Addressing #2, this could cause legal problems in specific scenarios, rather it is more important for any instance to be able to disallow the propagation of specific communities from a federated server (if this isn’t already possible).