Fediverse

I'd love it if the API that exists was more reliable... It's getting better, but the amount of basic features that didn't work (usually without specific combinations of params or unknown ranges, but sometimes not at all) is pretty crippling. (If there's a central place of discussion, I'd love to hear about it...I don't speak rust or flutter, but I've had to muddle through source several times)

I've never done anything as a mod so I have no idea what kind of tools they need, but I noticed enough basic parts to build all sorts of things.

There's definitely no reason to build it into the core though... Why put it on the machine busy serving everyone? You could do stuff so much cooler if you offload it... Like you could track mod actions against users/communities/servers, give a sample of random posts across their vote distribution, show the top few communities they get down voted.... All things psychotic to even consider in the core right now, but a reasonable project for a separate system

And since you seem like you'd get it, I want to share a win I made today. I've got a lemmy app I want to mix feeds (including between accounts and servers) to make a unified feed algorithm on your device. I also want it to support kbin, and maybe more... I took a couple cracks at it and charted out several designs, but I was getting too deep into abstraction.

Today, I finished working on a ridiculously generic abstraction layer - it handles not only tracking pagination, buffering, and preprocessing, it also enumerates all of the options in the Lemmy sdk so I can auto magically build most of the controls when I update. It also disambiguates resources (and actors) across instances and could describe valid actions you can take on it (I think that might be too far, so I'm resisting the urge... This time)

Everything is done through the account level, everything knows where it came from and can call the API by passing itself to its account to be worked on. It's also neatly serializable, you just have to write one function to pull the next page, and the rest is just an absurd amount of generics

Now, if I can figure out how to translate all that into a usable UI, I'll be getting somewhere...

I just had to share that with someone who can appreciate crazy data flow, it's been in the back of my head for months and today (after pulling my hair out for an hour and realizing I was forgetting to actually pass the posts to the UI) it worked beautifully