Notices by NEETzsche (neetzsche@iddqd.social), page 15

It’s why they recruit for specific programming languages, like implying any SWE worth his salt can’t just learn a new one to get shit done.

I don’t really believe in relays at this point. It’s a thing I did and now stopped doing. There are other fixations I have less guilt about delving into, most notably muh scrobblez.

I’m thinking of exploring what I will call experimental Activity types. I want to bake things like board game moves and dice rolls into Activities which can be generated interpreted by a BE and interpreted by an FE more natively than just taking a content field at face value from a bot. But I’[m not sure I’ll find the time for it.

I did something similar when I first started, that was comparable to a follow bot, but quieter and less annoying to end users. I created relays everywhere my instance could, and it did so systematically: when it was processing an instance, it would hit /api/v1/instance/peers to look for more instances, and any instances therein that weren’t processed yet, went through this process. Then it tried to create a relay to it. My instance had literally thousands of peers in its list by the end of this. It functioned like a breadth first search, since it was queue-based and FIFO

This made my instance’s intake of activities pretty intense, but it was still manageable with my little shell script. I kind of regret doing this now, and in fact took some efforts to undo it, but the intake of activities is still pretty intense even now.

I write little shell scripts for memory leaks in Pleroma itself. I have one that runs every minute and sees if the CPU is at 85% or more. If it’s that way for 5 minutes straight, restart Pleroma.

The real chad move is to just have a cron job that backs up all your shit. That way, if your VPS host jannies you, you can just open up an account on another one – or shit, the same one – and start over like nothing happened lol lmao

I used to say that all podcasts fall into one of two categories:

• COVID/racism sermons
• Drunk jewnigger rants

But now, I think we need to add a third category:

• E-drama

I mean, it’s an e-drama podcast, strictly. How good could it have been in the first place?

@lain I mean my fork of Soapbox hazards a guess on if it should show a playing emoji or a pause emoji depending on if the time elapsed exceeded the length of the track since scrobbling, but it doesn’t stop displaying it even if the most recent one is from last year.

This is because, it’s a personal preference, I didn’t want them to just disappear just because they weren’t very recent. But I’m seeing that other people have an inverse preference. It’s not about how recent it is, it’s about if it’s current, if the user is playing the song right now or at least very recently.

Maybe we can find some reconciliation between these perspectives. For example, maybe the text can be very prominent, big, with colors that pop out at you when they’re currently listening to it, and then it becomes small, muted, when they aren’t. Think 16pt bold while playing, 8pt barely different from the background color when it was from last week.

This is of course just brainstorming

@marine @Kirino @Moon @lebronjames75 @why

You don’t need that. Also, this idea that the url field needs to refer to a URL that yields an ActivityPub Object JSON blob is incorrect. Even without offering a documentation of artist, title, album, and length, this line of thinking that it must refer specifically to what you think it should is not right.

The object is embedded in the returned value.

Try the id URL and not the object URL. It exists.

>It [Pleroma scrobbling] is broken

How is it broken? Show me step by step how to produce a bug in it lol. Things that work, aren’t broken, by definition. HARD MODE: find a bug in it that’s caused by my PRs.