Blocking instance does not save to settings
However, I was able to block in Voyager and have it appear and function correctly back in Summit.
Syndicated from the fediverse. Read and engage on the original instance.
View original on piefed.zipView original on piefed.zip
6 replies
Ive had the same problem forever.
I had to block each and every hexbear community manually as I saw them.
If you really want to block an entire instance, you can still use the web interface for your instance. I just happen to be testing 5 apps and reporting issues to help the devs.
well then, I'll just SHUT UP AND SIT IN THE CORNER!!!
Hope we're both joking. Forgot to add a smiley in my reply. 😄
Just saying I run 5 Fediverse apps and 4 Matrix because this is all relatively new, buggy, and mostly developed for free in spare time. So running additional apps and using the web are options until dev fixes.
we're both joking ;)
Ah, this one is for historical reasons. IIRC Lemmy did not always have the option to block instances so blocking instances are purely local.
That being said, blocking instances in Summit should work. It just won't sync to web or other apps.
There is actually some benefits to doing it this way as it's compatible across different backends as well (eg. Lemmy vs Piefed).
Maybe a more proper solution here to do check if the backend supports it. If it does, use the server side block otherwise use the client side one. I'll add it to the roadmap.