A quick Google search found me https://amara.org/ so maybe content creators could us it to allow others to add su s. Source: over 3 years ago

Man, just happened the same to me. I was transcribing some clases using the large model and theres a point in the video that the teacher gets a 5 minute break, and what happens? I get the following (https://imgur.com/a/8HQdpng). It is in spanish but says, brought by amara.org, which is a web that subtitltles things and then a lot of ads. Source: over 3 years ago

Https://amara.org/ ? You just link your video, and volunteers can/will translate it to whatever language you want. Source: over 3 years ago

You could use amara.org for a free and opensource web-based translation tool. Source: over 3 years ago

The best thing is Amara, and is in fact what Google shunted in place when they removed community captioning, giving creators a whole 3 months (or something similarly piddly) of one of their paid services for free. It's not an equivalent experience though, as folks have to go elsewhere AND know a volunteer-captioned video exists in the first place. Separate but equal is not equal. Source: over 3 years ago

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

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

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

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

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