For what it’s worth, I do think OCIS is worthy of switching to if you don’t make use of all of the various apps Nextcloud can do. OCIS can hook into an online office provider, but doesn’t do much more than just the cloud storage as of right now.

That said, the cloud storage and UX performance is night and day between Nextcloud/Owncloud and OCIS. If you’re using a S3 provider as a storage backend, then you only need to ensure backups for the S3 objects and the small metadata volume the OCIS container needs in order to ensure file integrity.

Another thing to note about OCIS: it provides no at-rest encryption module unlike Nextcloud. If that’s important to your use case, either stick with Nextcloud or you will need to figure out how to roll your own.

I know that OCIS does intend to bring more features into the stack eventually (CalDAV, CardDAV, etc.). As it stands currently though, OCIS isn’t a behemoth that Nextcloud/Owncloud are, and the architecture, maintenance is more straightforward overall.

As for open-source: OCIS released and has still remained under Apache 2.0 for its entire lifespan thus far. If you don’t trust Owncloud over the drama that created Nextcloud, then I guess remain wary? Otherwise OCIS looks fine to use.

Persistent keep alive is configured per connection by all peers (server and client typically). As I understand it, Wireguard’s peer-based architecture will let both client and server peers define an optional persistent keep alive timer in order to send heartbeat packets on interval. Otherwise Wireguard on either peer may keep opening and closing connections for inactivity (or get its connections forcefully closed externally) if traffic isn’t being regularly sent. This can occur even though the network interfaces for Wireguard on both communicating peers remain up.

I do agree that running some kind of health-check handshake service over the Wireguard tunnel is an easy enough way to periodically check the state of the connection between peers.

Depending on how your connection is negotiated, it may partially not be possible due to the architecture of Wireguard. There is likely some way to hook into capturing handshakes between clients (initial handshake, key rotations). To determine disconnects and reconnects however is a challenge. There are no explicit states in the connection. The closest thing to disconnect monitoring is utilizing a keep alive timeout on the connections. There are some caveats to using a keep alive timer, however. Additionally, not every connection may use a keep alive timeout, making this a full solution infeasible.

Detailed information about Wireguard session handling can be found in section 6 of this PDF.

I believe it’s mostly drawing tablet support in Qt and in turn porting to Qt6 that’s holding native Wayland builds back.

An aside to the technical question of how to migrate profiles to older versions:

DO NOT DOWNGRADE FIREFOX BELOW 131.0.2 OR ESR 128.3.1, 115.16.1

I feel that given this recent vulnerability, it is important to make this notice.

Otherwise:

For migrating profiles between the same major version, Mozilla provides a guide for full profile migration. This also works with forwards compatibility. I generally wouldn’t try to go backwards however as many new major versions change the data format and contents of your profiles, which older versions have no idea how to interpret.

For downgrading, it’s best to export bookmarks, go through your important addons and backup the settings for each one that needs configuration, and take note of anything you’re previously modified in about:config to your preference. Perhaps take screenshots of your tab bar and overflow menu as well so you can recustomize them to your liking easily on the downgraded version.

Just note that with Bambu printers about past data collection practices and their in general mid to atrocious after-sales support. If this doesn’t deter you, then go ahead and get one.

I do a lot of my functional parts in ABS, ASA though printing such material may be difficult on an open-air machine. The two obvious choices will generally be PLA or PETG. PLA is one of the most common printed materials, and is fairly balanced in material strength. PETG parts are more likely to permanently deform heavily before fully snapping, as well as they have a but more temperature resistance than PLA. Additionally most PETG plastics hold up decently well to UV, often making them more suitable for parts that need to be outdoors.

PLA takes not much consideration on surface to print, as most printers come with a smooth PEI build sheet by default. It will however need more cooling than printing with PETG at equivalent speeds. If you use a PEI sheet for PETG, make sure it is textured. You will destroy a smooth sheet if it doesn’t have some kind of release coating to lower its adhesive properties to PETG.

There is no guarantee for spools of filament to actually arrive dry, so a filament dryer isn’t a bad idea. I don’t have any particular recommendations for a good filament dryer. I have a Filadryer S2 from Sunlu, but am not impressed by it.

Just took a couple minutes to install and setup the fork to try it out. Turns out there is a flatpak on Flathub under the id dog.unix.cantata.Cantata that looks to be maintained directly by nullobsi. I’ll have to see where rough edges show up, but this fork looks good thus far. A full port from Qt5 -> Qt6 isn’t a trivial amount of effort, so mad respect to everyone working on this ported version.

As I found out recently myself, you should almost always set the minimum amount of reserved memory for the iGPU on modern hardware. The reserved memory is just that— reserved. The kernel still dynamically allocates memory for GPU usage as needed on iGPUs.

The specific patent links seem to be broken. All return 403. Here are functional alternatives.

• 9421713
• 9592660
• 7555357
• 9168698 / 10556381

Largely things look good. It might be a good idea looking for a motherboard that has Intel ethernet rather Realtek. I’m also a bit curious if the barebones VRM design on the board is adequate as well.

We are well beyond the point of a majority of common hardware having built-in kernel drivers and userland software for extra stuff like RGB control that the best advice is rather avoiding Linux, to instead avoid the trash hardware (NVidia for the time being, GoXLR, Broadcom, etc.). My GPU, audio hardware, network interfaces are both popular products and have worked out of the box for years now.

2-2-1 still insinuates having a remote backup. I don’t see how this particular threat destroys a 2-2-1 setup.

The heated bed is coupled to a thermistor. I’d argue controlling the temperature in order to not accidentally overheat parts of the phone is a step above a hair dryer.

The worst gotchas and limitations I have seen building my own self-host stack with ipv6 in mind has been individual support by bespoke projects more so system infrastructure. As soon as you get into containerized environments, things can get difficult. Podman has been a pain point with networking and ipv6, though newer versions have become more manageable. The most problems I have seen is dealing with various OCI containers and their subpar implementations of ipv6 support.

You’d think with how long ipv6 has been around, we’d see better adoption from container maintainers, but I suppose the existence of ipv6 in a world originally built on ipv4 is a similar issue of adoption likewise to Linux and Windows as a workstation. Ultimately, if self-rolling everything in your network stack down to the servers, ipv6 is easy to integrate. The more one offloads in the setup to preconfigured and/or specialized tools, the more I have seen ipv6 support fall to the wayside, at least in terms of software.

Not to mention hardware support and networking capabilities provided by an ISP. My current residential ISP only provides ipv4 behind cgnat to the consumer. To even test my services on ipv6, I need to run a VPN connection tunneling ipv6 traffic to an endpoint beyond my ISP.

Windows does have memory compression, though you can’t really change the algorithm or how aggressive it is. AFAIK it is just a toggle of on or off.

Beyond the article being ancient at this point (in terms of AOSP and Android development lifetime), Stallman’s argument boils down to the same talking points of Free Software purism.

To the first real point being transformed here: Android is not GNU/Linux because it does not contain much of the GNU Project’s software. While it’s correct to claim it’s not GNU/Linux, how does it not make it Linux still? Is Alpine Linux not considered “Linux” because it doesn’t contain GNU? Please elaborate on this point of Linux being Linux because it has GNU.

To the second point of including proprietary drivers, firmware, and appplications: we once again meet the questionable argument of transforming an OS to something else. Points are made that Android doesn’t fit the GNU ideals due to its usage and inclusion of proprietary kernel modules, firmware, and userland applications. These are valid points to be made in that these additions muddy the aspect of Android (as packaged by Google and major smartphone manufacturers) being truly free software. However the same can be said about traditional “GNU/Linux distributions”. Any device running on x86 (Intel, AMD) will be subject to needing proprietary firmware in order to function with that firmware having a higher control level than the kernel itself, just as Android would. There is also the note that while it is less necessary now to have a functioning desktop, a good portion of hardware (NVidia, Broadcom, Intel, etc.) require proprietary kernel modules and/or userland drivers in order to have full functionality that the average user may want. Finally, there is proprietary applications as well. Some Linux desktops include proprietary applications like Spotify, Steam, Google Chrome by default. Are we really to also exclude an overwhelming majority of the biggest Linux distros as Linux as well being that they include proprietary software or rely on proprietary code in some fashion? GNU itself lists very few distros as GNU-approved.

To note, AOSP does have a different userland environment than your standard Linux distro running X11 or Wayland. That is by far the best reason I could think of to classify Android as a different category of ‘Linux’ from say Debian, Fedora, OpenSUSE, Arch, Gentoo, Slackware, and others. However, AOSP is still capable of running with no proprietary userland software and can even be made to still run cli applications as well as run an X11 server that is capable of launching familiar desktop Linux applications. I really think that the arbitrary exclusion of Android from being Linux by virtue that RMS doesn’t think it fits with GNU ideals is silly. If there are better arguments to be said for why Android (especially AOSP) shouldn’t be seen as Linux with a different userland ecosystem rather than not Linux entirely, I’d love to see them. However, I remain unconvinced so far.

The A485 is actually such a terrible laptop. I would never reccomend such garbage to anyone considering mine almost never worked properly. I had in three years have six main board replacements for various hardware faults. Not a single of the boards has been free from severe hardware faults.

I have been utilizing BunkerWeb for some of my selfhost sites since it was bunkerized-nginx. It is indeed powerful and flexible, allowing multi-site proxying, hosting while allowing semi-flexible per-site security tweaks (some security options are forcibly global still, a limitation).

I use it on podman myself, and while it is generally great for having OWasp CRS, general traffic filtering targets and more built on top of nginx in a Docker container, the way Bunkerweb needs to be run hasn’t really remained stable between versions. Throughout several version upgrades, there have been be severe breaking changes that will require reading the setup documentation again to get the new version functional.

Before going any further to adjust your Z offset and other factors to tune for better bed adhesion, you should probably adjust your bed to actually be level as well as ensure (seeing that you only have one z lead screw?) that the X axis frame isn’t sagging on the side not containing your Z lead screw. Once you’ve got those factors sorted out, you should check your probe repeatability and then set your Z offset accordingly.

Bed adhesion even with proper, clean first layers can be a pain depending on the bed surface, material being printed, how clean the bed is of oils and other contaminants, how hot the material is being extruded, and how hot the bed is among other factors. While using a bed mesh will greatly help to account for off-zero unevenness in your bed surface, you really shouldn’t use it to compensate for uneven bed leveling (especially when it looks like you are nearing more than 0.5 mm in unevenness).

To diagnose other print issues, it will be helpful to see a picture showcasing the problems described in a failed print.

As a side note, it is somewhat difficult to read your Klipper config file without using view source as it is being markdown formatted. You can negate it by using three graves on the lines above and below it so that it is wrapped in a ‘code block’ and isn’t formatted.

```
Some code
  eeeee
  fffff
```

Turns into

Some code
  eeeee
  fffff

The desired alternative is not Matrix simply because privacy-conscious, open-source ecosystem vs. proprietary solution is not the goal. Matrix would still generally be terrible for support. What people want is publicly searchable content that is ideally indexed like a wiki. Many will happily settle for issue boards or even forums though. Discord has pathetic search capabilities in comparison to any search engine and has no way to properly and publicly backup information that is posted to the platform. With a website of any kind, one could clone the site for mirroring or simply get a web archive service to crawl relevant sections.