subtype, 4 months ago

@eris Actually, nodeinfo shows that, like here: https://mastodon.social/nodeinfo/2.0

Maybe it would be possible to get this information from the nodeinfo part of the Instance object in an MRF and reject that way. I’ve once made a MRF that auto-delisted posts from vanilla masto, and it shouldn’t be that hard to query a different part of the nodeinfo and reject instead. Just a fair warning that I had to disable this as it broke federation on my instance, but maybe someone with better Elixir skills could chime in: https://forge.insufferable.tools/subtype/akkoma/src/commit/ced1fb99d4fbf197069613de504d89617972af11/lib/pleroma/web/activity_pub/mrf/force_mastodon_unlisted_policy.ex

Ukko, 4 months ago

@subtype @eris how did it break the federation? I don't remember

subtype, 4 months ago

@Ukko @eris Only with masto, I couldn’t follow anyone or fetch posts; I thought I got blocked again until I figured out that it was because of my own MRF. Though if one actually wants to block then it might be ok. Still, I think writing MRFs while not understanding what’s going on there might be a bad idea :ablobcatsweatsip:

Ukko, 4 months ago

@subtype @eris weird shit i guess maybe there's a crash/inexhaustive pattern match somewhere that erlang just hides nicely

subtype, 4 months ago

@Ukko @eris The main problem is that it was literally the first time I wrote any Elixir and I had no idea what I was doing.

Ukko, 4 months ago

@subtype @eris yeah i have no idea what's happening either