The Mutable Web
simulacrum.party
simulacrum.party
I touched on this in a recent post here: https://www.jamesyu.org/blog/my-journey-from-frame-maker-to-...
I empathize with the author on this, but I also appreciate that platforms have designed their frames to prioritize content. This has resulted in an explosion of creativity within the frame that we wouldn't have otherwise seen, because the platforms have allowed more people than ever to express themselves, and not just the folks who know how to hand code pages.
Homogeneity provided the consistency so that creators could focus within the frame.
Not only is most content delivered snippets devoid of styling, the lowest common denominator Internet user is just (1) the only source of growth nowadays and (2) utterly conditioned to expect everything looks like a Google SERP, so (3) everything looks like a Google SERP.
Of course, many services provide APIs, so in theory this decoupling is already possible, but the problem is that many platforms rely on advertising & promoted content for their revenue, so they need to maintain control over the front-end and therefore won't allow people to build alternative UIs.
I don't know how to solve the revenue problem. I just wish we could find a way to have UI competition.
Basically protocols are what you want, but they don't make it easy enough to be shitty, so they're dying until we outlaw (yes, with actual laws) being shitty. Which may never happen.
A new Reddit
- but with the Wikipedia funding model
- with Snapchat's ephemerality
- an amazing API and all open source code
- all submissions cc-by-sa licensed
Since profit isn't a motive, it would encourage the proliferation of new frontends and clients. As well as really cool mashups (haven't heard that term in awhile - probably due to increasingly closed ecosystems.)
Without having to save user generated content you can save tremendously on servers. You don't have to scale other than enough to handle the fire hose. Everything could reside in memory. Just Redis and Rust.
The content gets scrubbed after a week. No sharded storage is necessary. But due to the license, others can persist content they like.
There's next to zero value in looking up old posts. I don't know why this hasn't been done.
I genuinely cannot tell if this is satire.
A lot of subreddits are bastions of information for sometimes very niche topics. I frequently run into reddit posts that are 6+ months old but still relevant to what I'm seeking knowledge about. Outside of the programming sphere, posts from years ago generally still hold value.
Saving posts would imply that I knew what Future Me wants to look up, or praying that someone was interested and cached it. Writeups/insightful discussion would be completely wasted, and I would have to find -another- website for potential caches of things relevant to what I'm looking for.
It would be like IRC where people delve into the same topics and arguments ad infinitum.
If I wanted an ephemeral social network (like snapchat) I would use an ephemeral social network, like snapchat.
While I don't doubt that's the case, it's incredibly difficult to get at old content due to Reddit's horrible search experience. I never look up anything old there.
site:reddit.com or site:reddit.com/r/nichesubreddit <query> is how I actually find things. Lately I actually have begun to cache important things locally, but I wouldn't assume anyone else is doing that for the particular topics or niche subsection of a topic that I'm looking up.
This is what a * chan does. N pages of content max; anything more, and the oldest thread will be "dropped off" the site.
Combined with anonymous-by-default posting, it works fairly well.
>There's next to zero value in looking up old posts. I don't know why this hasn't been done.
This is not really true; there's tons of good information that gets lost. On most * chans, this was recovered by screenshotting the thread and sharing the image around; today there are auto-archiving sites for the larger * chans, and people just link to that. But the culture still prefers sharing (edited, MS Paint) screenshots around.
Or just get rid of the false binary between centralized control/data (silo model) and decentralized resource-consuming p2p apps (blockchain model).
Federation models provide a sane alternative and have proven scalable/maintainable in the long run (see email/xmpp).
For federated web protocols, see ActivityPub, Linked Data or WebSub. Outside the web, there's the old and wise XMPP.
On the web specifically, micropub and activitypub were designed with interoperability in mind (for the microformats and activitystreams formats respectively).
We need to use more of these (or other) standard protocols in every backend project we make: our blogs, agendas..
In the uBlock Origin settings the second tab ('Filter lists') contains a list of filter files, some of which are enabled by default and some of which aren't. I checked the boxes to enable some additional filter lists - everything in the 'Built-in' category except Experimental, and everything in the 'Annoyances' category.
It's been a while since I enabled these so I don't remember what exactly all of them do, but I rarely see a cookie banner or a modal popup subscribe dialog, I think due to these extra filters. These extra filters also include social blocking ones, which delete like/share buttons such as those from Facebook and Twitter (these buttons are useless to me). I think one of the rules in these extra filter lists is matching on your images, which are on the path '/assets/images/tmw-twitter-xxx.png.' The uBO logger shows the rule being matched as '/images/twitter-' and that it is present in Fanboy's Annoyances and Social Blocking lists.
Of course there's nothing wrong with the site, the images here are just a casualty of a blocking rule. But it was an interesting 'bug' to find.
I don't completely hate Twitter's redesign-- it does include a night mode and different highlight colors. I feel like-- as a professional installation art designer, web designer, and an education in architecture-- I can spot the same obvious pitfalls of the re-design you call out: mainly, phat text and a bulky sidebar. However, it's clear you have a stronger-than-most design sense, and are sensitive to these issues.
I wonder how the everyday user-- the consumer that uses (and does not make or own) a platform-- feels about these features? How about someone who isn't adept at web design? Who can't read small text or icons?
For me it's not the design, per se. It's that they changed a couple of things in the UX department that really rile me up.
1- The old design pulled for updates in the background, and the browser tab notified me that there were new tweets in my timeline (which is not a notification for every tweet, it's just letting me know there are new tweets). This doesn't work anymore. I have to open the tab and then it loads new tweets.
2- Every damn day, I have to reset the ordering of tweets to chronological. If I set an opiton I expect it to stay put.
Disclosure: Wrote that doc