wallabag Reviews

Temporal Reviews

wallabag mentions (19)

• KOreader

  I am using koreader.rocks on my ereader and KOreader has a native support for https://wallabag.org/. They are both fantastic opensource projects, whenever I like to read something I am sending them to my wallabag and therefore I can easily have them on my ereader too. Also the fact that you can install different plugin on KOreader and customize it in a way you like is fantastic. - Source: Hacker News / 11 days ago

• Ask HN: Does a good "read it later" app exist?

  I moved to a self-hosted Wallabag (https://wallabag.org/) after Pocket shut down. Not the sexiest but does everything I need it to. - Source: Hacker News / 6 months ago

• Mozilla shutdown Pocket on July 8, 2025

  I'm looking into setting up Wallabag for myself, maybe it could work for you too? https://wallabag.org/. - Source: Hacker News / about 1 year ago

• Mozilla shutdown Pocket on July 8, 2025

  I use KOReader [1] on my Kobo. It supports Wallabag [2]. Wallabag offers both hosted [3] and self-hosted options. There's also a standalone kobo client for Wallabag [4]. In addition, Wallabag also supports direct import from Pocket. [1] https://koreader.rocks/ [2] https://wallabag.org/ [3] https://www.wallabag.it/en [4] https://gitlab.com/anarcat/wallabako. - Source: Hacker News / about 1 year ago

• Trust in Firefox and Mozilla Is Gone – Let's Talk Alternatives

  Instapaper[1] and Wallabag[2] would be the two main alternatives to Pocket, I think. Wallabag is self-hosting although I believe there are hosted services around as well. Cannot get either of them to integrate with my Kobo ereader like Pocket does, though. :-( [1] https://www.instapaper.com/ [2] https://wallabag.org/. - Source: Hacker News / over 1 year ago

Temporal mentions (17)

• Temporal in Production: Sharp Edges & Good Practices

  When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 16 days ago

• Your Agent Bills While It Waits. Here's the Fix.

  Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / 21 days ago

• Compiler as Custodian

  Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 2 months ago

• How we turned our workflow editor into a real SDK

  We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / 2 months ago

• Three days debugging a missing trace

  The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 4 months ago