Embed Notice

@sun@shitposter.world @susie@blob.cat @adiz@soc0.outrnat.nl That's not the point, though. You can't possibly "win" against the web if your objective is "better features" because anything is already possible on the web. You have top choose a different playing field, and I see the best chance in a protocol that's more lightweight and less flexible than HTTP (to hopefully avoid the kind of invasive tracking and anti-patterns we have here), but focuses on providing features to get sites up and running with little effort. A menu system like I described above is one such thing. But if we think further, what about a set of higher level components that mirror patterns we encounter on the web pretty often? Instead of a dumb image element, we could have an image list component which can be displayed as a dumb list of links by less capable browsers, and as a proper grid with thumbnails and captions by more powerful browsers? How about a lightbox component, something which to this day requires JavaScript on the web?
Trade flexibility with more "bang for the buck". That's the only way I can see a protocol that's supposed to be an alternative to the web gaining traction.