@wowaname @matrix @pea

but what is the issue? if some kid figured out how to yeet Pleroma instances, for example, that's something we need to know about.

@kaniini @matrix @pea guess you wont know

@kaniini @wowaname @pea He didn't say much

@matrix @wowaname @pea i'll just ping him in IRC

@p @matrix @pea @wowaname it's good to hear you've recovered from the outage. I was concerned that perhaps somebody found a way to yeet Pleroma instances.

@kaniini @p @matrix @pea well, technology found a way to yeet itself

@wowaname @matrix @p @pea

ah kinda like the outages I was having last month with my stuff that ended in a server literally catching fire due to mainboard VRM failure

@kaniini @matrix @pea @wowaname Oh, thanks, and nope, not yet. If it was something like that, I'd have an issue filed and the endpoint that triggered it blacklisted and I'd be yelling.

On the other hand, you totally could do that with an instance that had a large enough objects table and no rate limit on hashtag search. This is a thing I figure the relevant people know, though. If I'm wrong and it's not, I can scrub some logs and toss them out.

(I do have an FE patch and an FE issue, but my git.pleroma.social account went missing. I don't know if it got scrubbed or there was some data loss or what the deal was. I am not even sure that's what happened, just that I couldn't log in or get a password reset a while back and retried now and reregistering with the same credentials worked.)