spoiler

made you look

  • 0 Posts
  • 28 Comments
Joined 3 months ago
cake
Cake day: July 27th, 2024

help-circle












  • Then don’t get me started about how the www subdomain itself no longer makes sense. I get that the system was designed long before HTTP and the WWW took over the internet as basically the default, but if we had known that in advance it would’ve made sense to not try to push www in front of all website domains throughout the 90"s and early 2000’s.

    I have never understood why you can delegate a subdomain but not the root domain, I doubt it was a technical issue because they added support for it recently via SVCB records (But maybe technical concerns were actually fixed in the decades since)



  • They’re “file like” in the sense that they’re exposed as an fd, but they’re not exposed via the filesystem at all (Unlike e.g. unix sockets), and the existing API is just mapped over the sockets one (i.e. write() instead of send(), read() instead of recv()). There’s also a difference in how you create them, you open() a file, but connect() a socket, etc.

    (As an aside, it turns out Bash has its own virtual file-based wrapper around sockets, so you can do things like cat a remote port with Bash, something you can do natively in Plan 9)

    Really it just shows that “everything is a file” didn’t stand up in practice, there’s more stuff that needs special treatment than doesn’t (e.g. Interacting with TTYs also has special APIs). It makes more sense to have a better dedicated API than a generic catch-all one.




  • Existing JPEG files (which are the vast, vast majority of images currently on the web and in people’s own libraries/catalogs) can be losslessly compressed even further with zero loss of quality. This alone means that there’s benefits to adoption, if nothing else for archival and serving old stuff.

    Funny thing is, there was talk on the Chrome bug tracker of using just this ability transparently at the HTTP layer (like gzip/brotli compression), but they’re so set on pushing their AVIF format that they backed away from it.



  • The_Decryptor@aussie.zonetoMemes@sopuli.xyzYouTube now vs then
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 months ago

    You can’t do normal BitTorrent in browsers, there’s no support for plain sockets that you’d need to communicate with other peers, WebTorrent is technically a new protocol that implements the BT semantics over stuff the browsers do provide (So you can proxy between the different swarms, that’s the “hybrid” nodes in the image on the WebTorrent page)

    But it turns out it’s all a moot point, since PeerTube removed WebTorrent support anyway in favour of their own P2P system

    Edit: Ok so I misunderstood, and it seems like it’s a bit complicated. The server can (it’s disabled by default) use WebTorrent to import videos, the client still uses the WT trackers to find peers but uses a different protocol to actually share the video data.

    There’s this tool that provides the ability to automatically seed videos, but development has stalled because no up to date client will ever make use of it.

    I think the one remaining use is the “download as torrent” option, but even then that’s just using a web seed, so it’s just an alternative way to download the video.