@mike805 @jeffcliff @brewsterkahle I agree.

For now, there's #BiglyBT which does that #I2P bridging, but that's only one and not one that is all that popular.

There is work being done in adding I2P support to #libtorrent (https://github.com/arvidn/libtorrent/tree/master) so eventually it will be much simpler for clients to enable it.

Making wrapping for the lib in some sane language is on my "eventually todo" list.

#Torrent #Torrents

@ophiocephalic @utzer @esther #Peertube doesn't lead to seeding while you're not watching the video/having the tab open.

For that, you need conventional #torrent clients. Incidentally, #libtorrent has added #webtorrent support since a little while (enabling clients using it for protocol support to also support webtorrent), though last I checked it solely is available through the C++ bindings which kinda sucks.

@ignaloidas @alfredohno For shorter stuff it also depends on the video type a lot.

Popular musician like #MBR? Guaranteed seeding. Random plumbing repair video? Not so guaranteed.

And yeah, for longer content that also happens to be either very popular or interest-specific seeding would also make a difference.

This is one reason I'm glad #libtorrent has support for #WebTorrent, for all that its binding availability is atrocious outside of C++, as classic clients will be able to cooperate.

there is definitely something leaky going on with #libtorrent or #qBittorrent resulting in tcpip.sys turning a non-paged pool into a non-paged waterworld. could be #windows11 specific 🤔

Latest work on #Libtorrent has repaired/improved support for #i2p, which might promise more broad support for #torrents-through-i2p among FLOSS torrent clients, many of which are built upon libtorrent. Great news for privacy and guerilla archivists. :)
https://github.com/arvidn/libtorrent/pull/7356

Latest work on #Libtorrent has repaired/improved support for #i2p, which might promise more broad support for #torrents-through-i2p among FLOSS torrent clients, many of which are built upon libtorrent. Great news for privacy and guerilla archivists. :)

Oh now. #libtorrent has added support for #I2P (or at least is actively working on it)?

That's interesting. I'm not terribly fond of #CPP or #C for complex networked software, but with adequate containment it may still be usable for #WebTorrent over #I2P.

And then #Peertube.

Not sure if browsers could be fixed up to participate too though.

Wrote a script to help out #peertube instances with bandwidth. It's just a webtorrent seeder and will reseed the trending, most liked and most watched videos. Just run it on your VPS to help out your favorite instance :)

https://gitlab.com/NamingThingsIsHard/media_tools/peertube-reseed

Made possible by #libtorrent and #docker

If you use @tilvids you might see 2-3 seeds on some videos.

#fediverse #community #softwaredevelopment #script

Writing a #peertube mirror/seed script, but I can't find working #webtorrent lib. The one from npm doesn't work neither does #libtorrent 😢

Any suggestions? I'd like to just contribute to peertube's bandwidth with my VPS...

Why is it that every project I start has to have a buggy dependency :jeb:

Wrote a #peertube mirror script based on #webtorrent in JS --> it uses a nested chrome/ium and throws errors.
OK, I switch to #libtorrent --> webtorrents don't work despite being implemented >1 year ago.

No wonder people turn to farming 😅

#rasLeBol #sigh #onlyWednesday

#μTP (Micro Transport Protocol) aka. #LEDBAT (Low Extra Delay Background Transport) est implémenté dans plusieurs clients #BitTorrent (#Transmission, #KTorrent, #Vuze, #qBittorrent, #Tixati, #libtorrent): https://en.wikipedia.org/wiki/Micro_Transport_Protocol#Development

Avec #Transmission je ne sais pas par contre si #μTP est activé par défaut dans toutes les distribs, car sous #NixOS / #Linux cela m'a demandé de changer des #sysctl:
https://github.com/NixOS/nixpkgs/blob/7728136201023022493e85e790ccc719516aab3c/nixos/modules/services/torrent/transmission.nix#L331-L338
@bortzmeyer