

100% SO fault. I’d rather change professions than try to ask anything there.
I’m just hoping for some alternative, because there need to exist a place to exchange that kind of knowledge.


100% SO fault. I’d rather change professions than try to ask anything there.
I’m just hoping for some alternative, because there need to exist a place to exchange that kind of knowledge.


I think there’s a plug in. But it does connect to an api. So you have to have an endpoint available for that. Being an online service (mostly paid) or your own service running in your machine.


I think the issue is that many sites are too aggressive with it. Anubis can be configured to only ask for challenges if the site is under unusual load, for instance when a botnet it’s actually ddosing the site. That’s when it shines.
Making it constantly ask for challenges when the service is not under attack is just a massive waste of energy. And many sites just enable it constantly because they can defer bot pings from their logs that way. That’s for instance what op is doing. It’s just a big misunderstanding of the tool.


I don’t know if “anything”. But surely people overestimate its capabilities.
It’s only a PoW challenge. Any bot can execute a PoW challenge. For a smal to medium number of bots the energy difference it’s negligible.
Anubis it’s useful when millions of bots would want to attack a site. Then the energy difference of the PoW (specially because Anubis increase the challenge if there’s a big number of petitions) can be enough to make the attacker desist, or maybe it’s not enough, but at least then it’s doing something.
I see more useful against DDOS than AI scrapping. And only if the service being DDOS is more heavy than Anubis itself, if not you can get DDOS via anubis petitions. For AI scrapping I don’t see the point, you don’t need millions of bots to scrape a site unless you are talking about a massively big site.


You are right. For most self-hosting usecases anubis is not only irrelevant, but it actually works against you. False sense of security and making your devices do extra work for nothing.
Anubis is though for public facing services that may get ddos or AI scrapped by some not targeted bot (for a target bot it’s trivial to get over Anubis in order to scrap).
And it’s never a substitute of crowdsec or fail2ban. Getting an Anubis token it’s just a matter of executing the PoW challenge. You still need a way to detect and ban malicious attacks.


I don’t think you have a usecase for Anubis.
Anubis is mainly aimed against bad AI scrappers and some ddos mitigation if you have a heavy service.
You are getting hit exactly the same, anubis doesn’t put up a block list or anything. It just put itself in front of the service. The load on your server and the risk you take it’s very similar anubis or not anubis here. Most bots are not AI scrappers they are just proving. So the hit on your server is the same.
What you want is to properly set up fail2ban or, even better, crowdsec. That would actually block and ban bots that try to prove your server.
If you are just self-hosting with Anubis the only thing you are doing is deriving the log noise towards Anubis logs and making your devices do a PoW every once in a while when you want to use your services.
Being honest I don’t know what you are self hosting. But at least it’s something that’s going to get ddos or AI scrapped, there’s not much point with Anubis.
Also Anubis is not a substitute for fail2ban or crowdsec. You need something to detect and ban brute force attacks. If not the attacker would only need to execute the anubis challenge get the token for the week and then they are free to attack your services as they like.


My “important” emails work on a white list basis. So every sender not approved by me goes to spam. When I’m waiting for an email I’ll check the spam folder for it and white list the sender.


I guess that they want to be indexed by google for the full content but not to be seen by you.


Scary indeed.
Phone carriers are to blame. Unlimited SMS plans weren’t common when whatsapp took hold of our communications.


It’s the de facto communication medium in Europe. It’s not much of a choice. Even work related groups are usually over WhatsApp.


I contacted my representatives in Spain and they gave two fucks about it, they still positioned as “in favour”.


Why would a OS need an online account?
We truly live in the stupidest timeline.
They are closing the whole project.
Specifically they say that they are tired of pushing fixes and that they don’t find excitement in maintaining the project. With zero mentions at all to being scrapped or having any kind of AI related issue.
I don’t know if you knew the project before seeing this post. I did, I was considering between this and freshrss and chose freshrss specifically because I knew that the end of ttrss was close (this was like 2 years ago). There were a lot of signs that the development was ending and the project was on route to be abandoned.
First, source code is on github.
Second, RSS aggregators are self hostable, not a service provided by the dev. The dev would have not issues of a public instance of ttrss hosted by someone gets scrapped.
Third, RSS aggregators doesn’t really tend to be public facing. Due to their personal nature they don’t tend to be open. They are more account based.
Sorry, I really don’t see the case here.
It really doesn’t seem like that’s the case. It doesn’t even makes much sense. What do tou think was being AI scrapped? The source code?
You could want to have multiple clients in sync.
Also a web service could be fetching 24/7 and perform classification algorithms before serving to the client that will only connect a few times a day.


Newpipe, now signed by Norman Reedus, verification picture and everything!


I will push with my current phone, for a few years. Luckily abd installs could do the trick for a while.
For when this phone is failing I hope the new partnership between GrapheneOS and a phone manufacturer that’s not google is already working and producing a phone I could buy.


My despise to ads is so big that if someday ads are completely unavoidable I’ll settle for a system that just blackens the screen and mute the volume for the duration of the ads. It will still be worth it.
TIC-80 has terrible performance on firefox browser. But when you open the firefox debug logger to try pinpoint the issue it runs flawlessly.