Im.very into “AsCode” and pretty comfortable with vi bindings. So the two extremes where i document (random notes with no structure needed and formally verified documentation ) it works for me.
I can preview the markdown, use vale rules to enforce style and vocab, do mermaid.js diagrams, link my UML to stuff, etc.
Then check into git to do version control or just to save it off local.
The silence of two hours ago lol
Chill brother. Like i get it, and FOSS advocates should lead with meaningful alternitives first imho, but there definitly seems to be some https://joplinapp.org/
I personally prefer vscodium and nvim myself for notes but that isnt a one for one comparison to obsidian (in either direction) imho
How have tests gone so far?
also cool concept, you can actually get eBPF XDP to compile to FPGA on some smart NICs even further pushing it away from the core system if it works!
Honestly 100% for Odysee and Peertube adopting this plus if we could get proxing for each other too.
Opensource can win because we can do what google cant afford to do (their investors would flip).
That is a runtime that some flatpaks use as well.
Gnome and KDE as projects are a bunch of things, from login managers, to compositers, desktop UIs, and user application (like Gnome “System Monitor” or KDEs “Plasma System Monitor”).
You can actually mix and match some pieces and they just work, but especially the user apps because both teams put in work for interoperabilty or Freedesktop standarization.
So you can have an app that uses KDEs shared libs and an app that uses the Gnome projects libs on the same issue with rarely any issue. Even more so with flatpak since the all of the files those apps see are in what is called an overlay filesystem, so your kde apps get a layer of files jist for KDE apps to build off of and gnome apps get a layer of files just for them to use. In flatpak these are called runtimes. That is what is being updated here.
I have my shared data on Longhorn, so for services that’s just longhorn as a PVC on rke2(k8s) and for clients I expose the NFS for mounts from a longhorn PVC to them to mount to.
How is the kubernetes (k3s/rke2) migration coming along?
Tbh everything that makes those systems good for noobs works on other systems. Flatpak, distrobox, homebrew and btrfs snapshots.
The immutable OS part is actually just optional lol
Why not cloudinit instead of ssh?
Non-sequitor because people will blame the dumbest stuff on stuff they think is “wierd”
I guess the project was abandoned but supposdly spirtually succeed by https://github.com/matomo-org/?footer
The GNU project has a great write up: https://www.gnu.org/licenses/license-recommendations.html
tl;dr (though if you are interested its a good read) Client software == GPLv3 small projects are ok to be Apache v2 Server software == AGPL
the rest of the guide is more for devs and projects with recomendation on licenses for libraries and docs.
“Lets fight ICE” also “you need an id to use your laptop and be verifed by big tech to use it” Worse then clowns. Fucking traitors
Great now i can Kompose convert my converted helm charts!
RKE2 is the next step up from k3s Same group mantains it (Rancher) but its built for bigger productuon uses (i.e. it deploys etcd instead of sqllite by default).
Moonshadow@slrpnk.net Called it “immasculate conception” and i just fits too eerly well for me to forget
Reminder the size of breaker in the US electric code is to protect the wire and receptcle. After that you’re in someone elses hands.
Their building a Prison System ™️ regardless, open source (e.g. Linux) just offers SOME protections.
We have to do more regardless, but it’s still all part of the good fight in my book