Also: one of the features of the underlying tech stack is that the UI is actually a completely separate module than the backend API. Different github repo, everything: the site is akshuallyhttps://api.bytecode.news and the UI at the "base url" is just one layer for that API. The goal was always to have multiple interfaces, all tuned for whatever the technology supported best: see https://enigmastation.com/2014/07/09/repost-some-of-what-id-... (from my personal blog).
BCN actually has multiple UIs for it, although I've been concentrating on the content rather than the front-ends - I'm not a front-end guy, so my UIs tend to be impenetrable. The model works. If it's my implementation the other front ends will suck from a UX perspective, because I don't see the UI the same way most people do (there are reasons, they're not important, bottom line is that I avoid UI.)
What would YOU suggest for a UI? I'm very much curious, because I would LOVE for the UI to sing and I would have no idea how to make that happen.
What's your load chain? I've seen some other people (who use Tor through Brave) say that it's slow to load, and I'm curious to fix that - the front end has a cached version that should be rendering pretty aggressively without datafeed updates.
BCN actually has multiple UIs for it, although I've been concentrating on the content rather than the front-ends - I'm not a front-end guy, so my UIs tend to be impenetrable. The model works. If it's my implementation the other front ends will suck from a UX perspective, because I don't see the UI the same way most people do (there are reasons, they're not important, bottom line is that I avoid UI.)
What would YOU suggest for a UI? I'm very much curious, because I would LOVE for the UI to sing and I would have no idea how to make that happen.