antsu

@antsu@lemmy.wtf

• ⁨Comment⁩ on ⁨Bet this guy is a great tutor for your kids⁩ ⁨⁨2⁩ ⁨days⁩ ago⁩:

  British Mastodon user.

• ⁨Comment⁩ on ⁨Let's hear it, little lemmings.⁩ ⁨⁨5⁩ ⁨days⁩ ago⁩:

  Can I pick 2 and have them talk to each other instead? Would love to watch Hawking get Newton up to speed on some stuff.

• ⁨Comment⁩ on ⁨I love bpd girls⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I read this as “bipedal girls”. Me too, love me a nice pair of legs.

• ⁨Comment⁩ on ⁨I have tomorrow off :)⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  That’s WALL-E.

• ⁨Comment⁩ on ⁨Deploy Authentik to already working services and accounts.⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Your top priority should be “Are my backups good? / Can I trivially roll back any breaking changes?” If an account oopsie can permanently compromise your users’ photos, then you have bigger problems to worry about.

  But assuming your backups are good, there isn’t much to worry about. I recommend you don’t take my word for it and thoroughly read the documentation of each of the services you want to put behind Authentik, but in general, when a service is configured to use SSO, if a user with the same ID already exists on the target service, they are simply merged. The most common ID for this is the email associated with that user on both Authentik and the service. Worst case, if the ID doesn’t match, you either get an error saying the user is invalid or you get a new user created on the target service.

• ⁨Comment⁩ on ⁨North Korea and South Korea isn't working. Let's try West Korea and East Korea instead.⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  It’s Koreas all the way down.

• ⁨Comment⁩ on ⁨Looking for ... inventory management, I guess?⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  +1
  This is a problem a simple spreadsheet is perfectly adequate for.