In many ways, Mastodon feels like rewinding the clock on social media back to the early days of Twitter and Facebook. On the consume side, that means that your home feed has no algorithm (this can be disorienting at first).
Practically, it means that you see only what you want to see and only see it linearly. You never wonder “why am I seeing this and how do I make it go away?”. Content can only enter your home feed via your followed tags or handles and the feed is linear like the early days of social media.
That was actually caused by using old import files.
I’ve made a ticket for the instance issue: https://github.com/laurencedawson/sync-for-lemmy/issues/421
re: “multi communities” I too think its best to wait for a proper lemmy solution here. The only other way I can think to do it is to manually call the posts api n times for each community. Its not going to be a good experiene.
re: hiding, the solution sync has now isn’t the best but I’m waiting for this to also be added on lemmy
re: web settings: there’s an open ticket for this and I’ve just marked it as high priority. I’ll try to get that added for the next release.
re: long pressing: there’s an open ticket for this too
re: negative #s: I’m pretty sure sync displays negative scores unless I’m missing something here?
re: low ram usage: I try to make things myself, don’t rely on libs and still use java!
So tl;dr most of your points are being tracked as open issues. I’ve prioritised a few and hopefully they’ll be included for the next release.
Thanks for the detailed reply!
I should have known… I suspected about it though.
Yeah, I also think it would not be the best experience… I only mentioned it because Summit has it and Lemmy needs to fix lots of more stuff first before adding new features.
I think it is not the same that I meant? I mean I don’t want to hide them entirely as you can with Reddit, I only hide read posts per session based (or that is what I want to accomplish), so what I meant was to be able to do this without hitting the hide read posts button too much.
It is very handy to handle all this client side because a simple refresh would bring back all those read posts hence you can see updates of such posts or whatever, as I’m using Lemmy implementation for hiding the read posts so I’m missing on that.
Hmm, it works for me with comments for sure, but posts all they stay at 0 votes, never -x
Should I interpret this as java being very efficient? 😅
Thanks for your feedback to my feedback dude! You are a pro!