2553

Dutch government starts own Mastodon instance as reaction to the instability of Twitter (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by quinten@lemmy.world to c/fediverse@lemmy.world

241 comments fedilink hide all child comments

https://social.overheid.nl/@beheerder

you are viewing a single comment's thread
view the rest of the comments

[-] maegul@lemmy.ml 5 points 1 year ago

ha yeah I remember that, that was fun.

Hey! I was trying to be vague and anonymous!! 😅

But yea ... totally with you!!

For those that don't know, this person is the author of https://fediversereport.com/ and posts here like this.

@fediverse_report@lemmy.ml ... you could add more links and what not to your bio here ... ?

[-] fediverse_report@lemmy.ml 2 points 1 year ago

haha well think it mostly worked :D

and thanks for the shoutout! I do need to update my bio and get proper accounts. For now just testing out the water a little bit, havent really fully decided on which server I want to pick. reason Im replying with 2 accounts is that federation between kbin.social and lemmy.ml specifically is still broken, couldnt even see your reply. Not sure how to approach that yet

[-] maegul@lemmy.ml 2 points 1 year ago

Oh wow. Didn’t know about the broken federation.

[-] fediverse_report@lemmy.ml 2 points 1 year ago

https://kbin.social/m/kbinMeta/t/173366/lemmy-ml-is-no-longer-shadowbanning-kbin#comments

seems like a side effect of lemmy devs being overloaded with info and messages getting on a long backlog

[-] maegul@lemmy.ml 2 points 1 year ago

Huh ... that's quite funny and unfortunate.

Curiously enough I've been ranting in some replies about how "The Protocol" maybe requires too much coordination at a software level for its promises of a distributed social network to be taken at face value.

This issue incidentally seems like a prime issue. Like, just looking at it naively, would it not be reasonable that at some level the protocol has some checks built into it such that an instance either is or is not federating with another instance and determining whether that is the case or not is straight-forward?

The arbitrariness of a service called kbinbot being a whole instance's federation request service and the ability to block that by accident without any more declarative data structures verifying or identifying whether federation is successful ... that all smells like a bad system.

I'm starting to wonder if there's something to my "concern" compared to other protocols (wish I knew enough to seriously examine it).

I'll stop ranting now ... glad lemmy.ml and kbin are connected again.