The floating button is currently being overhauled which I think should make changing the position easier even if it doesn't support it out of the gate.
In the mean time, you could turn off the floating button for the feed view and instead use the feed button on the bottom navigation bar to scroll back to top. Bit of a hidden functionality :) Don't think there is currently a work around for the post view though unfortunately.
Hmm can't say I've encountered this myself. Have you tested Thunder with other Lemmy instances and had the same issues?
Yep, Thunder is checking for the deleted field in the comment thread but not in the reply modal. Will fix and try to get it in for the next nightly. As mentioned in another comment I made, Lemmy's API mark the comment deleted but still sends the contents.
This is also a reminder to be mindful of all comments and messages you make on Lemmy. They are not secure.
Oof good catch! But yeah as Qiqi said, Lemmy doesn't actually delete the messages. It just gets marked as deleted. It's then up to apps to hide it accordingly. Should be an easy fix, thanks for the find :)
Are you still having issues viewing community pages? If so, is it happening with all community pages? If the instance you're connected to is experiencing down time or having issues, it can cause that to happen.
Regarding posting, there should be a floating plus sign button on the bottom right of the screen when viewing a community. Alternatively there is a post button you can press when viewing community info accessible by the info button on the right side of the community banner. Hope that made sense!
Do let us know if you encounter any unique issues on tablet! I don't think it has gotten nearly as much testing.
The top left hamburger icon will open a side drawer that has a list of your subscriptions. You can scroll through that and click the one you want. Hope that helps!
Hello, comment context was my contribution :) Just a quick note, there are still some rough edges when interacting with comments from that context view. I have some fixes for them but they didn't make the cut off unfortunately. So that will definitely be improved in the next release.
I really like the idea of custom feeds made up of selected subscription groupings. Can't speak to if or when such a feature would get implemented. But regardless, if you have the time to open an enhancement issue on GitHub, we would greatly appreciate it!