If you don’t like the layout of regular Lemmy, feel free to use these :) (They can also be used for instances other than ours. Except for mlmym, they only have a single instance mode and no default instance config)

And in case you’re wondering why we aren’t using old.lemmy, a.lemmy etc instead…

Cloudflare charging $10 to have layered subdomains

…it’s because CF wants money for that and I’m not paying for that shit lmao

  • tustamido@lemmy.fmhy.netEnglish
    1·
    10 months ago

    Thank you!

    Maybe you should promote these links in main page sidebar like other instances do for people to notice them.

    • nullishcat@lemmy.fmhy.netOP
      1·
      10 months ago

      after switching to ansible, pictrs (the image backend) didn’t have proper perms to access its own folder (for whatever reason.) this is now fixed.

  • Martineski@lemmy.fmhy.netEnglish
    0·
    10 months ago

    Why use “-” instead of “.” to separate the prefix?

    The dot looks better imo, that’s all.

    Edit: lmfao, I should learn to actually read stuff before commenting.

      • Martineski@lemmy.fmhy.netEnglish
        0·
        10 months ago

        I wouldn’t too because I don’t think that there’s any technical reason to make the user pay for that. Or maybe there is, I’m not very tech savvy.

        • nullishcat@lemmy.fmhy.netOP
          1·
          10 months ago

          With how cloudflare is setup, there technically is, but it’s also bullshit. Basically they have two certificates for SSL (which allows for https): example.com and *.example.com. These cover everything from example.com to superlongsubdomain.example.com, but NOT, say, a.b.example.com. That would require something like *.b.example.com.

          This is kinda BS though, as certificates are pretty much free nowadays. I guess it saves on server load? But it’s so minimal that there really is no reason to charge for it, especially not with a monthly subscription. ($120/yr for certs!!)