I have proposed something of this nature to the Lemmy developers and am waiting on feedback from them.
There could be a few trusted folk out there turning their servers into S3 nodes (?) via minio or something like that, which Lemmy's pict-rs could use as storage. The main Lemmy backend process serves out the images anyway (I have no real idea why pict-rs is that separate tbh), so throwing a CDN in front of that (filtered to images and video) should be enough to get some reliability on serving images.
Of course this is only the technical stuff. The legal parts are a completely different issue altogether
There seems to be enough interested people that even if this one were to die, a "phoenix lemmynsfw" or few is almost sure to happen. Of course the issue with that would be getting all the activity back again, so it would be nice if that did not happen.
There is no way in hell a single person will be able to handle an instance of this size (and rapidly growing). Coordinating is a must if this instance (or any other like it should it die before everything gets set up properly) were to stay alive
The JS patch was deployed for a very short time (remember when the NSFW box was showing checked but wasn't? Yeah). Any further development seems to have been done on the Lemmy code itself, under different tags (not branches)
Best of luck, both to you and whatever you decide to do in the future, but also to the poor soul who will now have to maintain all this after you :p
For kickstarting I personally just dumped the relevant ones from my own stash (that were still up, I have a few more I'll need to reupload because Imgur & co) and let the community take over from there, though of the 3 communities I tried it only seems to have worked for 1, so YMMV.
It's likely a caching issue considering how random it seems to be. Do a CTRL+F5 and try again.
Looking through the (Firefox) devtools, there is only one cookie (being my login token), but a fair bit of cached images (and IndexedDB data for managing said cache), which is what I assume most of that size is.
The reason why it's easy to find communities here is because this instance is specially modified to list them without being logged in.
Your best bet would be to bug admins of instances who are explicitly OK with NSFW to pull in a patch like the one used by this instance, or tell https://lemmynsfw.com/c/nsfw411 about them as you find them.
Reddit doesn't own that content, individual posters do. They do grant Reddit a license to display it to others (in the terms of service nobody reads) but they are still the legal owners of their posts (assuming we're talking about OC)
If we leave the reposting to lemmit, people can easily opt out from it showing up on their All feeds by blocking the singular bot that does all the posts, whereas if we allow it here people would need to individually block each bot.
However, Lemmit only reposts Reddit, there is at least one bot here that reposts one of the rule34 boorus, and I'm sure other sites are to follow. Those seem to be the real issues here.
https://git.lemmynsfw.com/explore/repos
Look at the tags, not branches
Pictrs itself seems to support S3 as a backend. I think they're talking about that.
https://git.asonix.dog/asonix/pict-rs#user-content-filesystem-to-object-storage-migration
I ask because images are not copied as part of federated data. They remain on the original instance.
Technically they are. As far as I'm aware its temporary, but they are copied & cached for some time. I think it was a week by default.
Try a CTRL+F5. Could be a caching issue. Works on FF Nightly
I guess I’ll use the uncheck and recheck method until I hear its fixed
with how the patch works, sending untagged and tagging afterwards would be more reliable, as it only runs on the 'create post' page. but then i'm not sure how well this would affect the federation (it's certainly better than keeping it untagged)
Go to sleep.
don't feel like it
I think what's happening is that the new auto-NSFW patch is checking the box visually, but isn't letting Lemmy know about the box actually being checked.
Here is the code that seems to be behind it. It's setting .checked
true, but there's a change
event Lemmy registers on the checkbox, which I'm not entirely sure if it gets triggered or not.
This seems like a really roundabout way of going with this, but I'm not sure how hard it would be to do the 'proper' way. It's 4 AM and I really should be sleeping instead of lurking here.
To be fair I do have the technical knowhow to duct-tape a patch for this. I'd try my shot at getting it upstreamed but there has to be a reason why it's implemented like this. And my sleep deprived ass can't figure out why. Did they seriously just overlook something like this?
Also I can't be bothered with opening up a github acct under this name.
By Web UI it means that the graphical part of it -- where you write your prompt and hit generate -- is running inside your browser and not as a separate window or command line. Everything is kept on your own computer unless you explicitly tell it to open up remote access.