i don't think it's a great idea to make what is essentially a direct bypass for the age gate... x)
there is already a direct bypass for the age gate: you can simply hotlink the images. or copy-paste them, as artists are now doing
cohost added an age gate for a good reason. verifying that someone is allowed to see certain content is extremely important. i'm pretty sure in many jurisdictions it's also a legal requirement.
if someone wanted to hotlink the images, they would have to go to the page and pass the age gate. of course, there's probably not much cohost could do beyond that point. if that user wanted to copy the image URL/data and paste it somewhere else, that's on them.
i'd assume it's a completely different story for cohost to add a bypass on their end. of course, it's technically possible to have adult content in embeds, but how is cohost gonna make sure kids and such don't see that on a third party platform like discord?
just because there's technically a way around the gate, doesn't mean we should get rid of the gate altogether. as much as i greatly support NSFW artists, i think it's extremely important to make sure the people who want that type of content can access it, while the people who shouldn't or don't want to, cannot.
imho, the current system works.
more to the point, it doesn't really impact offsite embeds when someone is actively trying to share the work, since as i noted, artists are already pasting their images alongside cohost
links. it's just adding extra steps.
ianal and cannot speak authoritatively to any legal concerns, but i'm not aware of any specific US requirement here. and notably, twitter will happily embed images for a tweet marked as "sensitive" — despite having a warning prompt if you view the same tweet on-site.
im struggling to find any specific laws on the matter (especially in the US), but i'm almost certain that several other countries have this type of legislation at least. (i am also not a lawyer lol)
as nice as it would be to be able to share this type of content more easily, i honestly don't know how it could be done without compromising age verification to some degree.
that said, i'm not sure why or how twitter allows embedding like that... do those laws somehow not apply in those cases...?
There is definitely 100% no law saying that your discord embeds have to do special magic to hide porn. Discord is the party responsible for displaying embeds on discord, and if your server is allowing lots of porn in channels not marked 18+, they can (and I believe sometimes do) take enforcement action.
We include the age gate as a best practice / way to avoid Surprise Porn. It's obviously easy to bypass the age gate, as it is easy to bypass the age gate on sign-up (as I've said before, lying is easy and free). Every single age gate that isn't "submit a photo of your ID" is based on the honor system.
Having an opt-out bypass for embeds would make sense, although I'm not sure how we'd manage discoverability UX here. Taking it under consideration.
just posting to say this would improve the usefulness of the site for me quite a bit. would be cool if links worked in discord embeds too!
discord embeds are discords problem. like, its all on discord's end, and you can't just turn off discord's age gate remotely like that. embeds dont talk to the site they're embedded on (and its a good thing they don't, for privacy reasons). discord doesn't know you've consented to view adult content on cohost, cohost doesn't know you've consented to view adult content on discord.
also, i agree that the age gates are there for a good reason.
fake edit: oh yeah, you're eevee. this is expected behaviour for you lol. mate can you please learn a lesson for once in your life and stop trying to smuggle minors past age gates for five fucking seconds
Hey that's completely technically incorrect on the one hand, and either malicious slander or lies you've been duped by on the other.
You can easily verify that discord has nothing to do with it whatsoever: simply make a SFW post and mark it 18+, then an identical one and don't mark it, and post them both to discord. The marked one will say "this post contains 18+ content", and that text is coming from cohost, and is determined entirely by the adult content checkbox. For further verification, you can also confirm that discord will happily embed NSFW content in a cohost post if you don't mark it 18+ on cohost (though of course if you do try this please make the post from a page with no followers and don't tag it, and probably delete it after).
And then on the other hand: before you go accusing people of things online, please actually do your research. If you care enough about the situation to be nastily airing your opinion in public, you care enough to spend the time to read the relevant documents. The things you think happened did not happen.
you're just repeating what I said. discord indeed has nothing to do with it whatsoever - discord and cohost don't know what the other is doing, and so they both need to independently ask for age verification. so its fine they both do so. whats not clicking.
the things i was talking about certainly happened. i'm talking about exposing minors to pokemon porn, which is admitted to be true in the documents you posted (even as it's couched in excuses). like, you would think you'd learn the importance of age gates, after an whole-ass callout blew up somebody you knew just because of lacking age gates lmao. i was on tumblr for the pengo callout, and all the other minors who came forward after the fact. I remember it.
eevee
currently, if i drop a link to an 18+ post in e.g. discord, the embed simply displays
"this post contains 18+ content"
which is a reasonable default, but in an environment like a nsfw discord channel, everyone has already agreed to see 18+ work. so at best this is redundant, but at worst people may not even realize it's supposed to be a link to artwork.
this isn't like massively inconveniencing, but i've already seen several artists trip over it, and it seems like it discourages use of cohost as a "canonical" adult art host.
(i don't know exactly what this would look like. you could slap another path segment on the end, but then any ui, as well as making the response contain both a redirect and the appropriate meta tags, are left as an exercise to the reader)
29 people like this idea