> but what if with time my pets will become a cattle? I will need to rework everything, then.
You don't have cattle yet, you a pet. Don't neglect real pets for hypothetical cattle. If you wanna learn how to do Ansible stuff and you use a fedi instance as a practical project, that's fine, but it's not something you need now with one machine and might not ever be something you need. You need to know what the load is gonna look like.
A lot of things were built into Pleroma around some anticipated usage patterns that didn't turn out to happen, and some other usage patterns that ended up real didn't get accounted for. For example, hellthreads. Nobody expected the naturally occurring hellthreads to have as outsized an effect on the network as they did, let alone that there would be people that make hellthreads for fun. So there was an accidental DDoS: https://git.pleroma.social/pleroma/pleroma/-/issues/2765 . The problem was that a message gets rejected by the HellthreadMRF, but that message is a reply and has replies, so Pleroma queued those up to fetch. Since it dropped the original post, and it's a reply to the parent post, the parent post gets rejected and the first post is queued up again. So it walks up the chain and back down, repeatedly fetching the same objects, then rejecting them, and every instance that tried fetching that post did the same thing.
It's very difficult to anticipate a problem like that: it's difficult enough to detect it. All I saw was that any time I clicked "Like" on a post in the hellthread, FSE started getting hammered, I realized it was my friends' instances that were doing it, this took a while to figure out that it was due to the length of the thread and the mismatch between FSE's HellthreadMRF threshold and the other instances', and then it took a while to verify this.
Because instances tend towards idiosyncrasy, you're going to run into weird shit on a frequent basis and it's going to be difficult to generalize or anticipate. You want to just keep an eye on what is happening and whether or not the thing that is happening is causing a problem.
@anonymous Oh, hm, Akkoma. Not recommended, but your call.
When you say "no federation", you're getting the checkout error? Some of the things I have said would make less sense if we're talking about Akkoma rather than ActivityRelay. The checkout error makes more sense. Is it able to talk to the DB properly?
> Akkoma apparently comes with pleroma, at least that’s what I was told.
Akkoma is a small fork of Pleroma; it's less that it comes with Pleroma as it just is Pleroma with a different name slapped on it and some changes. Some of the changes are just merging in-progress branches, so in general it's a little less stable. Case in point:
> I am getting an arithmetic error when I try to search though:
I've not seen that and I do not know how much I can say about Akkoma. It might be fixed by running a different (newer, probably, but maybe older, who knows?) version of Postgres, or maybe there's a bug in their code that turns the search queries into SQL.
> I also get a strange Can't find LRDD template warning when I attempt to talk to certain instances.
I am not sure what that is, but error messages in this codebase are useful for finding out why some problem is happening; if there isn't a problem to diagnose, then the error isn't a problem.
@Inginsub@dcc@mint@sysrq Shit, seriously? Shit, that is rough. Raw or does stewed spinach do that too? Because I think I can eat an entire pound of stewed spinach, I'm pretty sure I have before.
@pwm@dcc@mint@sysrq It turns out that forensics labs are really good at detecting poisoning by this kind of strategy.
But @Inginsub is correct, it's cyanide rather than arsenic. I think the reason I remembered arsenic is that Turing died by eating an apple that had arsenic contamination. (Generally believed to be a suicide.)
@PurpCat@dcc@mint@sysrq Yeah, her last "quitting fedi forever" lasted two months. "I'm changing my password to something random and then logging out forever!" and then she's back. I don't know, she hasn't caused any trouble that propagated to this region since she quit fedi forever (again), so I'm happy to not turn over that rock.
@mint@dcc@sysrq You've got to rupture the seeds. If you eat the seeds whole, they're indigestible, they just pass through, but if you grind the seeds up, you'll get ill.
> "People on this server want to point out a retard" ∈ "People on this server want to see this"
Sure. It's a dumb reason, it creates drama, reaction-spamming is not the best way to do it. The premise, though, was a person that spams them without reading the posts. It doesn't matter which person did it, you've seen people that do that.
> How American of you!
It was an accurate analogy. The hugbox places only eat candy.
> Small amounts of poison might bring immunity to larger ones.
Apples contain arsenic in trace amounts, and a large amount in the seeds. A trace amount goes unnoticed, but a small amount of arsenic gives you scaly skin and cognitive problems until it's flushed rather than arsenic-immunity.
> Posts that fit his criteria of being manipulative or trying to pass emotions as objective fact.
Sure, but he also would go on tears of just smashing the big red X. Anyway, it's not really about Eris: Eris was mentioned just as an example, "There are people that do this, remember this guy?" Which one he used for which doesn't matter.
> I don't, I simply explain my disagreement.
If we've already been through this and we've both heard the other's thoughts on it, we could talk about something else.
> Maybe the public ones. I stopped using them once there were too much g*rmans on TWKN to mute.
Reasonable.
> I'll test it once Frantech's upstream stips shitting itself. Remind me if I forget.
At least one of us will remember. My test was essentially a handful of attempts to figure out why it was that a post federated. Invariably, if there were no people following the poster and no visible likes/reposts, viewing it on the origin instance resulted in finding a previously deactivated person reposting it. So the test would be something like following a user, deactivating without the undo of the follow propagating, and then having an announce from that user propagate to the server where they're deactivated.
> It still has to fetch the referenced object.
Sure, which is why I say I can't do anything about the problem this creates for the network, only the problem that it creates in the UI.
BOFH of freespeechextremist.com, and former admin. The usual alt if FSE is down: @p@shitposter.club, and others. I am no longer the admin. FSE has no admins now. Welcome to the FSE Autonomous Zone.I'm not angry with you, I'm just disappointed.I am physically in Los Angeles but I exist in a permanent state of 3 a.m.I have dropped a bytebeat album, feel free to DM me for a download code or a link to a tarball: https://finitecell.bandcamp.com/album/villain . There is a chiptunes album there, too.Revolver is coming: https://blog.freespeechextremist.com/blog/revolver-kickoff.html