argos-translate VS Flatseal

Interestingly, I think this is actually related to the offline translation features built into Firefox. Both are products of "Project Bergamot", but the Mozilla-maintained version was later merged into the Firefox application:

https://browser.mt/

https://blog.mozilla.org/en/mozilla/local-translation-add-on...

https://hacks.mozilla.org/2022/06/training-efficient-neural-...

https://github.com/mozilla/firefox-translations

https://firefox-source-docs.mozilla.org/toolkit/components/t...

Extra webpage with screenshot and links, impossible to search for normally:

https://translatelocally.com/downloads/

Does one thing and does it well.

Oh— For downloading models, it's much easier to pipe/`xargs` `translateLocally --available-models` into `translateLocally -d` than go through the GUI.

---

Other self-hostable translation tools:

https://www.apertium.org/index.eng.html

- Traditional rule-based translation. Seems to work pretty well, but no good desktop frontend.

https://www.argosopentech.com/

- Works, but crashy desktop app.

https://libretranslate.com/

- API wrapping Argos Translate.

https://lingva.thedaviddelta.com/

- Google Translate scraper/privacy frontend.

https://euroglot.com/

- Proprietary, subscription trialware.

Consider a free software alternative to this translation service, such as Argos Translate or its web based frontend LibreTranslate.

LibreTranslate (which uses Argos Translate) from my understanding, but I don't think it can be used to translate entire websites

This looks pretty legit but I haven't tried it: https://github.com/argosopentech/argos-translate

Google translate is both censored and intentionally flawed. Here is a better option: https://github.com/argosopentech/argos-translate

Argos Translate can do everything that LibreTranslate can do on your desktop without uploading translated text to the Internet.

Argos Translate has open source neural machine translation https://github.com/argosopentech/argos-translate

I'm trying to upload a Mac app to the App Store and need to take screenshots at 1280x800, 1440x900, 2560x1600, or 2880x1800 resolutions. I'm developing on a Mac Mini connected to a HDMI display and I'm unable to run at any of the required resolutions. I'm currently trying to take the screenshots through VNC using the Mac Mini in headless mode. I have the VNC server running (System Preferences > Sharing > Remote Management) haven't been able to set the resolution. How do you set the resolution when running a Mac in headless mode over VNC?

And not only that, the idea of portals is, IMO, misguided. See this view/bugreport when a flatseal user understands that even though they restricted permissions to access a certain area, the flatpak, itself, can ask to open files there and if OK'd that will be allowed. Their expectation is that with the overrides say "no access" it means "no access even if the flatpak asks very nicely". https://github.com/tchx84/Flatseal/issues/196

Since you installed the programme via Flatpak, you should simply lack the necessary rights (https://docs.flatpak.org/en/latest/sandbox-permissions.html). You can extend the rights quite easily with https://github.com/tchx84/flatseal.

Yes, filed https://github.com/tchx84/Flatseal/issues/196 a while ago, got no joy.

One design feature than can turn into an issue in some scenarios (usually dev tools) is the permissions of a flatpak. In case I need to tweak things, I use Flatseal. I know you can manually do this from the command line but I don’t change permissions that often so I don’t bother learning how to do that.

Does the Flatpak Permissions Settings replace a tool like Flatseal?

What about flatseal then ? https://github.com/tchx84/Flatseal

https://github.com/tchx84/Flatseal (Also on Discover. For security reasons, the Discover store installs apps as sandboxed "flatpak" apps. This one is used to view what each up can do and change the permissions of apps. May be required if the sandboxing breaks something, though usually not required.)

I believe it does. As an example if I try running Godot from the Steam flatpak, it won't be able to see any of the contents of my ~/Projects folder unless I explicitly allow the steam flatpak access to that directory that via flatpak's CLI options or using Flatseal