Ah thank you, that wasn't obvious to me from its website

True words. The sustained effort to keep something in decent shape over years is not to be underestimated. Now when life changes and one is not able or willing anymore to invest that amount of time, ill-timed issues can become quite the burden. At one point I decided to cut down on that by doing a better founded setup, that does backup with easy rollback automatically, and updates semi-automatically. I rely on my server(s), and all from having this idea to having it decently implemented took me a number of months. Just because time for such activities is limited, and getting a complex and intertwined system like this reliably and fault tolerant automated and monitored is simply something else than spinning up a one off service

Also Dinge die mir spontan einfallen wären z.B. private kostenlose Wlans wie Freifunk, staatliche kostenlose Wlans die oft an öffentlichen Plätzen und Gebäuden zu finden sind wie BayernWlan und sowas, kostenlose Wlans in Geschäften (z.B. viele Supermärkte), Bahnhöfen und Zügen. In jedem Supermarkt kann man einfach eine Prepaid Karte mitnehmen. Abseits des Mobilfunks gibt es auch öffentlich zugängliche Computer, z.B. in Bibliotheken. Also du kannst es auf jeden Fall unbequemer machen ein online Casino zu erreichen, ob das reicht hängt dann wahrscheinlich davon ab wie groß das Verlangen der Person ist trotzdem zu spielen.

Well maybe you youself are too new to recognize some of the appeals ;)

One large advantage with silverblue is, that the whole composition of the OS does not take place on the target machine. That means that all the issues that could arise will not take place on the target machine, and can be dealt with beforehand. In the simple case this could mean just enjoying vanilla silverblue without having to think about possibly borking the machine. In an advanced usecase this could mean for example building the os images in a GitLab CI/CD pipeline (with well working tooling that exists already for docker etc), then having automatic tests in the pipeline ensure that everything important works as expected. And only if the tests pass, the image will be added to the repositorie's image registry, where the target machines will fetch it from automatically and rebase to it.

Ah interessant, vielen Dank!

I think one puzzle piece of improvement is flatpak:

• It has a verification system, such that users can see which apps are packaged by their developers. For those apps, this eliminates the need to trust a separate maintainer entirely
• It targets almost all linux distributions with a single package. This cuts down the packaging effort for covering the majority of the linux landscape so much, that the number of package maintainers required to be trusted collapses - in the ideal case to just the developers themselves as in the first bullet point
• It makes use of sandboxing, so in case of a malicious app it (in theory) only has access to the stuff the user gave it permission to.

In reality there's a plethora of problems obviously:

• verified apps are the minority
• some people don't like the additional storage needed for runtimes (although the more flatpaks you use the more runtimes can be shared and its overall impact gets smaller)
• A lot of apps do not yet use all the portals, and require the classical full access to the system to work properly (in some cases the user can still remove some permission if certain features of the application are not needed by them though). This is just a question of ongoing development work, and hopefully we reach a point in the near future where a flatpak app without tied down permissions raises eyebrows

In terms of helluvalot less critical - is it really though? Remember that the app on your phone is also witten by them, closed source and does whatever they want with your clear-text messages. If the trustworthyness of a messaging vendor is part of the critical-ness question, e2e encryption does not add anything: Either you trust them and could also do so when they process your message on their server, or your don't and they could indeed spy on you on the proprietary client app.

End 2 end encryption is only a real benefit when the ends actually belong to the user, i.e. theres transparency about the ends being clean, which can only be shown for open source ends. If the ends are potentially compromised, there's so security / privacy guarantee.

But it should not need write access to those files.

I bet it is due to different UID. Nextcloud runs with the www-data user, and UID 1000 is likely whatever user OP set up on the host machine. Make Duplicati run with the same UID as nextcloud and it will have the permission to read the files.

I built a small tool that does that for me now and published it: https://feddit.de/post/2909288 maybe you'll find it useful, no guarantee that it doesn't break something though :D

Ahhh that looks very interesting! It seems to commit on actuall maintaining the projects that make it in there, hence of course trying to keep the number small and only letting relevant high quality projects in. That's of course more than gifting ownership of a project to the public for somebody to grab, but a rather nice concept nontheless!

There are also WordPress plugins that allow for exports of static html. Of course you need a theme without comment sections and all that jazz, as that is disfunctional in the static export anyways.

As many other stated, its nozzle ooze. When you travel the same path repeatedly, it will catch on previous ooze and build these diagonal structures.

Besides what other wrote, I can recommend:

• Try out how fast you can make your printer move, and travel as fast as possible. That gives your filament less time to ooze, and therefore you minimize the amount.
• When travelling, do a very small Z-hop. Something like .1mm. That helps a bit to not deposit the oozed material along the way, but where you touch down again. If you make the Z-hop too high, it will start to create strings. So you'll have to try and tune this value.
• Generally try to slice in a way that minimizes travels. Even stuff like choosing an infill that doesn't cross lines, and connecting those lines so that you print long and steady can help to keep your nozzle clean (I like gyroid with connected ends for that matter).
• What also helps is to convert your printer do direct drive. That gives more precise retractions. What works well for me is direct drive with small retractions. I believe, not shoving the filament back and forth so much yields better quality. Maybe, because retracting a large amount pulls air into the hot-end, and I imagine it might not all come out perfectly again when continuing with the next perimeter.