___

joined 2 years ago
MODERATOR OF
[–] ___ 6 points 2 years ago

I have proposed something of this nature to the Lemmy developers and am waiting on feedback from them.

[–] ___ 3 points 2 years ago

but it might even be possible to intercept images to check that this exists in the meta data before Lemmy wipes it....

This would be impossible without directly modifying Lemmy itself.

[–] ___ 3 points 2 years ago

As far as I'm aware yay will still be paying the bills for the foreseeable future, so I doubt that's the case.

[–] ___ 1 points 2 years ago* (last edited 2 years ago)

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

[–] ___ 3 points 2 years ago

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.

[–] ___ 1 points 2 years ago

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

[–] ___ 2 points 2 years ago (1 children)

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)

[–] ___ 6 points 2 years ago

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

29
submitted 2 years ago by ___ to c/orgasm
26
submitted 2 years ago by ___ to c/orgasm
24
submitted 2 years ago by ___ to c/orgasm
21
submitted 2 years ago by ___ to c/orgasm
23
submitted 2 years ago by ___ to c/orgasm
13
submitted 2 years ago* (last edited 2 years ago) by ___ to c/orgasm
[–] ___ 7 points 2 years ago

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.

 

Here is a link to the AI porn discussion thread, just in case there are clients that only show one pin at a time

Please refrain from posting disturbingly inaccurate generations

I'm not talking about the occasional weird proportions or AI Hands(tm) we love making fun of. There have been a few (now deleted by their creator) generations that the general audience of this community have communicated they clearly do not wish to see. If you want that kind of content, feel free to create your own community for that.

And as for the "half rule": Please try not to host on Imgur. I've been having trouble accessing any kind of content whatsoever (including SFW stuff) from there in the past while, and all the FOSS frontends get rate limited frequently enough that it impacts my ability to moderate properly. I'm not going to remove posts just because they're hosted on Imgur for the time being, but please consider hosts that are friendlier to NSFW content.


Also, this community is getting way more active than I expected when I first created it. I am not exactly sure how to proceed beyond asking for a couple more people to be around to help (oh, I should mention, I added @[email protected] and @[email protected] as mods to help me with this community, and I'm considering asking for a few more people).

If you do want to be a mod, do note that one of the responsibilities you will have on your shoulders is deciding if something is underage or not. We do not allow blatant lolicon/shotacon nor any realistic posts that are clearly under 18 (If you do see anything of that sort, REPORT), but while some generations are so blatant you don't need to check beyond the thumbnail to remove, there are many that are "teetering on the line" so to speak. (And I sure as shit don't want to be the ONLY person who decides on where that line is)


And finally, there is something else that's been bugging me lately, and I feel like I should at least throw this idea out to all of you, just to see what the reception would be like:

Should realistic generations and Anime-style generations be on the same community?

When I created this community, I didn't expect how prevalent realistic posts would be. You can tell by my own posts all being Anime-styled that I have no clue how you wizards manage to do it with the quality you do. And clearly people want to see more of it, so who am I to stop you from doing so?

There are middle grounds like adding tags to titles as makeshift flairs, but I do not want to go back to the days of "please tag your post as NSFW we mods literally can't do anything about it" but instead with style tags rather than a simple checkbox that says NSFW.

You're the ones here posting and (presumably) masturbating to this content, so I'm leaving the answer to that question up to you.

This post turned out to be way longer than I expected.

[–] ___ 1 points 2 years ago

Please keep discussion to the pinned thread. There is a link in the sidebar if pins aren't showing up on your client of choice.

[–] ___ 14 points 2 years ago (1 children)

Report them and we'll remove them. This community is starting to get a bit more active than I anticipated so I can't really look at every post by myself like I could at the start.

[–] ___ 1 points 2 years ago

It's likely a caching issue considering how random it seems to be. Do a CTRL+F5 and try again.

9
submitted 2 years ago by ___ to c/hardcosplay
view more: next ›