Notices by :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)
-
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 01-Aug-2020 17:15:28 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: anyway, back to lurking again. bye -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 01-Aug-2020 17:10:10 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @bhtooefr @farhan
in our current global political climate, using the fediverse for anything requiring privacy is foolish. mastodon should either adopt E2EE without message franking by default, or drop the scopes. they are not remotely trustworthy, and every moment that they exist is begging someone to shoot themselves in the foot. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 01-Aug-2020 17:07:51 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @bhtooefr @farhan
that also requires competently managing the cryptography. instead, we get 'message franking' so that a user's client can become a decryption oracle (for reporting purposes, but will most certainly be abused by nation states and other adversaries in the future) -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 01-Aug-2020 16:52:58 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @farhan it's a problem if you expect scopes to behave as advertised, which they can't in a federated network -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 01-Aug-2020 16:45:49 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: by the way, that security hole is specific to Mastodon. Pleroma, Hubzilla and even GNU Social's ActivityPub plugin handle Reject Follow correctly in their default configurations. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 01-Aug-2020 16:41:43 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: oh hey, i'm back.
Mastodon has disclosed to its admins that a security hole where it does not properly handle `Reject Follow` at all.
however, this security hole has existed since 2018.
also, the "fix" is to patch every Mastodon instance, because yet again, the entire trust architecture of the fediverse is backwards.
here's the bottom line: any other peer you federate with can do WHATEVER THE HELL IT WANTS with your data. the fact that admins are having to scramble to patch is because the whole fucking thing is broken.
scopes cannot work as advertised, it's IMPOSSIBLE. you have to rethink this in terms of expanded collections instead of virtual collections.
and even then, a hostile node can choose to just not be conformant with the spec and publish everything it receives for the public to see.
but hey, keep playing internet feudalism with broken crap, i guess. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Sunday, 19-Jul-2020 03:42:48 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: anyway, back to lurking. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Sunday, 19-Jul-2020 03:37:02 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @flussence i'll come back to it after the current techbro interest levels burn out.
key points: reactive automation of moderation is important, and portable identity is far more important than "real" federation (or in other words, mike was right) -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Sunday, 19-Jul-2020 03:33:17 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @flussence as i keep saying, automation is the only way to have any hope of staying ahead of the shitshow. yes, automation can go wrong, but automation can be a huge win when it's working properly. enabling that kind of automation was the whole point of MRF. too bad it wasn't fully realized. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Sunday, 19-Jul-2020 03:31:34 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @flussence it's fine, just keep blocking instances or something. since really that's the only way anyone can curate anything. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Sunday, 19-Jul-2020 03:29:30 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @flussence i hate to be that person, but i warned *all* of these fuckers. they don't care. all they care about is DAU metrics. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 19:13:43 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @deavmi @sjw @HarneyBA @dee @velartrill @boob
i'm mostly uncaring, tbh. i just don't wish to deal with it personally. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 19:08:14 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @alex @HarneyBA @boob @dee @sjw
Mastodon can do that on 500MB, if you know what you're doing. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 19:05:52 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @deavmi @sjw @dee @HarneyBA @velartrill @boob
no. misskey is in nodejs because that is what the author uses. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 19:04:48 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @alex @HarneyBA @boob @dee @sjw
CPU time is the most expensive part. Many things downgrade to hash scans and seq scans because the indices fail to keep up. This is why "VACUUM ANALYZE" is a common suggestion for "fixing" Pleroma performance issues (temporarily). -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 18:59:43 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @alex @boob @HarneyBA @dee @sjw @velartrill
once a Pleroma instance starts scaling out, it is basically as much of a nightmare to manage as Mastodon.
managing pleroma.site is a nightmare, almost everything on the fediverse is actively federating with it.
when i handed it over to href, the database was almost 300GB.
whenever href updates the instance, it takes several days to run migrations.
it took several days to import too, when i handed it over. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 18:57:17 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @boob @deavmi @HarneyBA @dee @sjw @velartrill
Misskey looks like a very nice platform. I don't want to deal with managing a NodeJS service for my own personal use though. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 18:52:08 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @boob @deavmi @HarneyBA @dee @sjw @velartrill
they could have done that by simply prohibiting DMs from leaving DM scope. no need to add a new object type. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 18:46:33 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @boob @HarneyBA @dee @sjw @velartrill
well, you see it from the end-user perspective.
from the admin perspective, it is largely "why is postgresql pegging CPU again today? why are queries falling over again?"
and from the dev perspective, it is largely "maybe if we add emoji reactions, we can get users"
when i was running instances, i deployed a shared postgresql for them that had 256GB of RAM allocated for cache. that made Pleroma fast, but it's not realistic. -
:abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Saturday, 18-Jul-2020 18:42:03 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: @velartrill @HarneyBA @boob @dee @sjw
that is literally what i am building. also, the ability to make channels and identity portable (kind of like fedi, but done right).