Please try to be as active as you can. Don't just come here, fap and then leave. Try to contribute and interact with the communities here. Because it's not the numbers that will drive growth for Lemmy but the engagement. Even if you don't want to contribute, you can always comment and interact by downvoting or upvoting posts.
We need to work together to ensure the best success we possibly can for Lemmy and the wider Fediverse.
Fuck Reddit, let's all try to move away from that absolute shitshow.
On another note: If you can't view the Lemmy NSFW
communities, check out the other locally pinned post for some potential communities you could join.
Spread the Word about Lemmy NSFW if you can, as many instances don't like hosting NSFW content.
Build your own Community. No fetish is too niche, try creating your own communities to help grow Lemmy NSFW further! (Make sure your community follows all instance-wide rules, though!).
Im getting back 400 responses when trying to post new content (using catbox.moe as the image host), but the rest of the website seems to be functioning fine. just wanted to raise it up to an admin in case you were not aware :)
Posting appears to work for me, maybe try again?
its intermittent. Sometimes posting works, other times it doesnt. When it doesnt work, it seems like the fetch to get the thumbnail preview of the image works (where the browser connects to the remote url), but then right after i get a 400 on
https://lemmynsfw.com/api/v3/post/site_metadata?url=https://files.catbox.moe/rcj7o3.jpgwith the returned response of{"error":"Site metadata page fetch is not DOCTYPE html"}This happens before clicking the post button, and clicking it does not fire off another network request.Hm interesting. Not sure if this is specific to us or if it's just lemmy generally, will check it out. Do other providers work fine?
I have been using catbox exclusively. I haven't had issues posting mp4's, and i have posted images that did fetch thumbnails in the past without issue, which is the weird part. The 400 I get causes some lemmy JS to explode, so it might be something with lemmy its self. I haven't tried digging into the JS cause the stack trace it throws has a lot of single letter functions from minimized JS, and yeah - thats just pain :p