dlock17

It would be cool if this was true, but no, Stremio does not seed cached files.

https://github.com/Stremio/stremio-features/issues/626

Somebody made an extension that adds cached torrents to your local qbittorrent instance though, which is a nice alternative.

https://github.com/Vance-ng-vn/Stremio-Seeds

Note: I haven't used this, since I use Stremio from a Chromecast.

”The application is requesting access to accelerated graphics and drastically increase it's battery usage, do you allow this?”

It's possible all right, I've already done it. Imported Tesseract into Go with WASM.

https://news.ycombinator.com/item?id=38146154

It's not trivial because you have to figure out intricacies of the language and whatever compiled it into WASM, and Emscripten compiled WASM does expect some JS glue code. But WASM with WASI doesn't inherently require JS. And since Emscripten's JS glue is called via WASM host imports, you can implement them in whatever the host language is.

Iterators are coming. But I think taking very long on adding features such as generics and iterators has a positive effect of repelling the ones who over engineer the most.

And because this is HN, I have to mention of course you can over engineer current Go as well. But it's not "fun".

My intentions was a "pure Go" approach, but that is probably more performant.

I imagine just calling the Tesseract CLI from Go would be simplest if that's all you wanted.

Technically I said reimplementation. But you are right in that it's not supposed to be a drop in replacement at all.

The only feature missing right now is Bounding Box detection, which I plan to add in the future.

You mean this? https://github.com/WebAssembly/wabt/blob/main/wasm2c/README....

That seems like quite an undertaking. But at that point, It would make sense to cut out WASM entirely like https://datastation.multiprocess.io/blog/2022-05-12-sqlite-i...

Exactly, I expected to find one but couldn't, so I put together my own. It's not the fastest, but it'll do for my purposes.

That is tricky. I wonder how other package systems handle this.

I do think I prefer having the version being "immutable" (as enforced by the proxy, anyway) over alternatives since it's safer.

Maybe the Go proxy should periodically rescan the source and print warning messages on go get if they don't match up?

This seems like a good use case for Cap'n Proto.