Are you getting black screen? Seems device adaptation specific bug, the post you linked works on J2
But most likely a longer one (or with more pictures) will also bug out on it
But most likely a longer one (or with more pictures) will also bug out on it
I caught it again.
The duplicates are not always next to each other. Last time, I had more (two?) duplicate threads and the duplicates were further apart, not next to each other; some other threads were interposed between the duplicates.
1 Like
The chain of replied-to posts is completely busted.
The correct chain can be accessed in the browser, but the forum viewer gets confused.
No, not a black screen, the text vanished and you only see an empty dark window with tge swipe dot in the upper left.
Thanks @szopin for merging my contributions!
I’d like to explain a bit how the drafts feature works:
- drafts are saved locally, and not synced with the forum
- drafts are saved after 13 seconds (most of the time, if the text seems worthy ro be saved
). Why 13? Because 13 is prime. - they will be loaded if you reply to the same user, topic, and post.
- drafts are kept indefinitely, unless you use the pulley menu in the post editor to delete them. Which is recommended to do from time to time.
- The draft of the “current” post or reply is deleted when the post or reply is submitted.
- There is some very basic obfuscation done on draft text, and the post they correspond to when saving. But it is using insecure storage (dconf), and the obfuscation is reeallly easy to figure out. Be wary of sensitive information in drafts.
The other features in 1.16:
- Categories can now be tracked, followed, ignored,… like topics.
- As there is RSS available, you can now get a link to that from the category page. Very handy of you want to follow the forum from elsewhere.
- In post composer, you can now display the post you are replying to from the pulley menu.
And if you like RSS, check out @abranson 's work at GitHub - abranson/sailfish-account-rss: Sailfish RSS event feed plugin · GitHub
12 Likes
Everything sounds good, except the 13 seconds delay, which is completely puzzling to me.
Why have a delay at all?
Why is it time-based instead of content-based?
Why not just save the draft immediately when the user types the very first character?
Why confuse users with hidden behavior which is not at all obvious, and which will inevitably make some users think the drafts feature has a bug where it sometimes loses the text?
Because it writes to the filesystem and you don’t want to write the dconf database on each character typed.
If there are issues arising with this we can change it, for now it is what it is.
2 Likes
The updated version is also in Store now. @nephros, please stop being so productive and go enjoy summer!
14 Likes
1 Like
“Omega 13”
Also, in-thread read position seems now synced, Or?
Great new feature too!
One more brick added, to make our phones closer to PC replacement (+new glasses for me)!
Less heat, less consumption, less equipment, lightweight backpack, nice!
Thank you @nephros for your big multitask work and @szopin for this app.
1 Like
I just tested the drafts feature and it’s awesome to not be scared all the time of losing everything you wrote.
Thank you!
But, how exactly does the draft feature work?
Does it save the text every 13 seconds or what?
Some sort of time indicator to show when the next save will occur would be useful.
In one of the tests I lost some of the text when I left the post and then came back to the draft.
Also, the status message seems to remain stuck at the moment of the first save (if the post is new) or at the time of the load of the existing draft (if a draft exists), so the user cannot know when the last draft was saved.
EDIT:
Ok, it happened again and this time it was not a test.
I had just started writing a post, I immediately remembered I had to get some more info from a previous post, so I exited the post probably before the 13 seconds mark, so there was no draft when I came back
This is annoying.
I don’t understand why such an arbitrary limitation is needed.
Overwhelming the system by saving on every character is not a good argument.
If the hardware or software gets overwhelmed by the pathetic typing speed of a human, we are in big trouble technology-wise.
Also, the official notes app doesn’t have such arbitrary limitations.
I had to post that message twice, because the first time no new post was created.
Fortunately, the draft was still there when I tried replying the second time.
Don’t know if this was just a fluke or this issue can be reproduced easily.
Apparently there was already a bookmarks feature.
Don’t know if this is a feature of the forum itself, or a feature of the viewer, but it works well once I figured out where to find the bookmarks (they are hidden in Notifications → Bookmarks ).
1 Like
I just saw this happen in the Browser version!!
I conclude that this is a glitch in the Forum software, and it’s not the fault of SFOS Forum Viewer.
1 Like
Thank you for locating it! My attempts all failed 
Anyway, if I may have a small request to @szopin, please add remorse timers where possible and viable. For example, I tend to select by mistake the pulley menu option to bookmark a thread instead of inserting quote and it is then quite difficult to unbookmark it. Just an example, there are numerous other options which would benefit from having remorse timers allowing to quickly undo (and similarly quickly accept) an action… TIA!
1 Like
I wonder whether it would make sense to swap the Categories and Notification UI options.
Have Notifications (and the stuff that is accessed from there like PM and indeed bookmarks) on the right page, and delegate Category selection to the pulley.
And maybe eventually end up with a carousel type UI where you just flip through all these pages by swiping to the right.
1 Like
I’d prefer having categories on the left page, like in quickddit.
3 Likes
I don’t know whether it’s always been this way, but it seems topics are treated as “unread” if any of the comments are edited?
Here’s an example:
It’s an ancient thread, but post #3 was edited recently:
Is that desired behavior?
Sounds more like the recent sync function, discourse is reporting you have lastread post in the middle of that thread, so it now highlights it even if never opened in app
Edit: wait, it’s not ancient, it’s a recent split from an ancient thread, yeah idk