embedded image links from discord ( urls like "https://cdn.discordapp.com/attachments/...") will go stale over time because they don't want you to use their cdn as free public facing file hosting. embeds from imgur still last though (make sure to right click the image and choose "copy link", the link from the copy button will just take you to that imgur page and it won't embed how you want it to.
alternatively one can use base64 encoded images using something like this
:3c
imgur is good but i would recommend filegarden as well
reach out on discord @cytosol for moderation-related help!
seconding discord embeds not being a viable place, but imgur is also bad.
a while ago they nuked a pretty significant amount of their posts, including uploads without user accounts and nsfw uploads, even ones attached to accounts. (though the model they used to do this sucks and had a lot of both false positives and false negatives)
this is funny to say while we're currently disallowing it, and my only preemptive lampshade is "we're working on it", but never trust a platform that doesn't allow NSFW content. they will sell every user out the moment it risks their own platform.
hosting stuff on the internet is a difficult thing right now.
SHAPED OR MOLDED FORMS appear to have been formed from a plastic material through directly applied force.
ABSTRACT FORMS are of uncertain origin.
wait are we good to use base64 image urls or no. Bc like on the one hand there's no file upload button but on the other that could just be bc actually implementing file uploads would be a pain
honestly I wouldn't go the base64 route, just stick to using filegarden and make a folder for random crap that's destined for appearing in your posts.
https://shinyjiggly.github.io/dungeon-crashers-website/dungeoncrashers/index.html
(aough where is the bb code editor on this thing)
idk to me it seems better because then I wouldn't have to worry about an image host deleting my images
Nice thread to stumble across while setting up my media server. If it's working, this image should show up:
// actually implementing file uploads would be a pain
It's not as daunting as it may seem, it's just a bit... exotic. Getting media storage and a CDN is piss easy nowadays (just don't get ripped off), the real challenge is doing the backend code for it.
This is roughly the journey a file takes thru a backend: user sends POST w/ file -> basic validation e.g. filesize -> convert uploads into temp files -> validate the mime type, generate hashes maybe -> send them to the media server (yolo) -> delete the temp file -> save the URL it's sent to
About 50% of that can be handled thru extensions, depending on your stack. At my pace this takes about a week and a half to get working, minus tests.
Btw, is gyazo still usable as an image hoster? Last time I checked it should be, though I remember it being a bit coy about linking to the raw image file
HE IS
ABSOLUTELY
KILLED!!!!
