B2 warns you, in advance, if your payment mechanism is expiring. And then, they don’t immediately delete your account or data if you’re late.

If you find out they accept advance payment, let me know; and I’ll do the same. Based on their charge model, you won’t be able to pay for X months, but I’d like to, say, have an account balance they will draw on if my payments fail.

I’m in particular considering the case of my untimely death. I have instructions for my family to get at all the backups, just in case, but if I die dealing with that is going to be really low on their list of priorities. I’d like to know that, 6 months after my CC stops working, my family will still be able to access my backups if they need to.

I double back-up onto SSD, but still.

Who do you think invented XMPP?

Yes, email, but it’s not real-time chat. Jabber sat between community chat IRC and the digital snail-mail analog, email.

Way back in 2024. Things were bad, but then, in October, there was a tectonic shift in the US, when the impossible became reality. There was a limbo for a couple of months, but in January this year we (the US) was flung back into 1940, and since then the years seem to be going backwards.

I wish English had a word like the German “doch,” to answer questions like “you’re not afraid?”

Are you kidding‽ I use it all the time! It’s even on my phone keyboard.

Did you know that there’s even an inverted interrobang? ⸘ I don’t know why, but it exists.

This is where I get stuck. I’ve worked with OAuth before, and it is very web-centric. Maybe it’s possible to work around http connections, but everything I’ve read makes it clear that it was designed with web applications - and browsers - as the foundational concept.

For example, I have a memory of trying to get two servers - neither of which had anything to do with the web - to authenticate, and to use OAuth I remember having to import an http library.

It’s been an age, so I may not be remembering it correctly; but IIRC the OAuth flow is designed around web protocols.

Don’t you threaten me with Kerberos. I used to have to deal with that crap decades ago; I disliked it then, and unless it’s gotten dramatically easier to work with, it’s not an option for me now.

I hadn’t heard specifically about samba4ad, but Kerberos on LDAP (and, originally, I think, on OLAP) I’m familiar with.

I like LDAP in concept, but after using OpenLDAP for a few years when my network evolved OpenLDAP evolved out of it. It may have been secure, but a more horribly, difficult to debug piece if software, I’ve rarely met. LLDAP has changed all that, and allowed me to start using LDAP again; it may be less capable, but OpenLDAP was overkill for home gamers. LLDAP is juuuust right.

Accidentally enabling SSO sounds like a big fish tale. SSO of usually a PITA to configure and set up. Even commercial software offerings are byzantine.

So… you have applications that aren’t web apps, authenticating themselves with other applications that aren’t web applications? Not proxying for you, but literally connecting to do something, like perform a backup.

I didn’t mean to suggest that it was. I meant that the kind of people who voluntarily choose IRC are the same sorts of people who would voluntarily choose to is XMPP. While IRC is older than XMPP, it’s still the 1:1 chat protocol for old technical people.

For your phone, use a native app, like Image Toolbox. It has a lot of functions, two of which are resize-by-dimensions, and filesize.

For the desktop… GraphicsMagick? Unless you need a GUI, in which case either whatever graphics tools come with Gnome of KDE should do the job.

Huh. I just checked Fluffy, and it asks for location, camera, and phone. I just denied it everything but notifications, so VOIP won’t work, but all I use it for is chat rooms anyway.

In any case, it doesn’t look any better than Element, in that respect.

If Pocket ID and Passkeys are like most modern “solutions”, they ignore everything that isn’t web, or human. Have you hooked any services together using it? Like having Home Assistant authenticate against mpd?

Yeah, that sounds ideal. I’d prefer editing a file than administering through a web page.

I’m checking Authelia right now.

SSO is part, but not all, of the picture. There’s also multi-system passwords, for things like sudo, and non-web service authentication; most of the stuff like OAUTH is really hacky to make work outside of web environments.

I’ve considered Vault for some of the inter-service authentication, but there’s not broad support built into services and it’s yet another thing to mess with.

LDAP forms a good base for most use cases, and so keeping it as the source of truth is important for me. And then, as few other layers on top to get SSO. Authelia is looking like the best solution.

Caddy is anything but intimidating! If Authelia is anything like Caddy in ease of use, sign me up!

Yeah, I want to keep my LDAP. Whatever sits on top has to use it as a backend.

There’s also the going in got a glass of water and being found an hour later by your friend because you got such watching the sink drip :-)

I’m not down on potheads. They’re my favorite inebriated people. I wish I could join them on their journeys, but alas my genetics gifted me with a paradoxical reaction to THC.

Why? I didn’t say that they were , only that someone in Lemmy has told me they were. I’m still not due they didn’t. I explicitly said I had no idea. And I posted the link to the comment in question, so there’s no doubt that they exchange actually happened.

I’m not taking a position on 50501 until I know more.

I don’t know. I don’t use Element; I wasn’t aware it requested location service access. I switched to FluffyChat ages ago; it only asks for notification.

But that’s just for group chat. I’ve been using Jami lately, and it does ask for location access; that’s because it has a “share location” feature, that - if you use it - shows a little map with your location to the person you’re sharing with. Maybe Element has implemented something similar?

Yes! I’ve used that page extensively. It doesn’t, however, address SSO.

Thanks! Two for Authentik.