@pauvretype pour miniflux tu peux lier tes comptes comme #linkding #wallabag #readeck #matrix etc alors que freshrss c’est par extension et pas forcement facile à configurer. autre point c’est que miniflux est en go qui est rapide. j’ai deja essayé de nombreuses fois installer freshrss mais à chaque fois je bute sur la multitude de flux RSS que j’ai en ma possession ça finit en erreur 404, mon NAS ne suit pas alors que miniflux pas de souci. là actuellement j’en suis à 200k articles xD
#Readeck looks great.
https://codeberg.org/readeck/readeck
The UX is certainly much better than in #Wallabag.
The only problems I see:
- No mobile app :c
Maybe I'll try to set up EPUB export, as suggested.
- The API docs don't say how to submit an article with the content; had to figure this out with mitmproxy.
Happy I Love Free Software Day!
Unfortunately, this year I could not join nor organize any in-person celebration, BUT of course I want to share my gratitude to the many, countless #FreeSoftware services I don’t merely use, but actually depend on.
Last year, I decided to focus only on #YunoHost, because it would have been crazy to list all the projects I use and I love.
This time, even if I will most certainly forget someone, I am challenging myself to mention all the #LibreSoftware my life is powered by.
Without further ado, THANK YOU to:
Lastly, but most importantly, the biggest thank you goes to all the free software libraries and dependencies the above mentioned #software are made of/built with, including #C, #JavaScript, #Python, #Rust, and all community-maintained programming languages.
I am super sorry if I forgot someone!
WHEE!
First real service moved to Quickbeam, fronted by Eru. And it works! The setup is thus validated, yay!
Incidentally, this was a service (#readeck) that had some deployment issues on the old server. No more, it works properly now on the new #NixOS host, running on a decade old Mac Mini.
It's not its final place, the Mini is temporary. But it's a nice first step, an experience in migrating something I use heavily.
Readeck
Wer die Vorlesefunktion von Omnivore vermisst, der kann auch eine der iOS-Stimmen (lokal) in Readeck nutzen. Unter Bedienhilfen einstellen, dann genügt es, mit zwei Fingern von oben zu streichen.
Angesichts der heutigen KI-generierten Möglichkeiten zwar nicht top, aber doch ganz akzeptabel für das Vorlesen neben dem Rasieren :-)
Readeck Update
- Für Markierungen können nun unterschiedliche Farben genutzt werden
- Die Suche kann nach dem Lese-Status (Fortschritt) filtern
@readeck It would be nice to be able to search or filter by color in the future. :-)
@nikolasdi @nadiyar Nice find, #Readeck looks much more polished than #Wallabag. Installing via Docker was ridiculously easy and worked flawlessly. Thank you!
For anyone following this, it looks like my answer is #readeck. The interface is #accessible, it does full text search, it archives pages, it has a browser extension, it works with #miniflux, it does the same kind of read/unread tracking that I wanted from #goodlinks, and it plays well with the rest of my things. Thanks so much to @readeck for making sure to build an interface that is fully #screenreader accessible. The only thing I'm lacking is an #IOS app. And the ability to share some labels publicly would also be neat. But otherwise, Readeck is perfect for my use-case. If you're a #blind person who wants a demo account to test it out and see if it works for you without going through all the bother of installation and set-up, send me a direct message. #a11y
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!
@nadiyar I have been using #Wallabag but recently started trying out #Readeck and I like it a lot. https://readeck.org/en/
Wochenrückblick, Ausgabe 75 (2025-02)
Themen:
Zensus-Atlas Deutschland
„How I build a feature“ von @simon
3D-Druck-Filament und die Feuchtigkeit
New Device Day: Eierkocher
Readeck statt Instapaper
Das CLI-Tool der Woche: make
#Wochenrückblick #Zensus #Karte #Software #3DDruck #3DPrint #Filament #Küche #Eierkocher #Readeck #CLI #make #Techno
Endlich mal ein gescheiter Workflow um lange Artikel distractionfree lesen zu können. Dank des neuen #Kindle #jailbreak #WinterBreak
KOReader mit OPDS an meine #readeck Instanz angekort. Funktioniert ganz prima :)
Und ja, der nächste E-Reader wird bestimmt kein Kindle. #selfhosting
Updated my #Readeck #NixOS module, now it is based on upstream's main
branch (as of commit 4793e11387), and uses the new readeck user
sub-command to set up users declaratively, in an ExecPre
script.
This is even better than my approach, because this supports declaring multiple users, and their settings are re-deployed every time the service is restarted, keeping them in sync with the configuration. On top of this, the passwords no longer linger around in an environment variable while readeck is running! They're only injected into the environment for the duration of the pre-start script.
It's still wild.
Been poking at it for a few days now, but my #NixOS module for #Readeck is now in a state I'm reasonably happy with:
DynamicUser=true
.ProtectSystem="strict"
.I'm kinda proud of the last bit, really. Here's how it looks in the configuration (also using sops-nix
for the secrets):
services.readeck.config = {
admin.initial_username = "algernon";
};
services.readeck.secret-files = {
main.secret_key = config.sops."readeck/secret_key".path;
admin.initial_password_hash = config.sops."readeck/initial_password_hash".path;
};
sops.secrets."readeck/secret_key" = {};
sops.secrets."readeck/initial_password_hash" = {};
The secrets are owned by root, readeck has no direct access to them. They get exposed to Readeck via #systemd's LoadCredential
. This allows me to use DynamicUser=true
, because the secrets need not be owned by the same user Readeck runs as.
The NixOS module also generates a "secrets loader" script, which loads all those secrets into the appropriate environment variables, and exports them. The generated loader looks like this:
export READECK_ADMIN_INITIAL_PASSWORD_HASH="$(cat $CREDENTIALS_DIRECTORY/READECK_ADMIN_INITIAL_PASSWORD_HASH)"
export READECK_SECRET_KEY="$(cat $CREDENTIALS_DIRECTORY/READECK_SECRET_KEY)"
A small wrapper around readeck sources this script (thus exposing the environment variables), and then execs the real readeck binary.
Save from readeck loading the secrets itself directly, I think this is the best way to inject the secrets into the service. But its not this idea I'm proud of, no. It's the magic that makes the configuration above possible. The magic that takes that services.readeck.secret-files
attribute set, and sets up both the secrets loader script, and the LoadCredential
list.
It's wild.