That’s a fair one, could write a bug for it on GitHub

Yes it does.

Release notes

This is a feature. As instance owners when people started posting CP and other horrendous shit we needed something to be able to turn it off ourselves, even if another site or instance was hosting it. If someone posts even markdown with it, we are still in the eyes if governments hosting it, and thus liable.

If the WEbRTC Simulcast support is what I think it is, I think it could be useful… but I’ll have to try it out first

k.

Wow, alright, I am not here to argue. Feel free to continue arguing without me. I found a tool that quite literally was a drop-in addition for me, I had maybe one line of configuration I had to set to set it up. Silly me, I thought “Man, more admins need to know about this, hopefully they can save some money and prevent some bot traffic”.

Little did I know that doing something like giving my suggestions on things that helped me would be such an angering thing. God damn every goddamn time I post someone’s gotta through a thousand goddamn pedantic things at me. Ffs yes I know there are probably gotchas, and above I even added them. I’ve been trying to help people here and in other places I crossposted this so we could see how it would work for them. If people wanted help debugging their configurations I was ready to help debug things, offering configuration and solutions. But no, that’s too goddamn much here.

I mean what do I fucking know okay? I’ve only ran apps for over a decade like this, both myself with services here and professionally, from IIS to kubernetes from startups to big tech, I mean my job title is only senior SRE. But yes, thank you for showing me the error of my ways. I will keep things that have helped me to myself now, because posting here has been exhausting.

Well known I think I would bypass Anubis completely. Have that set as a separate block in the proxy and just continue on to whatever backend app it needs. OAuth… yeah I could see it having issues with the callback in OAuth, if it started thinking the callback endpoint was a bot. You could fix that by not using Anubis for that endpoint. In NGinx, that’s just a location block like:

location = /oauth/callback {
  proxy_pass http://lemmy-ui:1234/;
}

Where the other ones through the standard routing. Admittedly more setup.

If you choose to disable core features of your browser then yes you will have reduced functionality in your browser. That is a tradeoff you have made.

All of those both work with Anubis, and if you didn’t want them to go through Anubis would be trivial to have bypass it with one line of proxy config.

I’ve noticed you can ask the most basic thing in registrations and people bots will just ignore it

Maybe that’s why some people think it’s difficult but I didn’t find it to be. Personally it’s blocking 90% of the traffic, which for a personal instance I know that is accurate, so I’m ecstatic

As I mentioned they are held up for a few seconds once. After the trust is established a cookie is set and they pass through freely. For my instance it’s been more responsive even because the bot traffic is gone.

I mean, it was trivial for me. I run in kubernetes with a test environment with docker compose and for both of them I spun up the extra container, and then after testing that container I just swapped the Lemmy proxy over to use Anubis first. To me that’s trivial, but ymmv

Unfortunately both 0.19.4 and 0.19.5 are hanging for me when spinning up my containers, getting some weird issue with inbox timeouts. Opened a bug here

Ohhkay I finally get what you’re suggesting now. From something like Mastodon there’s no clear way to specify.

Ehh, something to be solved but not a huge deal IMO. I think it’d have to be something custom, as there’s no concept on Mastodon like Lemmy’s communities, but I still stand by DNS isn’t the way to solve it. Mixing it in with a hashtag might be a good way, where if you could “subscribe” to a hashtag over there, like #community@instance.tld, but then we’re just talking about syntax. I actually do think there needs to be a standardization on “groups” then across the fediverse, and since Lemmy is the only one I’ve seen with a group syntax, I’d just suggest we standardize !

And that’s why users get @user and communities are !community. I’m not sure what you’re asking for tbh, I think the current system works fine, searching could be easier, but I haven’t seen anyone confused by the difference there.

Nested DNS is a pain, and not really what it’s meant to do, that’s why we don’t use nested DNS. If you take DNS away as a solution (because it’s not really one), then what is currently happening makes a lot of sense.

That is how it’s done though, the syntax for communities can be searched for with !community@instance.tld. It’s just not part of DNS.

As an instance owner, the amount of overhead to support that would be nuts for me. Each subdomain would have to have DNS routed to it, or a wildcard which isn’t the best supported. On top of that I’d need to somehow manage certs in a way where when the software detects a new community it’d have to ask for a new cert and broadcast the new domain to everyone. Then what do you do about communities from other instances on your instance?

What is being done is the right way. We use DNS to tell us different services/hosts. We use the path to tell us a subsection of the same service

Right now I’m torn. I do not want to host videos. Pictures are expensive enough for me. However, I would like to see videos standardized. As you mentioned every ui handles them differently, I’d like to have a standard way that videos are handled. On the backend, something similar to pictrs would be great to enable/disable videos and enforce things like compression, video length, resolution, and more.

Actually there is, spammers are kind of funny because they help solidify the platform long term for short term gains. Turns out rate limiting was broken in the latest release of Lemmy, and no one noticed until this latest attack. So, there’s a big fix and sounds like it’ll be patched in the latest version. Thanks spammer for helping us bugfix the platform to shore it up!