oranki

I didn't read all the comments, so someone may have pointed this out already.

One of the main ideas is probably something like Fedora CoreOS, where the Quadlet systemd files are automatically created during first boot with something like Kickstart or cloud-init.

Instead of shipping the applications with the image, the OS image can be very minimal, while still being able to run very complex stuff.

When you add the fact that CoreOS and other atomic distros can update themselves in the background, and boot to an updated base image, the box just needs periodic reboots and everything stays updated and running with basically no interaction from the admin at all, best case.

Probably not so useful in the self-hosting / homelab context, but I can imagine the appeal on a larger scale.

I've been using Quadlet+Podman kube YAMLs for a while for my own self-hosted services, and it's pretty rock solid. Currently experimenting with k3s, but I think I'll soon switch back. Kubernetes is nice, but it's a lot more fragile for just a single node. And there's way too much I don't understand...

I wrote a couple blog posts about the homelab setup, planning to add more when I have time. Give a read if you're interested: https://oranki.net/tags/self-hosting-my-way/

Nextcloud notes, but the setup isn't obvious:

• Create a list with user A
• Share the list .md file from the Notes folder via regular Nextcloud Files to user B
• As user B, move the shared note file to the Notes folder in the Files app

And you have a shared note. The Notes folder refers to the folder containing the user's note files, not sure what the English name is.

Not sure how well concurrency is handled, as Notes doesn't really support sharing, but if it's for groceries, I doubt it's a frequent issue. Has been working well for 2 years now.

They are convenient, but there's only a couple sites that support full login with passkeys. I'm reading between the lines of your comments none of them are sites you'd use (Microsoft, Github, Google, etc...)

Someone else commented KeepassXC has an open issue about passkeys, perhaps they'll add support sometimes too.

You're not really missing anything yet, to be honest. I've mostly tried them out just out of interest, and it's still very much aimed at people using Google or Apple...

With Bitwarden, you can use passkeys on chromium browsers. Vanadium actually enabled support in advance.

You need to have Play Services installed, though. This is due to Chromium, nothing GOS can do about that. No need for even network permission for Play Services, luckily.

Firefox is supposedly adding a standalone implemetation, which won't require Play Services, any year now...

Don't have Proton Pass, so don't know what's the situation there. With BW+Vanadium, they work well. I just wish Play Services weren't required. With Google Passwords they probably just work.

I don't think most apps even access sensors. I also think disabling it is not necessary, more so if you don't allow network for an app. Though some (google) apps may still send data to Google via Play Services, supposedly.

I wouldn't worry about it, but you need to decide for yourself. Usablilty is also an important factor, pixels aren't cheap at least where I live.

Not a stupid question at all.

Location is for, well, location specifically. Sensors is a GOS thing, it blocks access to all sensors, like gyro, proximity, ambient light, etc.

Since it's not part of AOSP, apps will very likely misbehave if you turn the sensors permission off. That's why I left it enabled for Play Svcs and GSF, not sure if it's actually necessary.

From https://grapheneos.org/usage#bugs-uncovered-by-security-features :

Similarly, some of the other privacy and security improvements reduce the access available to applications and they may crash. Some of these features are always enabled under the hood, while others like the Network and Sensors toggles are controlled by users via opt-in or opt-out toggles. Apps may not handle having access taken away like this, although it generally doesn't cause any issues as it's all designed to be friendly to apps and fully compatible rather than killing the application when it violates the rules.

IMO, just the options to automatically turn off WiFi and Bluetooth after being disconnected for a while are enough to make it worth it. Not to mention all the other privacy benefits, like others have stated.

Oh, and network permission toggle is also really useful. If only passkey APIs were part of AOSP instead of Play Services / GSF, I've got them installed just for that (with only sensors permission)

In that case it's definetly worth it to try this out, just so you have one more notification to disable

In that case hydroxide-push will work too, which is good news!

Just note that the IMAP, SMTP and CardDav functions have been stripped out from this push version. If there's interest to have those too, a different version with the push stuff added on top of full Hydroxide could be made. It will require a bit of time to develop.

The scope of hydroxide-push is only push notifications for now.

I think it does require a paid account, Hydroxide basically acts like the official Proton bridge.

I haven't actually tested with a free account, so there's a chance it does work. When you run the auth command (which is the same as upstream Hydroxide), it will probably throw an error.

If you have a free account and try this out (or Hydroxide), please report how it goes back here, I'll add a note to the readme. Upstream doesn't seem to mention this in their repo either.

Happy to report that version 0.2.28-push7, available today now supports HTTP Basic Authentication for the push topic!

Password for basic auth is stored base64-encoded in $HOME/.config/hydroxide/notify.json, this is something that could be improved. Considering UnifiedPush always requires anonymous write access to the push topics, I don't think this a very high-risk shortcoming.

Suggestions for better password handling, as well as general feedback are welcome!

There is no way to log in or do anything externally after the daemon has started.

The idea is just to provide push notifications, nothing else. The bridge creates a "login session", because Hydroxide won't poll for events if no users are logged in. In reality the SMTP or IMAP services are never started.

If there's an oversight somewhere, I'm more than happy to admit it and see to fixing it. I wouldn't run this on a cloud VPS, just like I wouldn't run Hydroxide either. Because all connections are outbound and the amount of data is small, a Raspberry Pi at home should be more than enough.

I see you deleted the comment, going to leave this here anyway.