Readeck turned one last month and there's a new release today 🚀
With progress tracking, colored highlights, new translations, layout improvements and other nice improvements.
https://readeck.org/en/blog/202501-readeck-17/
A big thank you to all contributors ❤️
Enjoy this release!
[#]readeck
=> More informations about this toot | More toots from readeck@mastodon.online
@readeck Congrats to the anniversary! 🎂🥳
And thank you for this awesome project!
=> More informations about this toot | More toots from johbrust@sigmoid.social
@readeck the upgrade was uneventful and quick, thanks a lot for your work on this 💜
=> More informations about this toot | More toots from xavier@pony.social
@readeck Congrats on the one year! Never realised its been 'only' one year. Amazing progress.
I upgraded to 0.17, but reading position doesn't seem to be saved. I also don't see the progress indicators on the thumbnails (as in your blog post), neither on existing nor new bookmarks. I double checked that I'm on this version in the documentation page... Is there anything else I need to do? Should I file a bug?
=> More informations about this toot | More toots from EFLS@mastodon.social
@EFLS could you check in Documentation > About Readeck that you're running 0.17?
What you're describing sounds like something I helped another user with yesterday.
If 0.17, then yes, if possible with logs and browser network activity :)
=> More informations about this toot | More toots from readeck@mastodon.online
@readeck Yeah it says 0.17 in the changelog on my instance. I'll see whether I can submit a bug report later today. I'm not familiar with this: what type of browser network activity do you need? And which logs?
=> More informations about this toot | More toots from EFLS@mastodon.social
@EFLS sorry for the lack of details :)
Open a bookmark and press F12 to open the console (there's a network tab). Then start scrolling and look if you see PATCH requests.
You can also press the read/unread button and see the same requests.
Back on the bookmark list, the indicator should be present
=> More informations about this toot | More toots from readeck@mastodon.online
@readeck Thanks for the details. Somehow, the issue disappeared.
Some details: I was reading on mobile Safari. Whenever I made a highlight, the page would scroll all the way to the top (although the highlight was registered).
Then, as I wanted to file the bug report and fired up Firefox on desktop, I noticed that the reading position of said article was saved.
And now I see the progress icons, and reading position is saved everywhere.
No clue what changed, but thought I'd fill you in.
=> More informations about this toot | More toots from EFLS@mastodon.social
@EFLS could be a cache issue. I don't know for Safari but Firefox for android seems very aggressive with its cache.
Glad it's fixed :)
=> More informations about this toot | More toots from readeck@mastodon.online
@readeck The loss of reading position bug seems persistent, but only on Safari. I've filed a bug report on Codeberg.
=> More informations about this toot | More toots from EFLS@mastodon.social
@EFLS thanks. Not sure what I can do since I don't own a mac.
I'll see if I can reproduce with a webkit based browser
=> More informations about this toot | More toots from readeck@mastodon.online
@EFLS I managed to reproduce the issue and had to go back one commit at a time to find the culprit :)
I'll push a fix soon and a patch release quickly thereafter.
Thanks again for the report!
=> More informations about this toot | More toots from readeck@mastodon.online
@readeck Wow that was quick. Thanks!
=> More informations about this toot | More toots from EFLS@mastodon.social
@EFLS due to a big incoming change with forms, I'm not going to publish a patch release but you can install a nightly with your issue fixed
https://codeberg.org/readeck/readeck/packages
Next stable release should arrive quite soon anyway :)
=> More informations about this toot | More toots from readeck@mastodon.online
@readeck Thanks, I just tested the nightly build and seems to work! Awesome, something like 24h after the bug report :)
=> More informations about this toot | More toots from EFLS@mastodon.social
@EFLS To be fair, it was easy to fix :) (took longer to find though)
https://codeberg.org/readeck/readeck/commit/55dc7bcddae05443010c4ad0b0e5b64a26910f0f
=> More informations about this toot | More toots from readeck@mastodon.online This content has been proxied by September (3851b).Proxy Information
text/gemini