Re:How the FSF sysadmins block botnets with reaction
by cyanydeez on Saturday July 11, 2026 @08:16PM
(#48877086)
are scrapers attackers?
I get they're DDoS; but take the mask off, and arn't they just the AI monied interests that fund the FSF? and a lot of them are just active inference, eg, the user is trying to ask about something and the AI monied interests setup a web scraper to go and get that data.
Just seems like no one wants to call out the hand that feeds them in a human centipede that's best described as the torment nexus.
Re:How the FSF sysadmins block botnets with reaction
by m3047 on Tuesday July 14, 2026 @01:17PM
(#48910066)
Anything which fills my logs with garbage is unwanted. Your cat could have fallen asleep on the keyboard, I don't care. If you want to use the internet as a giant petri dish, that's on you; but the cat box is elsewhere. I can feed you garbage or block you because your code is shit, or I don't like your style.
Re:How the FSF sysadmins block botnets with reaction
by nubinetwork on Saturday July 11, 2026 @11:03PM
(#48877900)
> We placed our regular expressions in fail2ban, and found that we were hitting the maximum rules that could be added to UFW firewall rules on our systems which showed degradation around 65,000 rules
Firewalld had a similar issue up until recently as well.
Re:How the FSF sysadmins block botnets with reaction
by Magicrafter13 on Tuesday July 14, 2026 @11:54AM
(#48908765)
> This software is gay, trans and anticolonialist. If you're uncomfortable with that, please don't use it
Weird message to include in AGPLv3 licensed software (which explicitly allows people to use software however they like, regardless of their beliefs or feelings).
Re:How the FSF sysadmins block botnets with reaction
by graemep on Tuesday July 14, 2026 @12:41PM
(#48909510)
You can, but if the exact quote in the GP is correct the claim is claiming the software is "gay, trans and anti-colonialist" and asks you not to use it. Why use a license that is designed to be politically neutral and then ask some people not to use it?
What I can see is a fairly clear indication that they do not want contributions from people whose politics differ from theirs. I would also question whether government funding of a project with political policies about who can participate is appropriate. The political stance is also rooted in a particular culture so is unwelcoming to people from other cultures.
Of course people can political views and preferences, but they presumably have some aim in mind when making that statement in the README. What is that aim?
Re:How the FSF sysadmins block botnets with reaction
by BigTTYGothGF on Tuesday July 14, 2026 @12:54PM
(#48909721)
> What I can see is a fairly clear indication that they do not want contributions from people whose politics differ from theirs
This is the same FSF that in the past has refused contributions from people whose politics include "I would like this software to run on my windows/apple/other proprietary platform". They're extremely political.
Re:How the FSF sysadmins block botnets with reaction
by collinfunk on Tuesday July 14, 2026 @01:04PM
(#48909872)
When did this occur? I am a GNU maintainer, and have never heard such a thing from the FSF. The GNU Coding Standards and other similar texts leave the decision to support non-free platforms up to the maintainer.
Re:How the FSF sysadmins block botnets with reaction
by rpdillon on Tuesday July 14, 2026 @04:28PM
(#48912546)
It was an emoji solution for Emacs that only worked on Mac. RMS basically said:
"If the point is to promote Free Software, we do ourselves a disservice by making our Free Software work better on a proprietary system than a Free system. Let's include this support when it works on the Free platforms as well."
FSF is political, but only about Free Software. Their goal is to promote it, and I think RMS has shown very clear thinking in this regard. I don't love the decision/outcome (someone did work to make something better and it was rejected), but I get it in service of the larger goal.
To flip the pschology, you could imagine a world where Emacs did way more awesome stuff on Windows and Mac, and the ensuing HN discussion where the obvious snipe appears a dozen times: "lol they keep talking about free software but their own products work better on windows lol".
Re:How the FSF sysadmins block botnets with reaction
by Ferret7446 on Tuesday July 14, 2026 @10:15PM
(#48915465)
FSF is not political in the sense that they won't forbid you to use their software or otherwise blacklist you even if you are against free software, or if you're far left or far right. They are only political in the sense that they have a goal. If that's how you define "political" then the word is somewhat meaningless.
They won't take contributions not aligned with their goals but won't block you from sharing your contributions in the spirit of free software.
Re:How the FSF sysadmins block botnets with reaction
by Permik on Tuesday July 14, 2026 @09:49PM
(#48915289)
I'd like to suggest that this messaging is actually the inverse of virtue signaling, I.E. "icky signaling" for snowflakes. Keeps people at bay who are icked by the message.
Re:How the FSF sysadmins block botnets with reaction
by stonogo on Tuesday July 14, 2026 @12:51PM
(#48909679)
The aim is to reduce the number of users of the software who are uncomfortable with those who are gay, trans, and/or anticolonial, probably because dealing with such people is a heavier burden than the other kind.
Re:How the FSF sysadmins block botnets with reaction
by graemep on Tuesday July 14, 2026 @01:19PM
(#48910096)
How would a you even know whether a user was uncomfortable with any of those things? Why would someone with a particular political stance be a heavier burden on maintainers? How would you even know how someone felt - if someone reports a bug it is highly unlikely they are going to add something like "I am uncomfortable with gays" are they? Nor is it going to be in the comments in contributed code. It sounds more like that the maintainers are uncomfortable with people who are not like themselves.
Re:How the FSF sysadmins block botnets with reaction
by Groxx on Tuesday July 14, 2026 @01:34PM
(#48910286)
You seem to be drastically overcomplicating this. They are asking people who are uncomfortable with it to not use it. The people who are uncomfortable with it are the ones deciding, nothing at all in there implies that they are deciding who is uncomfortable.
Re:How the FSF sysadmins block botnets with reaction
by McGlockenshire on Tuesday July 14, 2026 @01:39PM
(#48910381)
> Why would someone with a particular political stance be a heavier burden on maintainers?
Because of sealioning, among other things. If you aren't familiar with the term, please look it up. You're doing it right now. This post, and your reaction are textbook sealioning.
Re:How the FSF sysadmins block botnets with reaction
by jasonvorhe on Tuesday July 14, 2026 @03:37PM
(#48911971)
> Dude who came up with the term: "The core of what I set out to criticize is just the notion that any random patient stranger should feel entitled to as much of someone's attention as they want."
I don't see how that's related to the topic or issue being discussed though. If you're a maintainer you decide when to shut down a discussion. Someone is annoying/creepy/difficult and wants a feature? Let them fork it, eod. Every escalation afterwards is basically just trolling or harassment.
Re:How the FSF sysadmins block botnets with reaction
by lenkite on Wednesday July 15, 2026 @09:12AM
(#48920348)
The GPL mandates that if you modify and distribute GPL licensed software, your derivative work must also be free and open-source. This ensures code cannot be made proprietary.
Other than that, there is no expectation of political stance.
Only in the current ultra-modern age, has politically neutral devolved to meaning that you must agree with me on 99.99%.
Re:How the FSF sysadmins block botnets with reaction
by max__dev on Saturday July 18, 2026 @01:28PM
(#48960170)
1. GPL is extremely and intentionally political
2. anti-colonialism is not a trait of culture
3. the state of being gay/trans is not political
4. culture != politics
5. is != ought
Of course people can have their preferences, but presumably that reaction implies "gay/trans anti-colonialist" ought to be a problem for some "political/cultural" groups?
What is the aim of that?
My read is that the authors are signalling their community is a "safe space". I don't think they're trying to exclude particular cultures, trigger people, or otherwise cause problems.
Re:How the FSF sysadmins block botnets with reaction
by Bender on Tuesday July 14, 2026 @12:08PM
(#48908973)
My preference is to 'ip route add blackhole ${net}' as it has the lowest CPU overhead and I can add hundreds of thousands of CIDR blocks with no noticeable impact. The only downside is that it won't stop UDP packets from getting to a UDP listener. There will not be a response but the application will still see it. For my TCP daemons it's great.
Those 426951 blackhole routes include data-centers, VPS providers, botnets, known bad residential nodes and much more. I still see a few residential proxy bots but the feds are playing whack-a-mole with them. The bots self report to my silly blog so I can block them elsewhere on systems I might care a little bit about.
Re:How the FSF sysadmins block botnets with reaction
by Bender on Tuesday July 14, 2026 @01:08PM
(#48909927)
How do you decide when to add/remove a range?
The only IP's that come and go are the Tor 30 day blocklist and a couple FireHOL attackers from a repo though I will sometimes leave the last entries live until reboot. I do not really need to block tor but I use this silly blog as a testing ground. Tor and some known abusers come from a git repo I refresh periodically.
The data-centers, VPS providers, CDNs, known botnets are perma-banned. For my hobby nodes I personally find this acceptable. I would not do this in a professionally managed data-center. There are better methods for those cases especially for B2B corporate arrangements. Regardless of what daemons I run I never have external dependencies that need to be accessed from my node or from the client with exception of stratum-1 time servers.
I do have to periodically update the CIDR blocks for given ASN's. I have not automated this but I probably should some day. It's not hard to automate, I am just excessively "efficient". I was told to stop calling myself lazy, but I am.
Methods 2, 3 and 5 are the ones I talk about here. [1]
Re:How the FSF sysadmins block botnets with reaction
by TurdF3rguson on Tuesday July 14, 2026 @05:01PM
(#48912890)
The problem is when you block those "residential proxy bots" you also block real people who just happen to have a dumb teenager on their network playing some free games that are monetized by proxies.
The only real solution to bots is making users log in. And even then you have to fight registration bots.
Re:How the FSF sysadmins block botnets with reaction
by Bender on Tuesday July 14, 2026 @05:27PM
(#48913153)
I get what you mean. It happens all the time when some clown trashes an IP's reputation and Cloudflare or Google will send the next lease of that IP into crosswalk fire-hydrant bus traffic light purgatory.
That's why I eventually let those go usually after a kernel update and the git repo for FireHOL gets updated often. The kernels get updated often. I only perma-ban the data-centers which is fine for my silly blog and probably for some peoples hobby sites. People can chose which methods to apply, how to apply them or which ones to skip entirely.
Excellent username btw. Those SNL Celebrity Jeopardy episodes are unforgettable. [1]
Re:How the FSF sysadmins block botnets with reaction
by hun3 on Tuesday July 14, 2026 @10:54PM
(#48915696)
> The only downside is that it won't stop UDP packets from getting to a UDP listener. There will not be a response but the application will still see it.
Re:How the FSF sysadmins block botnets with reaction
by Bender on Wednesday July 15, 2026 @08:15AM
(#48919649)
What does all of this give you?
A playground to test things. A place for bots and their kin to report themselves to me so that I can use this information for sites I actually want to protect a little bit. A place to share some ideas with a small handful of like minded people.
Blogs are throw away for me. After some time I delete the VM and edit articles offline for 6 to 18 months and then put them back up on another domain when there may be a need to share some old articles. This method disjoints the archive sites.
Re:How the FSF sysadmins block botnets with reaction
by wasmperson on Tuesday July 14, 2026 @12:15PM
(#48909087)
It's somewhat interesting to see the FSF's approach to this. From what I understand they can't really use something like anubis since they want their websites to be accessible without javascript:
Users can't consent to running a page's javascript the way they can consent to running a program they've intentionally downloaded, so it's effectively "non-free" regardless of license.
Re:How the FSF sysadmins block botnets with reaction
by xena on Tuesday July 14, 2026 @12:49PM
(#48909641)
The meta refresh challenge actually uses time as the proof! It makes sure you wait for at least 75% of the time the administrator configured and adds client side smear to ensure that browser temporal randomization doesn't trigger a false failure.
Re:How the FSF sysadmins block botnets with reaction
by idoubtit on Tuesday July 14, 2026 @12:19PM
(#48909159)
That's interesting. I haven't used fail2ban for a long time, but reaction is worth evaluating. Unfortunately, that post does not describe their full configuration. Maybe it's on purpose, so that attackers can't adjust to fit.
My experience is that modern web scraping had no obvious pattern, since it is proxied through many IPs. The last time a server was failing to handle the pressure, we decided to temporarily ban IPs from some Asian regions. How does the FSF decide to ban an IP?
Why do they use iptables + ipset instead of nftables? Is there a technical reason or is it just legacy? AFAIK, Nftables is more performant, and IMO simpler. And it has native sets, see https://wiki.nftables.org/wiki-nftables/index.php/Sets
Re:How the FSF sysadmins block botnets with reaction
by itintheory on Tuesday July 14, 2026 @01:26PM
(#48910172)
> The last time a server was failing to handle the pressure, we decided to temporarily ban IPs from some Asian regions.
This is something we've been forced to do at work, a LOT. Some weeks it's Huawei Cloud, Tencent, and Alibaba. Other weeks it's all China Telecom. We're using Anubis where possible, but a lot of it is just whack-a-mole with residential proxies. I looked at Datadome and HUMAN, but they would be hundreds of thousands a year at our traffic scale, and I suspect may also have false positives. We abandoned CrowdSec for that reason as well.
I'd love to find a decent k8s native solution to this problem.
Re:How the FSF sysadmins block botnets with reaction
by Hackbraten on Wednesday July 15, 2026 @10:18AM
(#48921224)
> I looked at Datadome and HUMAN, but they would be hundreds of thousands a year at our traffic scale, and I suspect may also have false positives.
I can confirm. DataDome has been making my life a living hell. It thinks my phone is a bot, so I can no longer use PayPal and other quasi-monopoly services while on the go. DataDome will reliably block me on the first request.
Re:How the FSF sysadmins block botnets with reaction
by arbol on Wednesday July 22, 2026 @12:02PM
(#49008902)
Prosopo could cut out a lot of the residential proxy nonsense for you. We integrate with lambda@Edge / cloudfront workers / server side and perform analytics to detect residential proxy networks - at far less cost than DD or HUMAN.
Re:How the FSF sysadmins block botnets with reaction
by thomzane on Tuesday July 14, 2026 @01:58PM
(#48910681)
iptables has been mostly a wrapper for nftables for some time now. The choice of iptables + ipset with reaction is the difference in their configuration. Compare restart performance between the ipset and nftables example configurations with lists of greater than 1 million IPs.
Re:How the FSF sysadmins block botnets with reaction
by m3047 on Tuesday July 14, 2026 @01:27PM
(#48910195)
"Many sysadmins know about fail2ban..." and many will now know about reaction. But why will the result be any different than fail2ban? It won't.
I identify features (which can be expressed as firewall rules) from log data; I write totals to a temporary store (Redis). I have periodic tasks which scan the temp store for patterns which exceed thresholds. When that occurs, fail2ban creates the appropriate rules. This occurs in depth and in concentric rings.
Re:How the FSF sysadmins block botnets with reaction
by m3047 on Tuesday July 14, 2026 @06:42PM
(#48913860)
Why should I have a blog post? I get amazing "performance" out of fail2ban, it does what it's supposed to do and I don't ask it to do more. I've given it "super powers".
Last year I blocked basically all of Brazil. No problems. Who knew?
Re:How the FSF sysadmins block botnets with reaction
by charcircuit on Tuesday July 14, 2026 @01:29PM
(#48910212)
>Popa botnet
It's no more of a botnet than ProtonVPN for example. Apps intentionally added the Popa SDK to their apps as a monetization method. This allows apps without ads and tracking to be financially viable. I would expect FSF to support apps being able to move off of monetization schemes that depend on tracking people so it is disappointing for them to put such alternative monetization technologies in a negative light.
Re:How the FSF sysadmins block botnets with reaction
by thomzane on Tuesday July 14, 2026 @02:06PM
(#48910802)
This monetization scheme benefits the botnet controller and the developer who added the SDK and not the user who likely did not realize they signed up to become an exit node.
Re:How the FSF sysadmins block botnets with reaction
by charcircuit on Tuesday July 14, 2026 @03:33PM
(#48911904)
It allows as free versions of apps to be economically viable and compete with others. It helps users because they don't need to be spied on and shown ads to fund the development of the app.
The existence of an app brings users value, else they wouldn't use it.
Re:How the FSF sysadmins block botnets with reaction
by ryandrake on Tuesday July 14, 2026 @04:10PM
(#48912360)
Recruiting your users' systems into a botnet is not an acceptable way to make an app "economically viable" any more than, say, installing a rootkit on their systems.
Re:How the FSF sysadmins block botnets with reaction
by charcircuit on Wednesday July 15, 2026 @02:46AM
(#48917107)
Is Google Maps a botnet because all of the clients share location data to make navigation more optimized? Having multiple users connecting back to a central server does not make something a botnet. Users should be able to decide for themselves whether they want apps like this or not.
Re:How the FSF sysadmins block botnets with reaction
by ryandrake on Wednesday July 15, 2026 @10:50AM
(#48921714)
The difference of course is that Popa does not provide 1. informed consent to users and 2. actual useful app functionality. The user does not know when an application is using the Popa SDK and does not know their device has been compromised. It is bundled inside seemingly legitimate software without the user's knowledge. Therefore, the user cannot make an informed decision about whether to use the app. Also, unlike the Maps example, the botnet provides no feature that the user would want or choose.
Popa is an illegitimate and botnet[1] that no end user knowingly/willingly uses.
Re:How the FSF sysadmins block botnets with reaction
by nemomarx on Tuesday July 14, 2026 @03:52PM
(#48912153)
the fsf has never really been concerned with commercial viability. They're the worst audience for this sort of argument.
and I doubt these apps are really Free versions - do they support user modifications and access to the code? If they did support the four freedoms maybe the fsf would have something positive to say to balance it out?
Re:How the FSF sysadmins block botnets with reaction
by thomzane on Tuesday July 14, 2026 @10:02PM
(#48915383)
I would not have as big of a problem with it if it was a transparent arrangement that the app is free of cost, but the Internet connection would be shared with customers of RoboVPN. The issue is that the often invisible arrangement is not obvious and likely breaks the terms of service with the Internet Service Provider. If the user was intentionally running a TOR node, I would not have a problem with it. The current reality of it is absolutely unethical and breaking the Internet as we know it.
I get they're DDoS; but take the mask off, and arn't they just the AI monied interests that fund the FSF? and a lot of them are just active inference, eg, the user is trying to ask about something and the AI monied interests setup a web scraper to go and get that data.
Just seems like no one wants to call out the hand that feeds them in a human centipede that's best described as the torment nexus.
Can you elaborate on who these interests are precisely?
Firewalld had a similar issue up until recently as well.
Weird message to include in AGPLv3 licensed software (which explicitly allows people to use software however they like, regardless of their beliefs or feelings).
What I can see is a fairly clear indication that they do not want contributions from people whose politics differ from theirs. I would also question whether government funding of a project with political policies about who can participate is appropriate. The political stance is also rooted in a particular culture so is unwelcoming to people from other cultures.
Of course people can political views and preferences, but they presumably have some aim in mind when making that statement in the README. What is that aim?
Because you can have preferences while not restricting legal rights.
This is the same FSF that in the past has refused contributions from people whose politics include "I would like this software to run on my windows/apple/other proprietary platform". They're extremely political.
"If the point is to promote Free Software, we do ourselves a disservice by making our Free Software work better on a proprietary system than a Free system. Let's include this support when it works on the Free platforms as well."
FSF is political, but only about Free Software. Their goal is to promote it, and I think RMS has shown very clear thinking in this regard. I don't love the decision/outcome (someone did work to make something better and it was rejected), but I get it in service of the larger goal.
To flip the pschology, you could imagine a world where Emacs did way more awesome stuff on Windows and Mac, and the ensuing HN discussion where the obvious snipe appears a dozen times: "lol they keep talking about free software but their own products work better on windows lol".
They won't take contributions not aligned with their goals but won't block you from sharing your contributions in the spirit of free software.
Because of sealioning, among other things. If you aren't familiar with the term, please look it up. You're doing it right now. This post, and your reaction are textbook sealioning.
I don't see how that's related to the topic or issue being discussed though. If you're a maintainer you decide when to shut down a discussion. Someone is annoying/creepy/difficult and wants a feature? Let them fork it, eod. Every escalation afterwards is basically just trolling or harassment.
The GPL variants are the antithesis of politically neutral.
The GPL "tolerates" conflicting political opinions, which used to be closer to the norm and thus not political.
Other than that, there is no expectation of political stance.
Only in the current ultra-modern age, has politically neutral devolved to meaning that you must agree with me on 99.99%.
Of course people can have their preferences, but presumably that reaction implies "gay/trans anti-colonialist" ought to be a problem for some "political/cultural" groups?
What is the aim of that?
My read is that the authors are signalling their community is a "safe space". I don't think they're trying to exclude particular cultures, trigger people, or otherwise cause problems.
I'm most concerned about blocking innocent users, currently I use Cloudflare to block known bad ASNs using a list I found on GitHub.
The only IP's that come and go are the Tor 30 day blocklist and a couple FireHOL attackers from a repo though I will sometimes leave the last entries live until reboot. I do not really need to block tor but I use this silly blog as a testing ground. Tor and some known abusers come from a git repo I refresh periodically.
The data-centers, VPS providers, CDNs, known botnets are perma-banned. For my hobby nodes I personally find this acceptable. I would not do this in a professionally managed data-center. There are better methods for those cases especially for B2B corporate arrangements. Regardless of what daemons I run I never have external dependencies that need to be accessed from my node or from the client with exception of stratum-1 time servers.
I do have to periodically update the CIDR blocks for given ASN's. I have not automated this but I probably should some day. It's not hard to automate, I am just excessively "efficient". I was told to stop calling myself lazy, but I am.
Methods 2, 3 and 5 are the ones I talk about here. [1]
[1] - https://nochan.net/b/Internet-Crap/20260606-How-To-Block-Som...
The only real solution to bots is making users log in. And even then you have to fight registration bots.
That's why I eventually let those go usually after a kernel update and the git repo for FireHOL gets updated often. The kernels get updated often. I only perma-ban the data-centers which is fine for my silly blog and probably for some peoples hobby sites. People can chose which methods to apply, how to apply them or which ones to skip entirely.
Excellent username btw. Those SNL Celebrity Jeopardy episodes are unforgettable. [1]
[1] - https://www.youtube.com/watch?v=bEghu90QJH4
Try:
Peace of mind? Fair enough but I'd be more wary about blocking legitimate users. VPS providers are often used for VPNs etc.
A playground to test things. A place for bots and their kin to report themselves to me so that I can use this information for sites I actually want to protect a little bit. A place to share some ideas with a small handful of like minded people.
Blogs are throw away for me. After some time I delete the VM and edit articles offline for 6 to 18 months and then put them back up on another domain when there may be a need to share some old articles. This method disjoints the archive sites.
https://www.gnu.org/philosophy/javascript-trap.html
Users can't consent to running a page's javascript the way they can consent to running a program they've intentionally downloaded, so it's effectively "non-free" regardless of license.
https://anubis.techaro.lol/docs/admin/configuration/challeng...
I guess for the meta refresh challenge it's less "proof of work" and more "proof of patience".
Won't, they call it malware: https://www.fsf.org/blogs/sysadmin/our-small-team-vs-million...
My experience is that modern web scraping had no obvious pattern, since it is proxied through many IPs. The last time a server was failing to handle the pressure, we decided to temporarily ban IPs from some Asian regions. How does the FSF decide to ban an IP?
Why do they use iptables + ipset instead of nftables? Is there a technical reason or is it just legacy? AFAIK, Nftables is more performant, and IMO simpler. And it has native sets, see https://wiki.nftables.org/wiki-nftables/index.php/Sets
This is something we've been forced to do at work, a LOT. Some weeks it's Huawei Cloud, Tencent, and Alibaba. Other weeks it's all China Telecom. We're using Anubis where possible, but a lot of it is just whack-a-mole with residential proxies. I looked at Datadome and HUMAN, but they would be hundreds of thousands a year at our traffic scale, and I suspect may also have false positives. We abandoned CrowdSec for that reason as well.
I'd love to find a decent k8s native solution to this problem.
I can confirm. DataDome has been making my life a living hell. It thinks my phone is a bot, so I can no longer use PayPal and other quasi-monopoly services while on the go. DataDome will reliably block me on the first request.
Fuck DataDome.
I identify features (which can be expressed as firewall rules) from log data; I write totals to a temporary store (Redis). I have periodic tasks which scan the temp store for patterns which exceed thresholds. When that occurs, fail2ban creates the appropriate rules. This occurs in depth and in concentric rings.
Et tu?
Do you have a blog post about your automated fail2ban rule generation?
Last year I blocked basically all of Brazil. No problems. Who knew?
It's no more of a botnet than ProtonVPN for example. Apps intentionally added the Popa SDK to their apps as a monetization method. This allows apps without ads and tracking to be financially viable. I would expect FSF to support apps being able to move off of monetization schemes that depend on tracking people so it is disappointing for them to put such alternative monetization technologies in a negative light.
The existence of an app brings users value, else they wouldn't use it.
Popa is an illegitimate and botnet[1] that no end user knowingly/willingly uses.
1: https://krebsonsecurity.com/2026/07/fbi-seizes-netnut-proxy-...
and I doubt these apps are really Free versions - do they support user modifications and access to the code? If they did support the four freedoms maybe the fsf would have something positive to say to balance it out?
I pay for some software services. The services I pay for have a billing page (or a donation page) and I pay via the banking system
I rigorously block every ad, every tracker, every thing that does "monetization"
The evil period of trying sneaky ways to generate money is, I am optimistic, coming to an end.
If you want my money, ask me. If you must have my money, demand it. If you are sneaking around "monetization" I will do everything I can to stop you.
You got a genuinely free, to you, app.