banger180 | 1 year ago | on: Google’s OAuth login doesn’t protect against purchasing a failed startup domain
banger180's comments
banger180 | 1 year ago | on: Google’s OAuth login doesn’t protect against purchasing a failed startup domain
What I don't understand is why the `sub` claim is not consistent for those users at Google. To my understanding of the OIDC protocol the `sub` should be unique for a specific user.
Additionally as far as I understand if you take over a defunct domain and create a new google workspace with new users those new user account should get assigned a new `sub`.
banger180 | 2 years ago | on: Flathub: One million active users and growing
banger180 | 4 years ago | on: USB-C is about to go from 100W to 240W, enough to power beefier laptops
banger180 | 5 years ago | on: Response to Flatkill.org
Maintaining one package that works on all distros is a lot easier.
banger180 | 5 years ago | on: The Signal Server repository has not been updated since April 2020
banger180 | 5 years ago | on: This Week in Matrix 2021-01-08
If you run your own homeserver you are completely independent and don't rely on anyone else.
If you want to join the federation and talk to people on other homeservers you do need a publicly accessible web server with a valid TLS certificate (which you can get for free from let's encrypt).
If you only want to chat with people on the same server you can choose not to join the federation, but this is not what matrix was designed for.
> those homeservers seem very public by default if you just want one for your personal use.
You can disallow public user creation in the homeserver config. Then only users you have created can access your homeserver. Of course anyon in the federation can invite your users to a room etc.
> Which makes it seem a bit risky
I don't think there is a very large risk to running your own homeserver (not more than running other services).
A matrix homeserver can require quite some resources depending on how many users you host and how large the rooms are. Also there is some normal administration required (updating, making sure the cert is valid, ...).
banger180 | 5 years ago | on: How Discord (somewhat accidentally) invented the future of the internet
I would love for matrix to eventually replace discord, but ATM discord is still a better user experience.
banger180 | 5 years ago | on: Huawei’s HarmonyOS is now open source
banger180 | 5 years ago | on: The Day AppGet Died
APT is the classic tool for debian-like Linux distributions. FTFY
banger180 | 5 years ago | on: Ubuntu 20.04 LTS’ snap obsession has snapped me off of it
banger180 | 5 years ago | on: Zoom 5.0
It would be interesting if they found a way to watermark the audio in such a way that removing the mark makes the audio unusable.
banger180 | 5 years ago | on: Ask HN: Best current mailing list manager?
It is infidelity inspired by the layout of a forum, but looks great IMO.
banger180 | 6 years ago | on: ICANN delays .org selloff after California’s attorney general intervenes
banger180 | 6 years ago | on: Curl will now output JSON
banger180 | 6 years ago | on: Share Now, formerly Car2Go, is leaving North America
banger180 | 6 years ago | on: Websites can change content inside a selection
banger180 | 6 years ago | on: Guess I'm Done with Discord
banger180 | 6 years ago | on: Google's Quantum Processor May Achieve Quantum Supremacy in Months
Indeed this would be very interesting.
This issue is also very similar to CVE-2024-25618.
What we did to mitigate this is the following: - Federated login with OIDC - Look for a user based on the sub claim - If they are found: authenticate that user and optionally update their profile (email, name, ...) based on then new id claims. - Else look for a user matching on the `email` claim and link the `sub` to that user - If no user is found create a new one