Hell yeah.
Most clients use an API connection which is specific to Lemmy. This is extra work to make scrapers speak that language so no scraper does.
For the moment, a scraper trying to hit any API endpoint would just get a simple malformed request error. With any luck, it stays this way so we don't have to protect API directly.
Welcome to the gathering! Beverages to the left, snacks toward the right. Please mind the cat, she likes getting under feet as a trap for demanding treats.
Ahoy! I've wrangled a few more IP ranges to contain the Tencent monsters into their Iocaine cages.
Knocking on the proverbial wood here, but we've leveled out a bit for about 20 minutes and I think we're back to normal. I'll be keeping eye for a bit just in case.
Heh, I stole it from the old days of Internet yore. Take, and enjoy.
.... Can I sign up for your newsletter?
Expand into gigantic cruisers. Make repair a mission? Have to start cutting into derelict, including alien, remove damage, bodge, transplant...
Get em going enough to find the next rig... Rogue like? Refit discovered, take over, find the next, fix up for trade, cut down for scrap etc.
I'm all about options in this arena. Ship breaker is ripe with good options here.
I appreciate that the anarchists are canonically the fire. Warms my little heart.
There's flags set in the torrent tracker that might be getting in the way here in combination with the port issue.
There might be a seed, but he can't forward ports.
The data getting updated from "last seen" is the tracker telling your client a check in happened from a seeder I believe.
Some trackers also won't play nice and tell the seeder about you properly if your client has a history of leeching perhaps. Enforcement of ratio etc.
You could try another client perhaps, but if multiple behave the same then you are not going to get anywhere. Perhaps try getting a temporary vps to torrent into and then pull from there. Seed boxes can solve many issues, just be mindful of cost over time.
Jesus giving trump some back shots in this pic...
Hello!
More recently, when attempting to share some images to Element (chat client), I see the following:
I suspect this is file specific or mimetype, as it's consistent on a given image but doesn't seem to affect most images.
A source of an example image is https://lemmy.dbzer0.com/post/42991557 ...
In these cases, saving the same image then attaching it separately inside the chat client works normally.
Please let me know if I can help diagnose etc.
Happy to help. Arr!