If my fingers prune I’m going to die or something

Thanks for maintaning this fork, this was the last missing thing on lemmy for me

same, I feel lucky to have such an uncommon surname because I easily got the domain lol. there was a short version with the last two letters as the TLD but that was already taken sadly

? This post is a month old now

It seems to work, but it keeps throwing pictrs related errors, so it’s not really built for it

It barely works on my old version of lemmy, probably fixed now then. It would be nice if there was a was to turn that off and only use pictrs only for locally uploaded images. Since I’m the only person here caching isn’t too important.
I wonder if I could shut pictrs down and only use an external image hosting for images?

Lemmy sometimes caches remote content in pict-rs. It’s a bit broken so you usually don’t see it, but it does do it occasional

Related, What about a personal instance only I use? I can choose what communities I want but I can’t control what is posted on those communities. Someone could post something illegal to a beehaw community (and have) and the mods remove it, but does the deletion of images and posts federate? In know matrix keeps copies of every deleted file in a room on all homeservers, what about lemmy?

I have done some testing and I found a few reasons I’m having issues with webtorrent:

• The only reason they where working at all is because they were downloading from the HTTP URL in the torrent file, P2P was not working at all.

• To download the webtorrent from the blender instance I need to have the video watched in my browser to peer with the webtorrent client, the instance peers don’t work on non-peertube webtorrent clients.

• The reason instant.io was broken is my adblocker was blocking the tracker.

• The tracker in my peertube instance is broken.

EDIT:
I was a bit wrong here, there are two different formats in peertube: webtorrent and HLS. I was getting confused why the video on my instance (HLS) and the one on the blender one (webtorrent) was behaving differently with webtorrent clients. They are completely different formats so that makes sense now.

Webtorrent seems to have some issues with peer discovery. I’ve tried the instant.io site they have linked on webtorrent.io and I can’t get it to download or share anything, the desktop client managed to download a torrent from my peertube instance over normal BitTorrent but I can’t share it over webtorrent. I downloaded a video from my peertube instance using btorrent.xyz over webtorrent but I can’t seed new files because the peers don’t find each other. when I use a webtorrent with a tracker (like peertube) it works fine but how were sites like instant.io supposed to discover peers without trackers? I don’t think DHT exists for webtorrent yet.

You can manually seed videos on instances using redundancy but I was thinking automatic redundancy for watched videos might be a good idea, I guess you can do automatic redundancy for entire instances but that would take up a lot of storage space.

One of the nice thing with BitTorrent is the high reliability so I assumed that was what peertube was trying to do, I guess the idea is not to provide data redundancy but to split load instead?

why? if 5 instances are seeding the video, clients should be able to download from all 5 instances and spread the bandwidth usage right?

Why not also use the instance to re-seed? it could keep seeding after the visitor closed the video.

Would it not make more sense if your instance downloaded and redistributed the torrent? then you could keep seeding after the tab closed. it also wouldn’t leak your IP then.
What about peer discovery? I opened that webtorrent website in two browsers and they didn’t peer, is that demo real?

At some point the chess board is going to stop looking like a chess board. I think this will be the comment that does it.

This is wrong, I use IPTables but the device is absolutely not dedicated lol.

I just grep’d the nginx access log for the lemmy.world IP address and looked at the access times. you can see if it’s timing out is the response code is 400. sadly ~57% of the requests are currently timing out today. it seems to work for a bit then time out for about 10 minutes, at least there is some coming through now, before the requests had stopped completely.

lemmy.ml is also back in my logs. yay
lemmy.ml is almost perfect on the timeouts, so they must have managed to fix it.

It’s only been a few minutes but I’m seeing non timing out federation in my nginx access log. Hopefully it keeps working.
Also at least on my instance, lemmy.ml has completely broken, I’m not getting anything from it at all anymore. it dropped out at 13:52:22 and besides a couple few messages it’s been silence since then. It seems to be working on lemmy.world so I’m not sure what’s causing that.

Download ML thing.
make new venv.
pip install -r requirements.txt.
pip can’t find the right versions.
pip install --update pip.
pip still can’t find the right versions.
install conda.
conda breaks for some reason.
fix conda.
install with conda.
pytorch won’t compile with CUDA support.
install 2,000,000GB of nvidia crap from conda.
pytorch still won’t compile.
install older version of gcc with conda.
pytorch still won’t compile.
reinstall the entire operating system with debian 11.
apt can’t find shitlib-1.
install shitlib-2.
it’s not compatible with shitlib-1.
compile it from source.
automake breaks.
install debian 10.
It actually works.
“Join our discord to get the model”.
give up.

this issue is also causing lemmy.world to fail to federate with this instace, see this post on lemmy.world that doesn’t appear on this instance

working here, issue is with lemmy.world not me. I guess you can keep on !waveing over here then