Notices by :p: (p@bae.st), page 12
-
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 10:01:39 JST 
:p:
@graf
> checking the user agents in the poast nitter logs almost 95% of them haven't updated
Looks like about 5,723 are on 4.2.7, out of 11,497 active Mastodon servers, so almost exactly half. See attached.
masto_servers_by_version.json -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 10:01:37 JST
:p:
@graf Love me some awk. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 10:01:35 JST
:p:
@graf Lazy motherfuckers gonna get their IP ranges banned before they even start trying to use actual UAs. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 10:01:34 JST
:p:
@graf He didn't seem like he regretted doing it, he seemed like he was annoyed that he wasn't getting it for free. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 09:06:21 JST
:p:
@i @NEETzsche @dcc @graf @r000t @tinfoil-hat who the fuck is nixlon -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 09:06:00 JST
:p:
@i @dcc @NEETzsche @r000t @graf @tinfoil-hat Looks like they fixed some of the problems, a lot of the commits are related to bans. :nixlonlol: -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 08:58:00 JST
:p:
@NEETzsche @r000t @graf @tinfoil-hat
> Remember how I wrote a script that pulls images from 4chan and posts them on fedi, but calculates how often to post new ones based on fedi user responses and the "speed" of the board?
Yes. I liked the algorithm but perhaps not the mission.
> A relatively fast board where a thread is likely to get to page 10 in a few hours
It's like trying to have a conversation with someone in the little chatbox on a stream. Slower-moving boards are more interesting, and they discourage spastic bullshit.
> Never implemented it but it was a thought for a while now.
It's not a bad idea. Couldn't be that hard to bash something out. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 08:53:35 JST
:p:
@NEETzsche @r000t @graf
> it's because said 12yo is motivated by accomplishing an outcome and not motivated by "clean" or "good" code.
This is one of those things that has something to it as long as you are not taken literally, which you inevitably will be. (Cf., Moore's Law, Postel's Law, 90% of anything that Fred Brooks wrote.)
I've read what James Hague has to say about it, and he has a lot of very good points. (I have probably pasted a lot of URLs for his articles at you.) On the other hand, he's a game developer (and thus has a radically different lifecycle for his code than he would if he wrote distributed software) and I am old. (Maybe not as old as he is but old enough to know what I'm doing.) What constitutes "good" from my perspective is driven by practicality rather than some fantasy a dude has in his 20s about what constitutes "good" code. The young guy will write 10k lines of "clean" C++ to accomplish what an awk one-liner does, he's got no scar tissue and is prone to compulsive masturbation (technical and otherwise). VCs love this because in their view, either the market is cornered or the business is a failure, so they turn everything into a moonshot because a VC makes way more money with one unicorn and ninety-nine flops than with a hundred sensibly run modestly successful businesses.
"Good" in my case is informed by having run Pleroma for years and knowing the shape of fedi traffic and what is fast and what is slow and what should be faster and how to handle that, knowing what sort of things I want the software to do, knowing the general shape of the unknown unknowns you run into with stuff like this, and knowing the process of long-term maintenance and debugging a network, which is different from spot-welding a feature.
> inspired work has a habit of not following rules.
You've got to master the rules before it's meaningful for you to break them. A kid shoves a goto into a function and the code is worse; Ken puts a goto into a function and the code is better, and there's a good reason why. Arthur Whitney dispenses with line breaks and his code is densely packed and nigh-unreadable even to an experienced hacker, but the reason he does that is different from the reason a clown does it. An idiot breaks the rules and you get Clerks, a genius breaks them and you get Waiting for Godot.
> IDDQD was supposed to be a publishing house, but the early 2020s happened and I ended up just being here. It was initially a paid blog in 2019 but we shifted from that into print media, and only got our first real issue out in early 2023.
Oh, that's cool shit. Congrats!
> They never got on fedi because they regard it as a Twitter clone, and they all hate Twitter. So my entrenchment in fedi is kind of an accident in other efforts.
Ah, yeah. I think most of the things that make Twitter hellish don't apply here, but I can see it leaving a bad taste in someone's mouth.
> I attached a few covers of the zine, which you can find here: https://iddqd.pub/
That is seriously awesome.
> Well, in this case, it was because they were a project maintainer and I was PRing them.
Yeah, usually when that kind of thing happens, I just leave it. There's enough work to do without wasting time: ultimately, they'll do what they want with the project and I've sent my PR and I'll make adjustments if they want adjustments but if they don't like it and we can't work together, I should probably do my hacking elsewhere. Sounds like you had the same kind of experience. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 07:17:26 JST
:p:
@mint @NEETzsche @r000t @graf Also pretty easy to do ad hoc connections. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 07:12:47 JST
:p:
@NEETzsche @r000t @graf @tinfoil-hat
> I always liked the idea of smaller imageboards but I had a hard time keeping up with all of them.
Well, there's the federated one, I forget what it's called.
It's also possible to just not care if you miss some stuff on an imageboard. You feel like $x, wander by image board $x. When I moved from 4chan to 711chan, it was nice: you could post something on /g/ and it would still be there when you felt like checking in again after a week. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 07:02:25 JST
:p:
@NEETzsche @r000t @graf
> I (mostly) stopped with the tech sperg shit for the time being because I no longer find it terribly fulfilling,
Computer science only accidentally makes money for me. I like building out machines, reading research papers, making beautiful solutions, bashing out quick solutions, rattling off stunt-hacks, analyzing data from prototypes, diagnosing and fixing bugs. It's like music, but I can expect to make money doing hacker shit.
> Running a larger instance just sounds like it's all-pain, no-reward.
It's nice to give people a place to be, you know? Gives a fella the warm fuzzies. It is a huge pain in the ass and especially if you take a somewhat aggressive stance about one thing or another (e.g., freedom of speech) you kind of invite people that hate it or think you're doing it wrong, but definitely worth it. (I mean, still spending my money and time and effort on it, you can reason I think it's worth it.)
> I've been working on my print magazine and the technicals of that have proven to be much cooler.
That's cool shit. I hadn't heard of it.
> The technical problems you run into with that tend to revolve around much "realer" things, in terms of physicality. Paper jams. Paper cutter blades getting dull.
Oh, yeah, that's one of the things I like about not being on a VPS or a managed dedi, or doing RF stuff. But that's still circuits, it's not like printing or doing, like, woodworking or cooking or growing a field of corn. It's a completely different thing.
> much cooler to me than arguing with other tech spergs about non-issues like if a field should be url or externalLink.
The trick is to just not argue with them and if they insist on it anyway, have a robot disincentivize them. I like talking hackery but low-quality arguments about shit that doesn't matter are probably the most boring thing imaginable.
> And I'll never have to deal with needing a six million terabyte RAM computer, even if that accounts miraculously gets thousands of followers.
Well, you know my solution to that problem. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 04:45:46 JST
:p:
@NEETzsche @r000t @graf
> having to maintain the hardware can get expensive in terms of your time
Except that I got a refurb that turned out to have a flaky mobo, the hardware has been less of a headache. VPSs get weirdness around I/O performance, network performance. VPS hosts get DDoS'd for reasons unrelated to anything you're doing, like when the Ethereum fork happened, people DDoS'd a lot of Ethereum nodes (for voting "wrong") on Frantech, and sharing a pipe with other tenants meant that was a problem. For example, FSE had split app server and DB server early on (the isolation was worth it almost immediately) but the DoS targeting Frantech meant that people were registering VMs just to DoS from the inter-VPS network and FSE couldn't get to its own DB server. All those headaches go away if you just have a computer and you run your software on a computer.
> maybe the VPS game gets untenable past a certain point
Yeah. At this point, system requirements exceed what I can throw at a VPS. It's hard to come by a dedi with enough RAM. Anyway, gradually acquiring replacement hardware, but with requirements designed around different software. :ocelot:
Plus a much nicer BMC (Linux-based, stable), better load-balancing setup, nodes instead of VMs, etc. It'll be a few weeks before I've got all the necessary gear together but I intend by then to have an alpha-quality build ready to run on it. If I'm lucky, I'll also have a couple of the nodes running Plan 9, which should eliminate a few headaches. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 04:45:06 JST
:p:
@NEETzsche @r000t @graf
> I found the ideal compromise: daily backups.
Don't get me wrong, backups are great, but the issue isn't the data. It's difficult to replace a machine big enough to run FSE. The box that blew up has 384GB RAM, Postgres on its own NVMe, and even then, FSE required a lot of tuning to keep up with the traffic. We were right about at 10m notifications, for example, DB is 500GB on-disk, I'd sloughed off all the media storage to Revolver. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 04:44:13 JST
:p:
@NEETzsche @r000t @graf Box blew up, have replaced a large number of parts. Gonna get some new hardware, just bring it back as Revolver instead of trying to acquire another machine with enough RAM to handle FSE with Pleroma. -
:p: (p@bae.st)'s status on Saturday, 17-Feb-2024 02:58:16 JST
:p:
@colonelj
:rorshachsmug: A schizo died tonight. :watchmen: -
:p: (p@bae.st)'s status on Friday, 16-Feb-2024 17:45:29 JST
:p:
@mtr @kirby @Nitrohine @concury_
> my main source of "pleroma is made by the right" is mostly the akkoma blog that explains why akkoma exists,
The blog post was somewhat distorted and the main thrust of it was directed at the devs that let Gleason (an alleged "male feminist") contribute. He was somewhat divisive for his constant anti-trans posturing and he was banned from the project for unilateral merges and throwing tantrums on the gitlab instance. Nevertheless, FloatingGhost took the opportunity to throw the Pleroma devs under the bus, and manufactured "activity" mostly by merging in more dev branches while manufacturing notoriety by making claims that she knew to be false. And here you are, spreading the false claims, because it's what was written in the brochure. It is completely fucked up to lie about people this way, but it is as bad to repeat this kind of thing without knowing what you're talking about: you are contributing to a smear against people that you do not know and have never talked to.
Neither of the forks of Pleroma are good. Akkoma is an ideological fork based on a manufactured controversy with CADT-style code, and Soapbox is a bad clone of Twitter's UI maintained by someone who doesn't understand the backend he forked. Pleroma has been developed very thoughtfully and is good software produced by nice people that are clearly too classy to shit on FloatingGhost or Gleason. (I'm happy to shit on either or both of them, though. My source is "I was there and I know all of the people involved" rather than "I saw a blog post".) -
:p: (p@bae.st)'s status on Friday, 16-Feb-2024 16:18:45 JST
:p:
@phnt suya.. -
:p: (p@bae.st)'s status on Friday, 16-Feb-2024 13:50:31 JST
:p:
@irie @sjw @MK2boogaloo @syzygy :yaranaika: -
:p: (p@bae.st)'s status on Friday, 16-Feb-2024 13:50:25 JST
:p:
@berkberkman @sjw @MK2boogaloo @syzygy He had to fight the king of the hobos. -
:p: (p@bae.st)'s status on Friday, 16-Feb-2024 13:29:17 JST
:p:
@sjw @MK2boogaloo @syzygy It's the only one I have!
All ０７６萌ＳＮＳ content and data are available under the