I was just thinking. #fediverse really needs a kind of URL scheme which encodes both the origin URL and the fedi "platform", so fedi clients and browsers (perhaps with extensions) can reinterpret the URL and redirect the user to their own instance. This would go a long way to making federated services in the browser feel like one "app".
Perhaps simply adding ?fediapp=microblog or ?fediapp=threadiverse or ?fediapp=videos to the end might suffice, even though it's a bit ugly in the URL bar.
Or perhaps domains can expose this with a TXT record..? Hmm.
Peertube is so cool. I'm watching a recent video from a popular channel and just noticed I uploaded more data to other peers while watching the video than I downloaded from the server. It's a clever and completely frictionless implementation which alleviates some of the load (and cost!) from servers hosting videos.
It is funny how some bands sound somehow way better live than recorded. And some bands sound terrible live. I think it has a lot to do with the energy they project.
Computer graphics person. Currently work at NVIDIA. Opinions my own."Contains at least 40% post-consumer recycled content.""HIGH BIAS - IEC TYPE II - EQ 70us"Posts auto-delete eventually maybe