laskobar

Can you please tell me how to do that?

Additionally, how does the shredder working? I haven't attached a assembly line to it, but normally I can put manually pieces in to the stations. But this isn't possible with the shredder...

Yes, I think the card is the weak point here or better the weak driver support. My next laptop will definitely have a AMD card. But I have absolutely no idea which one is good enough to handle actual games with full details and usable fps. I don't expect Desktop like experience but at least 40 fps with full details in an actual game would be fine. Im not a professional gamer, but when I have the time to play, it should be fun and not frustrating. Mostly I do coding with VSCode and some database stuff in different flavors. So a not to small display is a must have.

Can you recommend a good GPU? For the rest I can do my own research...

Yes, of course. But nothing helped really. There is a small difference between the used Proton version. With 8.25 GE i get 13 fps and with 6.4 GE1 i get 19 fps. Using PROTON_USE_WINED3D11=1 makes it more worse than ever, with only 5 fps.

On the same laptop with windows, I have ~ 60 fps.

From my point of view, this is all relatively unstable and not really well thought out, far from being reliable. I have spent the last 2 weeks trying to convert my Crossbowser bookmark backend (https://codeberg.org/Offerel/SyncMarks-Webapp) into a functioning PWA. Very disappointing. Don't ask me how many nerves I've lost in the process. At least you can now use the WebApp as a PWA. The share_target also works if it was installed via Chrome or Samsung Internet. It also works offline. These functions are even retained if you subsequently uninstall Chrome/Samsung Internet. The WebApp then asks which browser wants to take over the functions. This also works with Chromite or Firefox. Strange but what the heck. At least you can now share any URLs with the backend. This also works offline, even if this is more of an Edge case for bookmarks.

Oh there is a APK, when using Chrome or Samsung Internet (installed via Samsung Store). The store is generating and signing the APK. Only with such a signed APK OS Level functions will work. A good example is the share_target functionality. If this is enabled by the PWA and installed as APK, you can share text and links with the PWA. The same applies for PWAs on the Desktop, for example with Edge on Windows.

If you use the same PWA with Firefox or Samsung Internet installed from Play Store, it can only add a shortcut on the home screen, without share_target functionality.

Additionally some service worker functionality is very basic on some browsers. On one hand this is bad for functionality, but good for privacy. Assume a PWA uses a background sync service for example. This can exchange a lot data and sync it with any target in the web, without user consent. This is only a small part where service workers do not respect users privacy.

If you look at that we come in fast steps to this insane and total crazy manifest v3 webextensions. They are completely privacy nightmare at least how Chromium designed them. The Mozilla implementation is a lot better, but incompatible to Chromium.

Welcome to the ugly world of new web technologies.

This makes sense. Yes, I have paid in the playstore for this app (and I would do it again and again). But if I understand it correctly this would also mean, I could download their v4.3.8-ose from the official GitHub repo for free, and it would be updated automatically from Playstore to v4.3.8-gplay version (which is not free). Strange.

But this app is worth every penny.

Oh thats my standard browser. I need Chromium only for testing my webextensions and for Geforce Now. Since the last will not work with Firefox.

I can give it a try, but I would prefer a more "native" approach. I don't like this flatpack/snap concept. But yes, it's an alternative.

Yes, that's my understanding of xdg. But I have no idea what this means for Ungoogled Chromium package. Base Chromium itself isn't degoogled. It has most of the Google service's active and enabled. Only a minor subset, like bookmark sync is disabled (but technically available). With Ungoogled Chromium, most (not all) Google dependencies are patched and inactive. At least this was the case as I last checked it. Since I prefer a mostly Google free environment, I would like to use Ungoogled Chromium for testing and a patched Firefox browser for standard web things.

Why do you build a chest around the bee's? Sorry, I'm new to Valheim.

Unfortunately no SFTP. On the other hand, it has WebDAV support.

This is because Wayland doesn't allow it to read window titles. Keepass and KeepassXC uses the window title to identify which entry to use. If you have no title, you can't find the entry. That's why it will not work with Wayland and never will work, until Wayland allows it to read window titles.

XWayland, which is forced with your workaround, is not Wayland.

That's at least for me, the main reason not to switch to Wayland. I have no idea why Wayland doesn't allow reading window titles. There is absolutely no security or performance benefit of this behavior. For me it's either a bug or a design failure. Or simply bad behavior.