People have been having issues with uploading images/videos to Burggit sometimes, usually a lemmy issue that we have no control over. Well now we have https://shota.nu feel free to upload your embeddable files there and embed them directly into Burggit! think of it as Imgur, but less retarded!
Check it out: https://shota.nu Keep uploaded content within Burggit Rules
important note: uploaded data is NOT encrypted. For encrypted temporary file sharing, try Shota Send instead.
Important note #2: Make sure to use the direct link when embedding files! It will look something like https://shota.nu/ss/yourfileid.extension. If it does not have the /ss/ it’s not a direct link and will not embed properly on lemmy.
For ShareX Users (Click to expand)
ShareX Config Provided by: @Sheep@burggit.moe
Download link. Or just import the following from your clipboard into sharex:
{
"Version": "13.1.0",
"DestinationType": "ImageUploader, TextUploader, FileUploader",
"RequestMethod": "PUT",
"RequestURL": "https://shota.nu/upload/",
"Headers": {
"Accept": "application/json",
"Linx-Delete-Key": null,
"Linx-Access-Key": null
},
"Body": "Binary",
"URL": "$json:direct_url$",
"DeletionURL": "https://shota.nu/delete/$json:filename$?linx-delete-key=$json:delete_key$"
}
Can you please make http://shota.nu redirect to https? enabling hsts would also be nice.
First experience I had was typing it out from memory, seeing the blank nginx page, and looking up the announcement post thinking I had misremembered.
example nginx config
server { listen 80; #server_name shota.nu; return 301 https://$server_name$request_uri; } server { #listen 443 ssl; #server_name shota.nu; # max-age of 15768000 and over will get hsts permanently compiled into some static lists! # If you're unsure about maybe disabling it later, reduce it to say 7884000 add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" always; }
Also you may wanna add
server_tokens off;to your html{} block if you don’t want to show off your 3 year old nginx that has been deprecated since 2021.I was wondering why you were thinking the redirect wasn’t working because I definitely had the redirect set. I remembered I was testing this on a subdomain at first as I was originally using a different server, decided to move to a server with more available storage. Turned out the redirect was still accounting for the old domain.
Forgot to do server_tokens off, thanks for reminding me. I’m just using the latest Debian 11 stable on that machine right now, so that’d explain the old Nginx version.
nice. how about hsts?
that should be enabled now too.
looking good, thx
Happy to help.