X_Cli

Well, that's not entirely wrong: the website owner is responsible for contracting with Cloudflare in the first place.

It is probably just a question of price per unit. Adding a button would increase the cost drastically. If you want security, you just don't go with a RFID tag. You go with a smartcard protected by a PIN. Security-minded people are not the market segment for RFID tags. And if people are forced to use a RFID tag in a security context, they can protect the tag with a shield.

You can ask them in lemmy.ml/c/veganism We are open to people asking honest questions.

Yes, I knew about that and I find this an excellent feature! This is the reason why I'm asking about the "by default" behavior and not about "disabling score for everyone". I like that this is optional. I'm asking the community their thoughts about having scores hidden by default ;)

Maybe they just like link aggregators and the classification by communities? I don't use score-based sorting algorithms, precisely because I do not like how people vote on Lemmy.

I did not know that there are such options in Lemmy admin interface. That's very good! Thank you for the information

Edit: According to the admin documentation, one can indeed disable downvotes but I don't think one can hide scores for all users by default.

I checked and you are correct about beehaw. Thank you for the pointer. I'll probably subscribe to their communities :)

Downvoters are invited to articulate their disagreement :)

For me, Diablo Immor(t)al is a social experiment.

I have yet to hit a glass ceiling, after about 20 hours in game on a single class, doing PvE. (6 classes mean you have at least 120 hours of free gameplay ahead of you and that is a minimal value because I have not found the ceiling yet). I got MVP several times on the battleground (PvP). And I have not spent money on the game (yet; I might buy a battle pass to "pay for the game", because the devs did a good job and they deserve a few bucks).

It may be that at some point progression in PvE is blocked without acquiring legendary gems, but it just means you "finished the game". And you have a lot of other options to level up your character (XP, gear, halliquarry, cycle of strife, legacy of horadrim, and maybe more that I have not uncovered yet).

Now PvP is another thing entirely. There is no ending in PvP. People that have a competitive mindset always want to come on top. Those will face the hard reality of this world: rich people rules over the poor. And Blizzard will tap into this misplaced ego to finance their game. People that want to pay to win will eventually learn the hard (and sad) truth of the current society... It is sad that people with gambling issues will fall into that trap. But they would just as easily gamble online. Diablo Immor(t)al is just one of many options for these people...

https://github.com/gomods/athens/blob/723c06bd8c13cc7bd238e650a559258ff7e23142/pkg/module/go_get_fetcher.go#L145-L148 https://github.com/gomods/athens/blob/723c06bd8c13cc7bd238e650a559258ff7e23142/pkg/module/go_get_fetcher.go#L163-L165

So two infos:

• Github does have a rate limiter; why should SourceHut be better?
• Athens has GitHub specific code, which, I think, is pretty horrific

(I would appreciate if the down voters were able to express their disagreement with words. Maybe I'm wrong, but then, please do me the favor of explaining me how. Also, I'm not a SourceHut hater; I even give money to Drew every month, because I like the idea of SourceHut. I just think Drew is wrong on that matter)

I don't think that a robots.txt file is the appropriate tool here.

First off, robots.txt are just hints for respectful crawlers. Go proxies are not crawlers. They are just that: caching proxies for Go modules. If all Go developers were to use direct mode, I think the SourceHut traffic would be more, not less.

Second, let's assume that Go devs would be willing to implement something to be mindful of robots.txt or retry-after indications. Would attackers do? Of course not.

If a legitimate although quite aggressive traffic is DDoSing SourceHut, that is primarily a SourceHut issue. Returning a 503 does not have to be respected by the client because the client has nothing to respect: the server just choose to say "I don't want to answer that request. Good Bye". This is certainly not a response that is costly to generate. Now, if the server tries to honor all requests and is poorly optimized, then the fault is on the server, not the client.

I have not read in details the Go Proxy implementation, to be truthful. I don't know how it would react if SourceHut was answering 503 status code every now and then, when the fetching strategy is too aggressive. I would simply guess that the server would retry later and serve the Go developers a stale version of the module.