• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle

  • Sometimes the identity of the messenger is important.

    Twitter was super easy to set up with the API to periodically tweet the output of some automated script: a weather forecast, a public safety alert, an air quality alert, a traffic advisory, a sports score, a news headline, etc.

    These are the types of messages that you’d want to subscribe to the actual identity, and maybe even be able to forward to others (aka retweeting) without compromising the identity verification inherent in the system.

    Twitter was an important service, and that’s why there are so many contenders trying to replace at least part of the experience.







  • I think that it’s foolish to concentrate people and activity there even further, it defeats the point of a federation.

    It defeats some of the points of federation, but there are still a lot of reasons why federation is still worth doing even if there’s essentially one dominant provider. Not least of which is that sometimes the dominant provider does get displaced over time. We’ve seen it happen with email a few times, where the dominant provider loses market share to upstarts, one of whom becomes the new dominant provider in some specific use case (enterprise vs consumer, mobile vs desktop vs automation/scripting, differences by nation or language), and where the federation between those still allows the systems to communicate with each other.

    Applied to Lemmy/kbin/mbin and other forum-like social link aggregators, I could see LW being dominant in the English-speaking, American side of things, but with robust options outside of English language or communities physically located outside of North America. And we’ll all still be able to interact.






  • I don’t think the First Amendment would ever require the government to host private speech. The rule is basically that if you host private speech, you can’t discriminate by viewpoint (and you’re limited in your ability to discriminate by content). Even so, you can always regulate time, place, and manner in a content-neutral way.

    The easiest way to do it is to simply do one of the suggestions of the linked article, and only permit government users and government servers to federate inbound, so that the government hosted servers never have to host anything private, while still fulfilling the general purpose of publishing public government communications, for everyone else to host and republish on their own servers if they so choose.


  • In 2003, there were very few websites where what you saw depended on your login information. For the most part, the entire web was a bunch of stateless pages where what you saw at a URL was what I saw at the same URL. There was no real opportunity for interaction with sites in the browser (anything like that required a browser plugin to run java applets or flash/shockwave content).

    RSS was such a game changer in that it really did change the way people consumed content. I could load a blog and it would only show me the posts I hadn’t already read, instead of naively showing me the whole thing. Suddenly there were states, and things could be marked as read or unread.

    And when someone realized how to combine RSS with actual audio or video media, that was the first real semblance of “on demand” content where anyone could press play on current, timely content at their own schedule. DVRs had basically just been invented, and cable on demand content wasn’t widespread yet. YouTube didn’t exist, and the best place on the internet to watch a trailer for an upcoming movie was apple.com, where they used movie trailers to try to persuade people to download QuickTime to play those videos.

    So yeah, automating a download to your computer to automate pushing content to your iPod was a huge step forward, and basically sold itself.