Obviously we all should go back to the place we were before colonising any land. So back to single cell organisms of the sea. Hexbear and .ml people already have a head start.

I mean, what do you expect? Those two unwashed apes created Lemmy because no one wanted to listen to them on Reddit. Just try staying away from .ml, your online experience will be vastly improved.

If you fancy oversimplification, yes. Otherwise it’s of course more complex, but well, where’s the fun in that, right?

I don’t and I don’t want to, I hate it when everyone makes their own standard which means there is no real standard to speak of. There’s a xkcd exactly for that.

I’m using ActivityPub and that’s what I’ll be using as long as I feel it makes sense.

They could have made ActivityPub better, instead they made an incompatible protocol.

So it’s a centrally controlled network? That doesn’t really seem like proper federation protocol.

Or is it only to federate with their main instance? Meaning InstanceX and InstanceY can still federate with each other even without approval from the overlords.

Pressure your instance to join https://boost.lemy.lol and pressure your mods to add the community there (or you can add it yourself if the instance is already part of the project).

Not really that important, the first load might be really slow, but after that it should be smooth. The api responses will be slower, but it doesn’t matter that much.

Well, even if you ignore the author, the books are actually trash once you’re older than ~16 years (give or take a year or two). There are soooo many inconsistencies, that I could write like one full A4 page just from the top of my head (and I read it in 2007, so you bet I’ve forgotten most of it). I could write many more pages with some light Googling.

Should be simple to rewrite the bot to accept input from this! If you plan on doing so, let me know, I’ll add support for the applications table.

No idea, I didn’t do any api development with Reddit, it felt way too oversaturated already. But event subscriptions are a common thing for such use-cases, so my guess would be actually very similar to what I have created here with this package.

It’s not only for the Lambda use case, my main motivation was AutoMods - they are very resource intensive currently and need to run very often. What you needed to do until this package, was traversing all new posts and all comments in there to check whether they’re newer than the last post / comment you’ve moderated. Which is a lot of api requests every minute or two, you’re essentially DDOSing yourself. With this, your AutoMod receives the information that a new comment was created and you can fetch the comment in a single (relatively inexpensive) api request, instead of plethora of requests which are all fairly expensive.

Whether the webhooks feature is then exposed to other users is really up to each instance admins, I’m thinking of exposing the functionality for my instance’s users when I finish implementing all I have envisioned.

Of course bot authors can add support for webhook triggering which means the admins can then use it more effectively.

The real point here is that this kind of behaviour is one of things that made Reddit fucking awful and I’d hate to see it flourish here in the fediverse.

Too late, I’m afraid, it already does.

No moderation without representation. IOW: mods should be democratically elected.

Mod elections should be annual and no mod should enjoy that status for life.

There should be a mechanism for inducing a ‘no confidence’ mode election at any time otherwise the communities are likely to splinter into “real_” communities just as they did on Reddit which no community in the fediverse can currently afford.

How do you enforce this? You would need the admin’s cooperation. What if the instance admin is also the mod? If someone starts a community, is it fair to take it away from them, if you don’t agree with their moderation?

There really isn’t any way to prevent all this, it would have to be built into the platform itself and it’s too late to do that now. Furthermore, there are very few communities large enough for people to even want to vote for mods.

It needs direct access to the db, so in my case it’s on the same vm as my instance.

It theoretically could be done in the webhook filter, it’s a full (but limited) language, I’d just need to add support for some functions.

Those are not really webhooks for public use but for the instance admins, so filtering by posts mentioning Taylor Swift should be more than enough. But yeah, you can just send everything to your bot if it can handle that.

Well, it stays warmed up some 15 seconds or so, but the important part is you don’t pay for that uptime. And if my bots ever get to 100s of requests per second, I’m gonna have to shut them down, I’m not that rich.

This feels like a moot point. I promise you this is much more efficient than the rest of Lemmy is.

Pub-sub might work for some use cases, but it wouldn’t work at all for mine. I host my bots on AWS Lambda so I don’t pay for anything, unless the code is actually running. So the webhook essentially wakes the virtual machine up and after processing is done, it goes back to sleep.

Yeah, they make a new ongoing tls connection on every https webhook. Which doesn’t necessarily mean all db events, there’s quite powerful filtering available and everyone should use it, sending a ping for db events you don’t need to seems quite wasteful.

Yeah, everything you do takes processing power. This is done in a way that minimises the impact. There’s no insert-after-event that I’m aware of. Also I’m not sure what you mean by expanded.

Yep, it uses pushing from the postgres to the webhook processor instead of polling for data periodically by an app. So after every insert, an event is pushed using the native postgres listen/notify mechanism and then the webhook processor doesn’t interact with the database at all.

Well, there can’t really be a governing body, but we admins do cooperate quite a bit. For example, we use Fediseer to coordinate defederations with bad actors.

We also post spammers we discover on our instances for other admins to block as well.

[email protected] would probably be a better place.