Anyone know what's happening with this-week-in-neovim?
https://sh.itjust.works/post/3071162
Anyone know what's happening with this-week-in-neovim? - sh.itjust.works
Seems like TWIN’s site (https://this-week-in-neovim.org/
[https://this-week-in-neovim.org/]) is down - the dns doesn’t resolve. IIRC the
author was moving away from neovim and was having some maintainence issues, but
I’m curious if anyone else has more info .?
A Solution for Questions of Defederation
https://sh.itjust.works/post/461409
A Solution for Questions of Defederation - sh.itjust.works
There has recently been a lot of debate on defederation as a tool. In
particular, around exploding-heads and lemmygrad. I am somewhat in favour, but I
do understand the concerns of fragmentation (I’m not going to entertain the
“free speech” people). I think most people on here - or at least the active
commenters, which is a biased sample - don’t like the general type of content on
those instances and the communities they generate. This means, for instance,
most of us probably don’t want them appearing in the local and federated feeds.
However, the proposal for users to have to manually block those instances isn’t
really enough, because it means we all have to do this manually even if most of
the instance doesn’t want to propagate and elevate the content from these other
instances. What I think would be best is if/when Lemmy improves moderation tools
^.^. In particular, I’d suggest that we should push lemmy or actively develop
into lemmy (its open source after all) some way to stop either specific
communities or posts from entire instances from appearing in the main feeds,
while they are still accessible if specifically linked to or searched for -
“silencing”. One step above per-user blocking of instances, but still below
defederation. We could also say “members from this instance can comment but not
post” or other things to reduce the risk of hostile brigading and organising on
this instance while not directly hindering interoperability ^.^