Arrowmaster
Joined 2 years ago
Karma
322
Submissions
160
Member since
Mar 26
Recent submissions
Comment · 9 days ago
It's an ever present neurological condition but the presenting symptoms can change over time as the brain develops. It's not just learning to manage it because not all the symptoms can be self managed.
Comment · 15 days ago
When the TLD first opened up you were not allowed to purchase {lastname}.name, it was restricted to third level domains only in an attempt to lure in customers wanting {first name}@{lastname}.name as an email address. But they didn't make it easy to configure that email redirect if you used another registar than verisign, and email has evolved.
Later in a desperate search for MORE MONEY, they opened up 2nd level if no 3rd level already existed under that 2nd. This sounds less like another search for more money with new sales as people are saying, but a reduction in unique domain handling and cost cutting (they can shutdown all those email redirection servers).
Comment · 15 days ago
So that you could use [email protected] as your email instead of [email protected]. The .name gtld was created in the height of the "we will move to a paperless world and email will become the universal way to communicate" era.
Comment · 16 days ago
Try it on an older LTS distro release that is still under distro support or even better, one that's under extended paid only support. Anything pre 2022 is probably completely broken and anything pre 2024 might have strange bugs. There was a great one where building a Tauri or Wails app on Ubuntu 22.04 for better compatibility but running it on a newer distro had a font rendering bug because of the older Webkit2Gtk. Trying to display emojis crashed the apps.
Comment · 22 days ago
When I stopped using KeePassXC, there was no merging. You configured each client to save immediately and reload when detecting the file changed. If you used a tool like Syncthing then you had to monitor for conflicts (which stopped syncing) and manually fix them. If the major clients on Linux, Android, and browser extensions all supported proper syncing on their own, I might switch back.
Comment · 22 days ago
I specifically moved away from KeePassXC to Bitwarden with self hosted vaultwarden because the Linux desktop experience and mobile syncing was so terrible. While I love KeePassXC, using it on an immutable Linux distro where everything needs to be Flatpak means the browser extension doesn't work because it doesn't support Flatpak'd browsers back when I switched. Auto type is a security nightmare and is not an option. Syncing does not exist and with the constant death and forking of Syncthing on Android, it became unusable to randomly find out my db hasn't synced for a week and now I have to reset everything with a new fork yet again.
Bitwarden was the no nonsense choice because it just worked.
Comment · 1 month ago
To be fair even the largest companies are still using curl piped to sh in their Linux install instructions. And they are all fucking imbeciles.
Comment · 1 month ago
It's almost as if they paid a contractor to design the hardware back in 2017 and put all the funding into marketing(bribes) since then. Shocker.
Comment · 1 month ago
Flatpak is the best of all bad options for multi-distro Linux packaging. Adapting to the sandbox if you aren't already using portals will probably be a pita though.
Comment · 1 month ago
Is this a professional project you created on behalf of your employer or your own business for monetary gain?
Just because you are forced to use AI on the clock doesn't mean you have to for personal projects.
Comment · 1 month ago
These are completely different types of services. One is a DoH recursive DNS resolver for use by clients. The other is a DNSSEC enabled DNS hosting provider for domain owners. The encryption in use is completely different with different goals.
Comment · 2 months ago
The README for wry under Platform Considerations suggests its not actually implementing the webview but just a wrapper that uses the correct one for each platform. The usage of WebKitGTK IS the problem that makes it second class on linux. I talked about this more in https://news.ycombinator.com/item?id=49514323
Comment · 2 months ago
Sure. Tauri tries to claim its lighter than Electron by not including a full web browser in its runtime and instead using the system renderer. But Linux doesn't have a universal system renderer like Windows and Mac does so it uses Webkit2Gtk on Linux. Libwebkit is an absolute mess of a library. It hardcodes the path to /usr which doesn't work in AppImages resulting in this[1] hack of a fix that replaces `/usr` with `././`. This problem isn't unique to Tauri as I have seen apps using Wails copy this same trick to package their AppImages.
Now the problem with libwebkit goes even deeper because Tauri uses libwebkit2gtk-4.1 after moving away from 4.0. When you build an AppImage you want to do it on the oldest possible distro you want to support because it will be built against GLIBC of that distro release. Due to how most devs release apps now, that means they compile against an Ubuntu LTS release because Ubuntu is the only option with Github Actions[2]. The first LTS version of Ubuntu with 4.1 is 22.04, so now by default you can expect every Tauri (and also probably Wails) AppImage to be built against GLIBC 2.36. But theres a bug in the interaction of older libwebkit2gtk and newer freetype that happens when you use an AppImage built on Ubuntu 22.04 on a newer distro. It crashes when displaying an emoji character. Freetype is one of the libraries you cannot include in an AppImage but you must include libwebkit2gtk, the solution is to use a newer libwebkit2gtk but thats only available in Ubuntu 24.04 and bumps the GLIBC to 2.39. Do you see how much of a mess this usage of libwebkit2gtk in an AppImage turns out to be.
And moving beyond that, the Tauri devs has an absolute disdain for the AppImage format and treat it as a 2nd class platform as you can see in this[3] PR where AppImage developers tell the Tauri devs to update to newer tools instead of mirroring the old obsolete broken tool that was taken down. This also meant that AppImages created by Tauri's build tools depended on libfuse2 being installed on the system while newer AppImages using the type2-runtime do not anymore. I believe Tauri has finally moved forward and stopped doing this recently. Electon is no better on this and electron-builder uses an outdated hardcoded tool that makes bad AppImages that depend on libfuse2 too.
I do like the AppImage format, but I do not believe anything that uses libwebkit2gtk-4.1 is fit to be distributed as an AppImage at this time. This means that Tauri (and by extension probably Wails, and some of these other NOT Electron frameworks) are not fit to be truly called cross platform. It does look like Tauri was making progress on Flatpak documentation so app developers could have a second cross distro packaging method. Ideally I think any framework that wants to label itself as cross platform should make it easy to package both AppImage and Flatpak and not run into the above libwebkit2gtk issues.
[1]<https://github.com/tauri-apps/tauri/blob/ad0b98a2329e369364e...>
[2]This is not entirely true, you can use a docker image inside the Github Actions Ubuntu VM or a sysroot but that is beyond even most expereinced app devs to setup.
Comment · 2 months ago
Won't happen until Tauri can treat Linux as a first class platform. Which they cannot do because of architectural design and library choices.