• 2 Posts
  • 19 Comments
Joined 11 months ago
cake
Cake day: June 7th, 2025

help-circle



  • Yeah, I agree with Authelia feeling brittle. I have seen a lot of people switch from traefik to caddy, and I am definitely considering it at this point - I am a bit worried about the lack of GUI as it is definitely easier to see if something is wrong by opening that up (when it actually works) than reading logs, but i also heard caddy has a plugin for a GUI?

    I have considered looking at proxmox, but i don’t think i do enough vm’s to justify it, and I dont have any dedicated WAP’s so OPNSense just isnt worth it for me, though if that ever changes I would definitely consider it.


  • honestly too poor for backup storage atm, I have a manual backup of my important shit, but definitely not a robust setup.

    A few people have recommended kanidm, definitely going to look at it - not the biggest fan of Authelia at this point. No real defaults, a ton of configuration steps you need to follow, and SSO was a pain to setup last time I looked.

    I have been considering caddy, as traefik has a few weird issues - for example, returning ‘I’m a teapot’ instead of its web frontend for no reason sometimes. Also, its near impossible to get useable certs to share with other services - it stores them in its own format, and the conversion tools dont really work.










  • The apps that enable tap-for-payment ask your bank for permission and some security details to activate using cards for NFC.

    In North America, banks won’t give that permission/security info to any android app but google pay, and only if the play store verification thing says the OS is fully secure - and google pretends grapheneos doesn’t hit those security metrics.

    So yes, NFC is how tap-for-payment works, but unless NA banks implement it themselves, or trust a 3rd party that isn’t google to implement it, grapheneos phones are blocked from using the tap-for-payment functionality.