

Yes correct. It’s just the same. Steam could just better call it “Linux” imo.
Yes correct. It’s just the same. Steam could just better call it “Linux” imo.
I think it’s actually a good thing. Let’s hope a new fork like Floorp or something will not just fork but take the lead and innovate!
Firefox has not been innovating enough in the past 10 years. It’s slow and its not having any good features either.
Love to see Linux support (or at least “steam Os”).
Rule 5 is about “If you have any questions regarding the site itself or would like to report a community”. I think this question is a valid question for Ask Lemmy, since this question it not about Lemmy or Mbin itself…
@Nyticus with “Community support” they mean questions about Lemmy software itself. the OP is not violating any rules here. You are fine.
No. That is why I shared my configs. With opcache and opcache.validate_timestamps = 0 you don’t have this problem anymore.
Of course you also need to enable opcache itself as well.
Or you have really slow spinning disks or something. Also be sure to use php 8.4.
And then the list goes on and on. Like prometheus, grafana, uptime Kuma, mariadb, Valkey, postgresql, unbound dns, all those things…
You can optimize php a lot for performance. See my config https://gitlab.melroy.org/-/snippets/91
deleted by creator
Not really… We do have this wonderful list(s): https://github.com/firehol/blocklist-ipsets
And my firewall is using for example the Spamhaus drop list source: https://raw.githubusercontent.com/firehol/blocklist-ipsets/refs/heads/master/spamhaus_drop.netset
So I know its possible. And hosting in a git repo like that, will scale a lot. Since tons of people using this already that way.
I found a very large botnet in Brazil mainly and several other countries. And abuseipdb.com is not marking those IPs are a thread. We need a better solution.
I think a honeypot is a good way. Another way is to use proof of work basically on the client side. Or we need a better place to share all stupid web scraping bot IPs.
Let them first start on focusing on performance. Since that is now really bad in Firefox. The js engine sucks hard.