Couldn’t find it in there, but maybe this opens up live collaboration between desktop and web users on the same document.

This reads like script kiddie & weeb bingo combined. What a world

LineageOS with microg

The main GrapheneOS dev creates beef with a bunch of other projects. It’s not some shadowy organisation, it’s him having stupid takes in GitHub issues and spreading false claims about other projects.

You’re not the only one. It’s one of my biggest reasons for staying away from it

Still much better, especially with respecting opt-outs, than most other LLMs

Kidnapped would be the correct term, no?

It’s an intermediate release, so the perfect time for Ubuntu to evaluate uutils for their next LTS

https://news.ycombinator.com/item?id=8863

Funny you should mention that, Nextcloud originally forked off OwnCloud due to drama.

I think the server is working, it’s basically OwnCloud Infinite Scale but rebranded. Not sure about the client apps, those might be work in progress still. I haven’t really kept up with it either though

Many of the people who worked at OwnCloud Infinite Scale are now at OpenCloud due to disagreements between them and the company which purchased OwnCloud.

They changed that with Debian 12 I think

The FSF has an ass-backwards approach to firmware, leading to only these distros fulfilling their requirements.

Their preference for firmware is as follows:

1. Firmware that’s open source (fair enough)
2. Firmware that can’t be updated (i.e. devices that are flashed once at the factory)
3. Firmware that can be updated (CPU microcode, firmware for GPUs, SSDs, etc)

As Linux includes patching of CPU microcode on boot (to fix security vulnerabilities and bugs) the default build of Linux doesn’t fulfill those requirements.

So what if your tiny site is offline for a bit. It’s not like you’re selling anything and the people will find an archive link

In practice many Exchange enterprise admins disable or restrict protocols other than EWS. This feature allows you to use Thunderbird anyways and will also enable calendar sync in the future, another often restricted part.

I tried Actual Budget for a while, but didn’t stick with it long term. I also looked at Firefly III, never tried it though.

Eventually I figured out I just want an expense tracker instead of full budgeting and settled for ExpenseOwl

Lemmy has a perfectly fine cross posting feature you could use

You can also use 200::/7. It’s been deprecated since 2004

You can use host_vars to set different variables per host. You’d still run the same playbook against both hosts, but each has different services activated.

1. Make the folder host_vars in the repo root
2. Make subfolders for every host with their hostname
3. Enable services you want by writing the variables into a yaml file for your host (any file name as long as it ends with .yml
4. Write an Ansible inventory for your hosts
5. Run the playbook with your inventory

Slightly fancier would be using group_vars instead, you can add a host to multiple groups. Then deploying the same services on a new hosts would simply be adding it to the group

Imagine using a well designed set of tools instead of parts stuck in the 90s