this post was submitted on 15 Jul 2023
21 points (100.0% liked)
Thunder App
2772 readers
5 users here now
An open-source, cross-platform Lemmy client for iOS and Android.
This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.
Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.
If there are any developers who would like to contribute, feel free to reach out on GitHub!
General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link
Android Releases
IzzyOnDroid: Link
Google Play: Link
iOS Releases
Apple App Store: Link
TestFlight Beta: Link
Related Communities
Nightly Community: Link
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The Connect app can block instances. I don't use other apps for Lemmy at this time so I cannot vouch for the others and if they have this option.
Thank you!!! I'll check it out, but I do hope Thunder implements it as well.
You're welcome.
Agreed that the other apps could s̶h̶o̶u̶l̶d̶ eventually add this as an option, though.
They really shouldn't, until lemmy itself adds support for this. Adding it on the app side, will mean it only works in that one app, and does so in a way that's inefficient and hacky, and will break when the feature gets actually added to lemmy.
(Connect is likely filtering out everything from an instance, while actually still loading all those posts, so it looks like you blocked something, but actually the app is just not showing those posts) @gon@lemmy.world
The point is to ɴᴏ ʟᴏɴɢᴇʀ sᴇᴇ ᴀɴ ɪɴsᴛᴀɴᴄᴇ ɪɴ ʏᴏᴜʀ ғᴇᴇᴅ so if hitting that little option that says, "BlOcK iNsTaNcE" Does its job, "filters" Or not, then it's mission accomplished. If by your POV that isn't good enough for you, then you need not use the app and are likely not doing so already.
I fail to grasp your gripe here.
It puts extra load on the lemmy instance, it puts extra load on your phone, it puts extra load on your connection. It's extra work for the app devs (which I'm one of btw). I'm not against the feature, I'm against it being implemented in a way that's stupid.
Worst case scenario, would for example be a user blocking lemmy.world. As the largest instance by far, your device would then be loading almost twice the amount of content needed at twice the speed, to display one "page's" worth of it. This fills up ram, this makes the app slower, this makes lemmy slower.
If everyone using lemmy were loading in everything just to look at half of it, the already limited server capacity WILL suffer. All clients implementing this type of "blocking" feature would be like a mini DDOS. Hence, it should NOT be encouraged even a little bit.
I see your point... It's still incredibly annoying though. I hope Lemmy implements this ASAP.
With that I will agree. Users should really be able to pick both what instances, and communities, they want.
Though, now that I thought about it some more, there might be a good way to do it in an app. By allowing you to automate blocking all the communities on an instance. This would still not block that instance forever, new communities on it might show up. So it would be like a poor-mans instance block, but it would allow the filtering to happen server-side, and get around the downsides of client-side blocking.