The main reason I don't shut down my instance and transfer to some other one is because I don't want to cuck to some other admin. On occasion I do special shit on my own fork. For example, I put in a url field for scrobbles, which was accepted into Rebased's BE and into PleromaBE under a different variable name externalLink (don't get me started, the expectation that I rename it for them was retarded).
My FE displays it as a little icon. If you click the YouTube icon it will take you to the exact YouTube video I listened to it on. And yes, that link will change to SoundCloud or whatever else if I listened to it there.
Being free to do wacky shit like this is probably the main motivator to keeping my instance up. That and because it's cool.
The similarities between this and e-wignat Holocaust deniers is striking. It's extremely analogous. I think the main difference is that Holocaust deniers are right.
I still see them trying to paint Kyle Rittenhouse in a negative light. I think this plays into the efficacy of leftist lies in spite of how obvious they are. They just repeat them over and over again for literally decades until nobody knows the truth anymore
Just realized you can build top ten lists with SQL. Here's one for the top ten artists of all time:
pleroma=> SELECT COUNT(*) "count", data->>'artist' "artist" FROM objects WHERE data->>'type' = 'Audio' AND LENGTH(TRIM(COALESCE(data->>'artist', ''))) > 0 GROUP BY data->>'artist' ORDER BY COUNT(*) DESC LIMIT 10;
count | artist
-------+------------------
469 | OT the Real
440 | James Kibbie
278 | Jedi Mind Tricks
247 | Vinnie Paz
240 | e00
220 | Rippingtons
209 | Aesop Rock
204 | 2023
193 | Taylor Swift
193 | Outerspace
(10 rows)
I added WebScrobbler support but that's really not the same thing as a desktop program. So yeah. Maybe I'll have to write one for that. Which player do you like these days?
>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.
I want to write something to the effect of "all control flow is goto in disguise" but I'll spare you that rant. So yes, you should master the rules before breaking them, but most importantly, you should get shit done, which is something I think we agree upon.
>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 don't think it's necessarily a cultural problem, exactly. It's that they don't like microblogging. They want a chat room, which is a lot closer to a stream of consciousness in certain ways. Chat rooms are more conversational. Also we get on voice chat a lot, which is like a Zoom meeting except we're talking about cool shit and not gay shit.
>That is seriously awesome.
Thanks fam. IDDQD Magazine is a zine for guys who either use the 4chan blue boards, or would if they knew about them. That's the culture that informs it. It's interest-based, but it's still filled with the right personality types, i.e., ours. Or rather, the parts of our personality types that overlap. There is a particular focus on /tg/, though.
Currently, this publication pays, but it's truly a pittance. An article buys you a nice lunch, basically. The "vision" I have for this is that it has a variety element. The readership should have an above average intelligence, but we put in stuff from all kinds of different backgrounds. So imagine this:
You are a tech sperg, a hacker in the old sense of the term. You might get an article pertaining to that, but when you turn the page, you'll get something else. You'll get an article about something like, I don't know, the Las Vegas underground rap scene. Or some weird math geek shit about dice pools in TTRPGs and the expected number of successes on X dice with Y sides with a success threshold of A and an explosion threshold of B. Then you turn the page and you get some political-theological philosophy shit.
So it's not your, the reader's, wheelhouse, and it's not supposed to be your wheelhouse, but it's supposed to be comprehensible to you in spite of that without insulting your intelligence. If you were to write tech sperg shit, I'd try to get you to write it in a way that a clever automechanic could read and comprehend it without it reading like Newsweek slop. And then when you turn the page you might get something about why Funkwhale is a piece of shit from the perspective of someone who wants to jam on their guitar and upload it without getting a computer science degree's worth of knowledge to do so. Or why Paladins past AD&D 2e are literally demonic and you don't realize it because you're not a theologian.
And none of this is made-up. We already ran all that shit. And who knows what next. I literally paid my mortgage shilling this shit mid-2023 out of Vegas punk rock shows.
>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.
That's exactly the kind of experience I had, but I will admit I was trying to overcome it in this case specifically so I can get scrobbles off the ground on instances other than my own. And it worked. I won that battle. I'm not sure what client you're using, but if you're using the Baest website, you'll see my scrobbles on SJW's fork of PleromaFE.
>It's also possible to just not care if you miss some stuff on an imageboard.
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? I had the idea of writing a similar thing that checks obscure imageboards on your behalf.
The rarer a post is on those boards, the more inclined it should be to notify the user that a new one is on that board. A relatively fast board where a thread is likely to get to page 10 in a few hours might only notify the user when a thread hits about 100 replies, while slow ones that get one or two posts in a month will notify someone watching it literally every time anybody posts anything.
Smart post intervals, meet smart notify.
Never implemented it but it was a thought for a while now.
>Computer science only accidentally makes money for me.
I like building things with computers, and I'm much less ideological about it than your average tech sperg. I often joke that a lot of the software actually worth using and vidya worth playing is a bunch of dogshit spaghetti code written by some literal 12yo, and it's because said 12yo is motivated by accomplishing an outcome and not motivated by "clean" or "good" code. It's a perspective I stand by, not because my code is incoherent spaghetti garbage, but because I know the difference between inspired and uninspired work, and inspired work has a habit of not following rules.
>That's cool shit. I hadn't heard of it.
It's actually the original reason why I got this domain name. 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. I wanted my own instance not just to have one but as a stomping ground for my readership, who never got on fedi. 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.
I attached a few covers of the zine, which you can find here: https://iddqd.pub/
I'm considering doing a digital version because people are worried about doxing/opsec.
>The trick is to just not argue with them and if they insist on it anyway, have a robot disincentivize them.
Well, in this case, it was because they were a project maintainer and I was PRing them. I had the spec on my side but they had the merge button in theirs. I think you can see how this works out. Logos cedes to ethos in this fallen world. RIP in pepperonis mi amigo.
I always liked the idea of smaller imageboards but I had a hard time keeping up with all of them. Maybe I should write a client that keeps a thread watch list, kind of like 4chan-X does, except I can use it on a variety of imageboards (maybe of which likely run LynxChan or something)
I'm just glad that I (mostly) stopped with the tech sperg shit for the time being because I no longer find it terribly fulfilling, and it's partly due to this kind of shit. Running a larger instance just sounds like it's all-pain, no-reward. At least, that's my impression from the outside looking in.
The last thing I did relating to that has all been about MUH SCROBBLEZ, which is a creature comfort and not that critical, and that was a pain in my ass for social rather than technical reasons. It's cool, but if it goes away it's not the end of the world, it's just dumb on the part of some project maintainer. I got native Pleroma support into WebScrobbler and PleromaFE to display the most recent one under people's usernames. Rich presence is neat, but that's all it is.
I've been working on my print magazine and the technicals of that have proven to be much cooler. 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. It's much more hands-on. On top of that, the act of generating actual content has proven much cooler to me than arguing with other tech spergs about non-issues like if a field should be url or externalLink.
Honestly I think my use of fedi might gradually shift to just running little single-user instances, or smallish ones that I just use to post about my other projects. 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, the backups are an anti-jannying measure, it's not about managing system resources and keeping a box up. The point raised is that having to maintain the hardware can get expensive in terms of your time, whereas if you're a VPS fag you can throw money at the problem.
That being said, it sounds like the system you're running demands a lot more resources than mine, so maybe the VPS game gets untenable past a certain point (I'm nowhere near that point)
I don't want to maintain hardware for this reason. But I also don't want to cuck to VPS hosts, since if they ban me I lose my data. I found the ideal compromise: daily backups.
I have a cron job that runs every day to pull all the shit updated since the last time it ran. I specify this because sometimes the computer running that cron job is off for whatever reason and so a day or three are skipped. But it pulls the changed data from all those days.
So if the VPS host jannies me I'll either make a new account on it or just find another VPS host, and do the same thing. I keep all my data and they have to maintain the hardware to make my shit run.