lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

63
active users

#oauth

1 post1 participant0 posts today
Joe Steinbring :thisisfine:<p>I got n8n working with LinkedIn, Mastodon, etc. Can I get it to work with Fitbit? :blobcatthink: </p><p><a href="https://toot.works/tags/Homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Homelab</span></a> <a href="https://toot.works/tags/n8n" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>n8n</span></a> <a href="https://toot.works/tags/OAuth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OAuth</span></a></p>
Erik Play2Learn<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@elmiko" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>elmiko</span></a></span> in my python tests <a href="https://mastodon.social/tags/GeminiAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GeminiAI</span></a> has been pretty good. So galang doesn't worry me that much. Interestingly multiple AIs struggle with <a href="https://mastodon.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a>, eg also <a href="https://mastodon.social/tags/lovable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>lovable</span></a> .</p><p>There aren't even free standing computers and library employees not respecting documentation standards pisses me off. So i have to check now if another library has a free computer. It's already the second library. In the first ive got <a href="https://mastodon.social/tags/hausverbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hausverbot</span></a> because I dont want to be <a href="https://mastodon.social/tags/homeless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homeless</span></a> anymore, see other thread on this masto account.</p>
Erik Play2Learn<p><span class="h-card" translate="no"><a href="https://chaos.social/@netzpolitik_feed" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>netzpolitik_feed</span></a></span> Haben die <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>EUCommission</span></a></span> Kollegen schon mal von <a href="https://mastodon.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> gehört? Ein großer Teil der Anfrage-Verwaltung ist damit technisch schon gelöst.</p>
skry<p><a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> Alert hijack attack <a href="https://www.bleepingcomputer.com/news/security/fake-security-alert-issues-on-github-use-oauth-app-to-hijack-accounts/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/fake-security-alert-issues-on-github-use-oauth-app-to-hijack-accounts/</span></a><br><a href="https://mastodon.social/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://mastodon.social/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dev</span></a> <a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdev</span></a> <a href="https://mastodon.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a></p>
C.<p><a href="https://mindly.social/tags/Fedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fedi</span></a>, looking for people with experience in <a href="https://mindly.social/tags/accessible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>accessible</span></a> software.</p><p>I have a friend with serious vision issues. Not blind, but can't easily read text that isn't 6+ inches high, and his vision is degrading. He is looking for a way to deal with email -- he's a writer -- because he says Gmail is now a nightmare to use even with a screen reader.</p><p>Preferred solution would be a mail program / <a href="https://mindly.social/tags/MUA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MUA</span></a> that runs on Windows and supports <a href="https://mindly.social/tags/OAUTH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OAUTH</span></a> authentication, so he can continue to use his Gmail address.</p><p>What's the MUA with the best <a href="https://mindly.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>accessibility</span></a> on Windows? Thunderbird brags about its support for screen readers and assistive technologies, so I had him try it, and he says it's almost as bad as Gmail - flashing colours, animating controls. I haven't personally touched Thunderbird in many years, so it was a surprise to me.</p><p>I use a text/console mail flow that relies on a local MTA, so nothing I use is of any use in this.</p><p>Thanks, appreciate any pointers.</p><p><a href="https://mindly.social/tags/mail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mail</span></a> <a href="https://mindly.social/tags/MailProgram" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MailProgram</span></a> <a href="https://mindly.social/tags/GMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GMail</span></a> <a href="https://mindly.social/tags/AssistiveTechnology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AssistiveTechnology</span></a> <a href="https://mindly.social/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a> <a href="https://mindly.social/tags/blind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>blind</span></a> <a href="https://mindly.social/tags/vision" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vision</span></a> <a href="https://mindly.social/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>software</span></a> <a href="https://mindly.social/tags/disability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>disability</span></a></p>
Aaron PareckiAt long last, the OAuth working group has finished the Best Current Practice for OAuth 2.0 Security and it was just published as RFC9700! This has been a long time in the works, and I'm very thankful to everyone who has helped out with it over the years! <br> <br><a href="https://www.rfc-editor.org/rfc/rfc9700.html" rel="nofollow noopener noreferrer" target="_blank"><span class="">https://</span>www.rfc-editor.org/rfc/rfc9700.html</a> <br> <br>This is one of the major inputs to OAuth 2.1, so I'm also very excited to be able to move that forward this year as well!
Francis Augusto 🇳🇴/🇧🇷/:bahia:<p>A little rant about e-mail authentication: </p><p><a href="https://francisaugusto.com/2025/Email-quo-vadis-or-where-is-oidc-for-everyone/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">francisaugusto.com/2025/Email-</span><span class="invisible">quo-vadis-or-where-is-oidc-for-everyone/</span></a></p><p><span class="h-card" translate="no"><a href="https://io.mwl.io/@mwl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mwl</span></a></span> I'd love your comment on this!</p><p><a href="https://mastodon.babb.no/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://mastodon.babb.no/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> <a href="https://mastodon.babb.no/tags/oauth2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth2</span></a> <a href="https://mastodon.babb.no/tags/thunderbird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>thunderbird</span></a></p>
Paul Keen<p>OAuth security is broken! A domain switch can hijack Google sign-in accounts. This affects your apps and users right now. <a href="https://ruby.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://ruby.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> <a href="https://ruby.social/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://trufflesecurity.com/blog/millions-at-risk-due-to-google-s-oauth-flaw" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">trufflesecurity.com/blog/milli</span><span class="invisible">ons-at-risk-due-to-google-s-oauth-flaw</span></a></p>
Terence Eden<p>🆕 blog! “Add a custom icon to Auth0's Custom Social integrations”</p><p>This is so fucking stupid.</p><p>There is no way to update the logo of a custom social connection on Auth0 without using the command line. On literally every other service I've used, there's a little box to upload a logo. But Okta have a funny idea of what developers want.</p><p>And, to make matters…</p><p>👀 Read more: <a href="https://shkspr.mobi/blog/2024/12/add-a-custom-icon-to-auth0s-custom-social-integrations/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">shkspr.mobi/blog/2024/12/add-a</span><span class="invisible">-custom-icon-to-auth0s-custom-social-integrations/</span></a><br>⸻<br><a href="https://mastodon.social/tags/Auth0" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Auth0</span></a> <a href="https://mastodon.social/tags/HowTo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HowTo</span></a> <a href="https://mastodon.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a></p>
Terence Eden<p>🆕 blog! “Creating a generic "Log-in with Mastodon" service”</p><p>…</p><p>👀 Read more: <a href="https://shkspr.mobi/blog/2024/12/creating-a-generic-log-in-with-mastodon-service/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">shkspr.mobi/blog/2024/12/creat</span><span class="invisible">ing-a-generic-log-in-with-mastodon-service/</span></a><br>⸻<br><a href="https://mastodon.social/tags/Auth0" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Auth0</span></a> <a href="https://mastodon.social/tags/MastodonAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MastodonAPI</span></a> <a href="https://mastodon.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a></p>
Stefan Bohacek<p>Has anyone made a good, reliable "log in with your fediverse account" library/service, ideally for node.js, yet?</p><p><a href="https://stefanbohacek.online/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fediverse</span></a> <a href="https://stefanbohacek.online/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> <a href="https://stefanbohacek.online/tags/nodejs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nodejs</span></a> <a href="https://stefanbohacek.online/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a></p>
bryan newbold<p>We got a blog post out summarizing our launch of OAuth for AT Protocol, and what work remains. This has been a huge project, led by Matthieu, with input from a bunch of standards folks and devs.</p><p>This tries to solve the same basic challenge that ActivityPub has, and builds on work by <span class="h-card" translate="no"><a href="https://hachyderm.io/@thisismissem" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>thisismissem</span></a></span> and <span class="h-card" translate="no"><a href="https://aaronparecki.com/aaronpk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>aaronpk</span></a></span> at the IETF (OAuth client metadata documents). Would be great if social web protocols end up aligning on the general shape of a solution and care share code+review.</p><p><a href="https://social.coop/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> <a href="https://social.coop/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a></p>
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<p>Say you're building a form that allows a user to login to <a href="https://mastodon.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a>. First you need their hostname. You want to validate that it's a URL before you allow the form to be submitted, but typing `https://` is kind of a pain in the ass. So you could add an onblur that prepends the protocol if the user hadn't done it themselves. </p><p>thoughts?</p><p><a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webDev</span></a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>html</span></a> <a href="https://mastodon.social/tags/javaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>javaScript</span></a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>development</span></a> <a href="https://mastodon.social/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> <a href="https://mastodon.social/tags/form" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>form</span></a> <a href="https://mastodon.social/tags/frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>frontend</span></a> <a href="https://mastodon.social/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>web</span></a></p>
Michael :donor:<p>Need some feedback from people working in <a href="https://infosec.exchange/tags/IAM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IAM</span></a> about the co-existence of passkeys and security keys for FIDO2.</p><p>How should you handle giving people the option to use security keys for non-resident credentials.</p><p>I have read the latest UX best practices proposed by the FIDO alliance, and I will probably go down the route proposed there, I'll offer two buttons "Create passkey" and "Use a security key". They trigger webauthn registration with different parameters, the "use a security key" uses residentKey=discouraged.</p><p>It seems like that is similar to what Google and Github do. However, in the aforementioned FIDO best practice the "future state" shows that the FIDO alliance thinks that the "use a security key" button may become obsolete in the future. Why? Is this assuming that browsers will implement better controls where the user can decide whether to create a resident key? Because I don't intend to take away this decision from advanced users who have hardware keys with limited credential storage slots.</p><p>Also, what webauthn registration parameters would you use for those two buttons? I am currently doing:</p><p>---<br>Create passkey:<br>uv=preferred<br>rk=preferred</p><p>Use a security key:<br>uv=preferred<br>rk=discouraged<br>attachment=cross-platform<br>---</p><p>FIDO Best practices mentioned above: <a href="https://fidoalliance.org/design-guidelines/patterns/passkey-management-ui-best-practices-for-combining-all-passkey-types/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">fidoalliance.org/design-guidel</span><span class="invisible">ines/patterns/passkey-management-ui-best-practices-for-combining-all-passkey-types/</span></a></p><p><a href="https://infosec.exchange/tags/identity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>identity</span></a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>authentication</span></a> <a href="https://infosec.exchange/tags/passkeys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>passkeys</span></a> <a href="https://infosec.exchange/tags/yubikey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>yubikey</span></a> <a href="https://infosec.exchange/tags/iam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iam</span></a> <a href="https://infosec.exchange/tags/idp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>idp</span></a> <a href="https://infosec.exchange/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> <a href="https://infosec.exchange/tags/openid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openid</span></a> <a href="https://infosec.exchange/tags/fido" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fido</span></a></p>
Mathias Panzenböck<p>Is there some kind of framework for <a href="https://chaos.social/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>API</span></a> services that already has everything pre-defined except the actual API? Meaning user management with <a href="https://chaos.social/tags/2FA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>2FA</span></a>, <a href="https://chaos.social/tags/OAuth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OAuth</span></a> client handling, Stripe integration for usage based or flat-rate plans, API usage stats, email notifications, a background jobs running on multiple machines? Preferable in <a href="https://chaos.social/tags/NodeJS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NodeJS</span></a> or <a href="https://chaos.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a>, but really can be any language as long as the background job can be in any language I want/need because of dependencies. <a href="https://chaos.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://chaos.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdev</span></a></p>
Jupiter Rowland@<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener noreferrer" target="_blank">Stefan Bohacek</a> To add to your table:<br><br><a href="https://framagit.org/hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> supports nodeinfo 2.0 and 2.1.<br><br>Examples from a stable release, just to show that they can differ, depending on how a hub is configured:<br><a href="https://hub.netzgemeinde.eu/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://hub.netzgemeinde.eu/.well-known/nodeinfo</a><br><a href="https://im.allmendenetz.de/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://im.allmendenetz.de/.well-known/nodeinfo</a><br><a href="https://klacker.org/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://klacker.org/.well-known/nodeinfo</a><br><a href="https://hubzilla.monster/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://hubzilla.monster/.well-known/nodeinfo</a><br><br>Example from a development release:<br><a href="https://zotum.net/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://zotum.net/.well-known/nodeinfo</a><br><br>However, it looks like nodeinfo can be turned off entirely by the hubmin. At least hubzilla.org has a blank nodeinfo page.<br><br><a href="https://codeberg.org/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> always has a blank nodeinfo page. Most nodeinfo code has intentionally been removed. It understands nodeinfo, but it seems to send something else instead which it only understands itself, which is limited in what information it offers, and which isn't parsed by Fediverse stats/instance-listing websites.<br><br>By the way: Both Hubzilla and (streams) support both OAuth and OAuth2 both as a client and as a server. However, Hubzilla's documentation is painfully outdated in this regard; parts of it still refer to Red, so they were last touched before the name change to Red Matrix. And (streams) doesn't have any documentation.<br><br>Also, Hubzilla and (streams) are the only Fediverse server applications with full, i.e. both server-side and client-side support for OpenWebAuth single sign-on.<br><br>CC: @<a href="https://infosec.exchange/@kpwn" rel="nofollow noopener noreferrer" target="_blank">Konstantin :C_H:</a><br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OAuth" rel="nofollow noopener noreferrer" target="_blank">OAuth</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OAuth2" rel="nofollow noopener noreferrer" target="_blank">OAuth2</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Nodeinfo" rel="nofollow noopener noreferrer" target="_blank">Nodeinfo</a>
Aaron Parecki<p>FedCM for IndieAuth</p><p><a href="https://aaronparecki.com/2024/05/12/3/fedcm-for-indieauth" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">aaronparecki.com/2024/05/12/3/</span><span class="invisible">fedcm-for-indieauth</span></a></p>
Stefan Bohacek<p>Are there any known issues with Friendica's OAuth login flow? Or maybe recent breaking changes?</p><p>Suddenly getting an "Unprocessable Entity" error without having made any relevant updates to the code.</p><p><a href="https://stefanbohacek.online/tags/friendica" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>friendica</span></a> <a href="https://stefanbohacek.online/tags/FriendicaDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FriendicaDev</span></a> <a href="https://stefanbohacek.online/tags/FediDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FediDev</span></a> <a href="https://stefanbohacek.online/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a></p>
matdevdug<p>Whenever I have to write an <a href="https://c.im/tags/oauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>oauth</span></a> login the struggle is never getting it to work. I can always end up with a successful login. </p><p>Without fail I will finish, then go check the best practices guide and inevitably find out I messed something up. It’s just crazy for an “easy” protocol to have so many footguns. (<a href="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/html/</span><span class="invisible">draft-ietf-oauth-security-topics</span></a>)</p><p><a href="https://c.im/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://c.im/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a></p>
Emelia 👸🏻<p>I fundamentally do not think it is wise for the ActivityPub community to be completely reimagining how an existing standard should be implemented, especially in a way that only satisfies the needs of a single client type.</p><p><a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/d8c2/fep-d8c2.md" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/fediverse/fep/src</span><span class="invisible">/branch/main/fep/d8c2/fep-d8c2.md</span></a></p><p>I have a fuller objection to this FEP here: <a href="https://socialhub.activitypub.rocks/t/fep-d8c2-oauth-2-0-profile-for-the-activitypub-api/3575/20?u=thisismissem" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">socialhub.activitypub.rocks/t/</span><span class="invisible">fep-d8c2-oauth-2-0-profile-for-the-activitypub-api/3575/20?u=thisismissem</span></a></p><p><a href="https://hachyderm.io/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActivityPub</span></a> <a href="https://hachyderm.io/tags/OAuth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OAuth</span></a> <a href="https://hachyderm.io/tags/FediDevs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FediDevs</span></a></p>