home.social

#onionservice — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #onionservice, aggregated by home.social.

  1. librarypunk.gay/e/160-sciopnet

    >And this is exactly why Linux distributions have been distributing ISOs using torrents for years. Aside from the sort of piracy thing, that's the other thing that BitTorrent gets used a lot for, and it means that the small organizations throwing up their own Linux distro can distribute it without it completely crashing their tiny servers.

    You're not wrong :P Pic related. It annoys me that #tails @tails recently moved away from having torrents as a form of downloading.

    >Yeah, it makes me, think about, and something I've thought about before but haven't really explored is you know how when you go on Archive.org and there's a file, and one of your options is just to download a torrent. Why don't we do that for institutional repositories and data repositories?

    That's one of my favourite parts of the Internet Archive :D

    >Because those are starting to get big. I mean, I know one of the reasons is because, like, we use proprietary software for our institutional repository and Clarabate and Elsevier don't want to support that.

    Elsevier, the bane of my academic existence.

    -----

    Also, vis-a-vis webseeds... what's stopping a Tor onion service from being the HTTP(S) endpoint? Those are pretty damn hard to bring down (from a legal standpoint). I'd assume the main limitation is that BitTorrent clients don't speak "onion service," but that's a fixable problem. Hell, what's stopping the trackers themselves from being onion services?

    #BitTorrent #SciOp #Tor #OnionService

  2. librarypunk.gay/e/160-sciopnet

    >And this is exactly why Linux distributions have been distributing ISOs using torrents for years. Aside from the sort of piracy thing, that's the other thing that BitTorrent gets used a lot for, and it means that the small organizations throwing up their own Linux distro can distribute it without it completely crashing their tiny servers.

    You're not wrong :P Pic related. It annoys me that #tails @tails recently moved away from having torrents as a form of downloading.

    >Yeah, it makes me, think about, and something I've thought about before but haven't really explored is you know how when you go on Archive.org and there's a file, and one of your options is just to download a torrent. Why don't we do that for institutional repositories and data repositories?

    That's one of my favourite parts of the Internet Archive :D

    >Because those are starting to get big. I mean, I know one of the reasons is because, like, we use proprietary software for our institutional repository and Clarabate and Elsevier don't want to support that.

    Elsevier, the bane of my academic existence.

    -----

    Also, vis-a-vis webseeds... what's stopping a Tor onion service from being the HTTP(S) endpoint? Those are pretty damn hard to bring down (from a legal standpoint). I'd assume the main limitation is that BitTorrent clients don't speak "onion service," but that's a fixable problem. Hell, what's stopping the trackers themselves from being onion services?

    #BitTorrent #SciOp #Tor #OnionService

  3. librarypunk.gay/e/160-sciopnet

    >And this is exactly why Linux distributions have been distributing ISOs using torrents for years. Aside from the sort of piracy thing, that's the other thing that BitTorrent gets used a lot for, and it means that the small organizations throwing up their own Linux distro can distribute it without it completely crashing their tiny servers.

    You're not wrong :P Pic related. It annoys me that #tails @tails recently moved away from having torrents as a form of downloading.

    >Yeah, it makes me, think about, and something I've thought about before but haven't really explored is you know how when you go on Archive.org and there's a file, and one of your options is just to download a torrent. Why don't we do that for institutional repositories and data repositories?

    That's one of my favourite parts of the Internet Archive :D

    >Because those are starting to get big. I mean, I know one of the reasons is because, like, we use proprietary software for our institutional repository and Clarabate and Elsevier don't want to support that.

    Elsevier, the bane of my academic existence.

    -----

    Also, vis-a-vis webseeds... what's stopping a Tor onion service from being the HTTP(S) endpoint? Those are pretty damn hard to bring down (from a legal standpoint). I'd assume the main limitation is that BitTorrent clients don't speak "onion service," but that's a fixable problem. Hell, what's stopping the trackers themselves from being onion services?

    #BitTorrent #SciOp #Tor #OnionService

  4. librarypunk.gay/e/160-sciopnet

    >And this is exactly why Linux distributions have been distributing ISOs using torrents for years. Aside from the sort of piracy thing, that's the other thing that BitTorrent gets used a lot for, and it means that the small organizations throwing up their own Linux distro can distribute it without it completely crashing their tiny servers.

    You're not wrong :P Pic related. It annoys me that #tails @tails recently moved away from having torrents as a form of downloading.

    >Yeah, it makes me, think about, and something I've thought about before but haven't really explored is you know how when you go on Archive.org and there's a file, and one of your options is just to download a torrent. Why don't we do that for institutional repositories and data repositories?

    That's one of my favourite parts of the Internet Archive :D

    >Because those are starting to get big. I mean, I know one of the reasons is because, like, we use proprietary software for our institutional repository and Clarabate and Elsevier don't want to support that.

    Elsevier, the bane of my academic existence.

    -----

    Also, vis-a-vis webseeds... what's stopping a Tor onion service from being the HTTP(S) endpoint? Those are pretty damn hard to bring down (from a legal standpoint). I'd assume the main limitation is that BitTorrent clients don't speak "onion service," but that's a fixable problem. Hell, what's stopping the trackers themselves from being onion services?

    #BitTorrent #SciOp #Tor #OnionService

  5. librarypunk.gay/e/160-sciopnet

    >And this is exactly why Linux distributions have been distributing ISOs using torrents for years. Aside from the sort of piracy thing, that's the other thing that BitTorrent gets used a lot for, and it means that the small organizations throwing up their own Linux distro can distribute it without it completely crashing their tiny servers.

    You're not wrong :P Pic related. It annoys me that #tails @tails recently moved away from having torrents as a form of downloading.

    >Yeah, it makes me, think about, and something I've thought about before but haven't really explored is you know how when you go on Archive.org and there's a file, and one of your options is just to download a torrent. Why don't we do that for institutional repositories and data repositories?

    That's one of my favourite parts of the Internet Archive :D

    >Because those are starting to get big. I mean, I know one of the reasons is because, like, we use proprietary software for our institutional repository and Clarabate and Elsevier don't want to support that.

    Elsevier, the bane of my academic existence.

    -----

    Also, vis-a-vis webseeds... what's stopping a Tor onion service from being the HTTP(S) endpoint? Those are pretty damn hard to bring down (from a legal standpoint). I'd assume the main limitation is that BitTorrent clients don't speak "onion service," but that's a fixable problem. Hell, what's stopping the trackers themselves from being onion services?

    #BitTorrent #SciOp #Tor #OnionService

  6. I really like to do #devlogs, so here is one:
    I implemented a lot of things in my blog the last couple of days.
    From generating an #rssfeed, listing my #github projects in a #serverside fetched view, to the Onion-Location header used by #brave to tell users that there's an #onionservice available. I've also #dockerized it. It looks like it's not gonna take too much time until i can finally publish it.