Comment by plastic3169
1 year ago
Website is great if you want to publish a document. Collect information in one place. Most of the daily stuff is just human communication better served by forums, tweets, images, news, e-mails, chats, tik toks etc. These natively work better in apps or app like sites where the information comes and goes gets lost or never even gets discovered. If we worry about the information siloing up we should build communication web thats not owned by big corps. It’s like the open source side stopped building the protocol after web 1.0 was finished and left all the emergent use cases for start ups to solve.
I feel this, but likely because I am a software engineer and PC tinkerer from the '90's.
Everything that get's created, gets commercialized and swallowed up by whatever product roadmap that commercial entity has. The soul of the internet, from my point of view, can be simply stated as "connection."
Where do we go when we want to connect further and wider than our feet can take us? The internet. What is the point of connection? To share who we are through a wide variety of means: games, text, images, music, voice, etc.
The internet as a protocol supports that endeavor, but the layers that were built on top of the internet started swallowing up human attention. Now there are a few large leaders who have built application layers on top of the web, and that's where people go for their connection. This very website is one of them.
Recent developments with ActivityPub and mastodon are promising. Personally, I'd just like to find my way back to a universal protocol for connection. At the root of it, there's a need for infrastructure which will always cost money. I think that's the main hurdle that needs overcoming.
> It’s like the open source side stopped building the protocol after web 1.0 was finished and left all the emergent use cases for start ups to solve.
Interesting take
I'm not sure it's true exactly - OSS had email as one type of messaging, and IRC as another. The problem is that email lacks instant-ness (and for a long time you couldn't send larger files as attachments), and IRC lacks, or lacked, rich functionality.
Messaging seems to just require more hardware, so the significance of whether the software is OSS or not is reduced.
I'd say IRC is a good example of one of the flaws of FOSS culture - the tendency to get cemented on the first working minimum viable solution, but then become too ossified to ever improve on it. IRC was great for its time, but it doesn't have remotely the minimum set of features the average person expected of a messenger solution 10 years ago. After the initial success of FOSS in chat protocols, almost all of the improvements came from commercial software, and it was too difficult to coordinate introduction of new features across all the implementations
And a lot of this is not even technical, but the cultural issue of scorning anyone asking for those features and claiming those use cases are just for teenagers. Real men just use plain ASCII and no multimedia apparently. Only after its lunch was soundly eaten did we finally get IRCv3, way too late, and still with little support. The reason a lot of younger developers are using Slack and Discord isn't because they're stupid kids, but because their requirements aren't met otherwise, and they're not going to constrain themselves to 90s tech out of stubbornness (to be clear I'm not accusing you of that attitude! I'm commenting on others I've seen many times over the years)
2 replies →