I don't know if it's a DDoS or a very rude scraper. Stand by.
Also unauthenticated whatever is temporarily kill. Accounts being scraped are a Baraag account, @judgedread , Drew DeVault's accounts, and me. Maybe others. Since one of them is DeVault's old account, it's not randomly selected accounts from the public timeline. It's enough requests that it's actually saturating the pipe. Very large number of hosts and I swat one and another pops up, they're ignoring 429s, 401s, 403s.
> Nobody proved there was an *Oban* bottleneck and still haven't.
Well, this was a remark years back. (It does still irk me.) Everything I know about the current Oban bug is second-hand, I am running what might be the only live Pleroma instance with no Gleason commits (happy coincidence; I was actually dodging another extremely expensive migration and then kicked off the other project, which meant I don't want to have to hit a moving target if I can avoid it, so I stopped pulling); at present, I backport a security fix (or just blacklist an endpoint) once in a while.
Unless you mean the following thing, but I haven't run 2.7.0. I don't know what that bug is.
> If I could reproduce reported issues it would be much easier to solve them but things generally just work for me.
I mean, like I mentioned, the Prometheus endpoints were public at the time. You could see my bottlenecks. (I think that would be cool to reenable by default; they'd just need to stop having 1MB of data in them if people are gonna fetch them every 30s, because enough people doing that can saturate your pipe.)
> A ton of work has been put into correctness (hundreds of Dialyzer fixes) and tracking down elusive bugs and looking for optimizations like reducing JSON encode/decode work when we don't need to, avoiding excess queries, etc.
I'm not sure what the Dialyzer is (old codebase), but improvements are good to hear about. That kind of thing gets you a 5%, 10% bump to a single endpoint, though. The main bottleneck is the DB; some cleverness around refetching/expiration would get you some much larger performance gains, I think; using an entire URL for an index is costing a lot in disk I/O. There's a lot of stuff to do, just not much of it is low-hanging, I think.
pistolero (p@fsebugoutzone.org)'s status on Saturday, 26-Oct-2024 00:51:41 JST
pistoleroConcurrent with the recent missile attack, Iran did some attempt at botnet; I don't know if details came out. But I'd made some remarks on IRC that there was a weird uptick in .ir IPs trying low-effort ssh brute-force attacks. So I'd said in a thread on fedi that this was weird: you run some machines that have public IPs and just watch and you see a lot of weird stuff, you can tell something is going down but maybe can't say *what* it is that is going down, you just know that something is up and if nothing has changed recently, then something is coming up in the next couple of weeks.
> The announcement itself shocks me, a year ago he wouldn't be caught dead saying that.
Well, that's reasonable but 10.4% in three years seems pretty big: it is past "immigration" and all the way into "all of the conspiracy theories are true" territory.
> Translation: The announcement itself is a measure of how unpopular he is and how desperate our liberal party is to win the next election, not that Canada is "righting the ship".
The bae.st media import is actually running on a CM-4 and the actual bottleneck is the disk and it's chugging but I just sort of took it as a given that this is something I have to fix. There was an instance running on a Switch for a while, and I'm sure you're aware of mint's antics. lain cares about that kind of platform, so it's nice that lain is around.
> ask me how I know he doesn't test shit before pushing updates.
"there isn't a Pleroma instance that exists which cannot handle the load on available hardware" still irks me because it means that the person that wrote it was ignoring the performance issues that had been reported in the bug tracker as well as in messages on fedi. (I don't think most people could have convinced Pleroma to stay up when subjected to FSE's load.) I guess nothing has changed since FSE's last merge with upstream.
Resident hacker, leader of the fsebugoutzone.org coup of the FSE Autonomous Zone, BOFH of freespeechextremist.com, and former admin of FSE before the establishment of the FSE Autonomous Zone. Launching a guerilla war against myself from this bunker.I'm not angry with you, I'm just disappointed.I am physically in Los Angeles but I exist in a permanent state of 3 a.m.I have dropped a bytebeat album, feel free to DM me for a download code or a link to a tarball: https://finitecell.bandcamp.com/album/villain . There is a chiptunes album there, too.Revolver is coming: https://blog.freespeechextremist.com/blog/revolver-kickoff.htmlWar has changed: https://blog.freespeechextremist.com/blog/update-and-roadmap.htmlThe usual alt if FSE is down: @p@bae.st or @p@shitposter.world.