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$"
}
  • Kyou@burggit.moe
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Nice domain btw, “shota nu” basically means “naked shota” in portuguese

    • Disa@burggit.moeOPM
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      That’s great! nu means now in Swedish, Dutch, Norwegian and I think some other languages too. I love that it means naked shota in portuguese xD

      • f(loat || loathe)@burggit.moe
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        It has the same meaning in french hahah “un shota nu” : “a naked shota”, and in galician and catalan. It’s what I use to remember what the domain name is, just thinking “naked shota”.

  • Nobu@burggit.moe
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Nice :3 I use the same server, just changed a few things and different theme etc.

    • Disa@burggit.moeOPM
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      How do you get a different theme? I hate the white theme but didn’t know you could change it.

      • Nobu@burggit.moe
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        1 year ago

        I just downloaded the source and changed variables around. Working on adding an image now, which is giving me a pain in the ass to position xD coz i have to rebuild the project over and over to test.

        Highly recommend building outside of docker if u want a quick test. I chose to stick with docker, which means every time i gotta create a new docker image just to see my changes, try to fix, repeat, etc.

        Lemme know if u need help.

    • Disa@burggit.moeOPM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I don’t use ShareX it’s probably possible, I enabled API usage of the service, however since I don’t have a Windows machine I don’t really have any means of testing this.

      • Sheep@burggit.moe
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        I managed to get a config working. Feel free to include it in the main post for people on windows who do use sharex.

        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$"
        }
        
        • Disa@burggit.moeOPM
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I’ve added this to the main post and credited you for it. Thank you! Very much appreciated.

          • Sheep@burggit.moe
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            I just realized I made a “mistake” and used url instead of direct_url for the response which will cause issues in lemmy specifically as it has to be the direct url being posted. I’ve fixed my post and download link. If you could update it in the OP as well that would be much appreciated!

  • porn@burggit.moe
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    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.

    • Disa@burggit.moeOPM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      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.