Source:
bskycheck.com
bskycheck.com/userinfo
www.reddit.com/r/BlueskySoc...
vqv.app
vqv.app/tools
The Top 1,000 Most Popular Bluesky Users + AI-Generated Statistics
bskycheck.com
bskycheck.com/userinfo
www.reddit.com/r/BlueskySoc...
vqv.app
vqv.app/tools
The Top 1,000 Most Popular Bluesky Users + AI-Generated Statistics
June 3, 2026 at 2:17 AM
Source:
bskycheck.com
bskycheck.com/userinfo
www.reddit.com/r/BlueskySoc...
vqv.app
vqv.app/tools
The Top 1,000 Most Popular Bluesky Users + AI-Generated Statistics
bskycheck.com
bskycheck.com/userinfo
www.reddit.com/r/BlueskySoc...
vqv.app
vqv.app/tools
The Top 1,000 Most Popular Bluesky Users + AI-Generated Statistics
there is 2 different way of creating an object in V8 with known keys and values. one of them is slow, one of them is fast. github.com/nodejs/node/...
src: improve `node:os` userInfo performance by anonrig · Pull Request #55719 · nodejs/node
Improve node:os userInfo performance by reducing the cost of creating a v8::Object.
github.com
November 5, 2024 at 7:40 PM
there is 2 different way of creating an object in V8 with known keys and values. one of them is slow, one of them is fast. github.com/nodejs/node/...
if we do want oidc in atproto oauth we'd have to implement this anyway i suppose, for the userinfo endpoint
November 28, 2024 at 10:21 PM
if we do want oidc in atproto oauth we'd have to implement this anyway i suppose, for the userinfo endpoint
By defining authority as: [ userinfo "@" ] host [ ":" port ]
rfc3986 fundamentally constraints the use of URIs in decentralized contexts
Since there seems to be some energy in the IETF to adopt more decentralized protocols (as ATP is proof of), "moving the mountain" might not be that inconceivable.
rfc3986 fundamentally constraints the use of URIs in decentralized contexts
Since there seems to be some energy in the IETF to adopt more decentralized protocols (as ATP is proof of), "moving the mountain" might not be that inconceivable.
June 30, 2026 at 12:28 PM
By defining authority as: [ userinfo "@" ] host [ ":" port ]
rfc3986 fundamentally constraints the use of URIs in decentralized contexts
Since there seems to be some energy in the IETF to adopt more decentralized protocols (as ATP is proof of), "moving the mountain" might not be that inconceivable.
rfc3986 fundamentally constraints the use of URIs in decentralized contexts
Since there seems to be some energy in the IETF to adopt more decentralized protocols (as ATP is proof of), "moving the mountain" might not be that inconceivable.
@bnewbold.net does AT Protocol's OAuth support the `profile` scope and userinfo endpoint from OIDC? We're considering these for Mastodon: github.com/mastodon/mas...
(essentially a stripped down version of the Account entity in Mastodon, or the DID in At Protocol is how I'd think of these)
(essentially a stripped down version of the Account entity in Mastodon, or the DID in At Protocol is how I'd think of these)
Add userinfo endpoint for OAuth · Issue #31257 · mastodon/mastodon
Pitch Currently mastodon has an endpoint that is GET /api/v1/accounts/verify_credentials which returns information on the currently authenticated user. The "standard" way via OIDC would be to suppo...
github.com
October 5, 2024 at 6:06 PM
@bnewbold.net does AT Protocol's OAuth support the `profile` scope and userinfo endpoint from OIDC? We're considering these for Mastodon: github.com/mastodon/mas...
(essentially a stripped down version of the Account entity in Mastodon, or the DID in At Protocol is how I'd think of these)
(essentially a stripped down version of the Account entity in Mastodon, or the DID in At Protocol is how I'd think of these)
📦 jeffersongoncalves/laravel-sso-client 1.1.0
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
September 25, 2026 at 12:55 AM
📦 jeffersongoncalves/laravel-sso-client 1.1.0
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
📦 jeffersongoncalves/laravel-sso-client 1.0.0
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
September 25, 2026 at 12:55 AM
📦 jeffersongoncalves/laravel-sso-client 1.0.0
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
SSO client for Laravel: Authorization Code + PKCE login, RS256/JWKS or signed userinfo token validation, user sync and back-channel Single Logout.
🔗 https://github.com/jeffersongoncalves/laravel-sso-client
Nothing says you have a subculture that really values creativity and independent thought like FOUR of them turning up with precisely uniform userinfo. What, were identical brownshirts too expensive?😏
November 21, 2024 at 9:42 PM
Nothing says you have a subculture that really values creativity and independent thought like FOUR of them turning up with precisely uniform userinfo. What, were identical brownshirts too expensive?😏
kurze bsky-userinfo:
Erstmal: Eure Blocks sind öffentlich sichtbar. Nicht in bsky selbst, aber im verwendeten Protokoll.
Da das mit dem zurückblocken hier ein bisschen schwierig ist, weil man die User nichtmehr findet, ist das aber ein Vorteil, weil es gibt ein Tool zum Nachschauen von zB Blocks:
Erstmal: Eure Blocks sind öffentlich sichtbar. Nicht in bsky selbst, aber im verwendeten Protokoll.
Da das mit dem zurückblocken hier ein bisschen schwierig ist, weil man die User nichtmehr findet, ist das aber ein Vorteil, weil es gibt ein Tool zum Nachschauen von zB Blocks:
ClearSky Search ToolLoadingClearSky Search ToolClearSky Search ToolClearSky Search ToolClearSky Sear...
bsky.thieflord.dev
August 20, 2023 at 11:19 AM
kurze bsky-userinfo:
Erstmal: Eure Blocks sind öffentlich sichtbar. Nicht in bsky selbst, aber im verwendeten Protokoll.
Da das mit dem zurückblocken hier ein bisschen schwierig ist, weil man die User nichtmehr findet, ist das aber ein Vorteil, weil es gibt ein Tool zum Nachschauen von zB Blocks:
Erstmal: Eure Blocks sind öffentlich sichtbar. Nicht in bsky selbst, aber im verwendeten Protokoll.
Da das mit dem zurückblocken hier ein bisschen schwierig ist, weil man die User nichtmehr findet, ist das aber ein Vorteil, weil es gibt ein Tool zum Nachschauen von zB Blocks:
The double dashes signal that the "authority" ([userinfo@]host[:port]) comes next.
foo:bar/baz/quux is an opaque URI
foo:/bar/baz/quux is hierarchical, but has only a path, no authority
foo:bar/baz/quux is an opaque URI
foo:/bar/baz/quux is hierarchical, but has only a path, no authority
November 1, 2024 at 8:06 PM
The double dashes signal that the "authority" ([userinfo@]host[:port]) comes next.
foo:bar/baz/quux is an opaque URI
foo:/bar/baz/quux is hierarchical, but has only a path, no authority
foo:bar/baz/quux is an opaque URI
foo:/bar/baz/quux is hierarchical, but has only a path, no authority
ope, let me just check if that's a valid URI real quick
January 26, 2025 at 4:06 PM
ope, let me just check if that's a valid URI real quick
i dont think it would work within the context of atproto, because profiles are an app-level concern and not the protocol
bluesky's profile records being used for userinfo wouldn't be great, i believe that's why the oidc scopes were removed (it was present initially)
bluesky's profile records being used for userinfo wouldn't be great, i believe that's why the oidc scopes were removed (it was present initially)
October 6, 2024 at 4:15 AM
i dont think it would work within the context of atproto, because profiles are an app-level concern and not the protocol
bluesky's profile records being used for userinfo wouldn't be great, i believe that's why the oidc scopes were removed (it was present initially)
bluesky's profile records being used for userinfo wouldn't be great, i believe that's why the oidc scopes were removed (it was present initially)
true to my userinfo, i am elbow deep in metaphor refantazio now so please feel free to yell at me about it. still early on bc things got busy and i'm about to host a few dear friends for a few days, but!!
October 17, 2024 at 5:01 PM
true to my userinfo, i am elbow deep in metaphor refantazio now so please feel free to yell at me about it. still early on bc things got busy and i'm about to host a few dear friends for a few days, but!!
At first, we tried to make our implementation OIDC compatible. As such "openid", "profile" scopes, id tokens and "/userinfo" were all supported.
Then we realized that there is a fundamental incompatibility between OpenID and our user identifiers.
So we dropped most of the OIDC code.
Then we realized that there is a fundamental incompatibility between OpenID and our user identifiers.
So we dropped most of the OIDC code.
October 7, 2024 at 9:04 AM
At first, we tried to make our implementation OIDC compatible. As such "openid", "profile" scopes, id tokens and "/userinfo" were all supported.
Then we realized that there is a fundamental incompatibility between OpenID and our user identifiers.
So we dropped most of the OIDC code.
Then we realized that there is a fundamental incompatibility between OpenID and our user identifiers.
So we dropped most of the OIDC code.
Try clicking this. Weird.
www.bbc.co.uk/userinfo
www.bbc.co.uk/userinfo
April 8, 2026 at 12:08 PM
Try clicking this. Weird.
www.bbc.co.uk/userinfo
www.bbc.co.uk/userinfo
userinfo
Username:
Ben/Dad
Former:
Award nominated illustrator
Best-selling cartoonist
Award nominated podcaster
Current:
Attempted author
Struggling stay-at-home parent x2
Operates Saga merch shop
Identifying features:
Anxiety disorder
Heavily tattooed
Dope spouse
Dial-up brain
Bot: negative
Username:
Ben/Dad
Former:
Award nominated illustrator
Best-selling cartoonist
Award nominated podcaster
Current:
Attempted author
Struggling stay-at-home parent x2
Operates Saga merch shop
Identifying features:
Anxiety disorder
Heavily tattooed
Dope spouse
Dial-up brain
Bot: negative
November 15, 2024 at 10:58 PM
userinfo
Username:
Ben/Dad
Former:
Award nominated illustrator
Best-selling cartoonist
Award nominated podcaster
Current:
Attempted author
Struggling stay-at-home parent x2
Operates Saga merch shop
Identifying features:
Anxiety disorder
Heavily tattooed
Dope spouse
Dial-up brain
Bot: negative
Username:
Ben/Dad
Former:
Award nominated illustrator
Best-selling cartoonist
Award nominated podcaster
Current:
Attempted author
Struggling stay-at-home parent x2
Operates Saga merch shop
Identifying features:
Anxiety disorder
Heavily tattooed
Dope spouse
Dial-up brain
Bot: negative
That & some other evidence act as “side channel leaks” that show that Reddit doesn’t actually delete usernames/ userinfo when users delete their accounts, just puts up a [deleted user] interstitial in place of displaying the username if the account has a flag set
December 29, 2023 at 3:21 AM
That & some other evidence act as “side channel leaks” that show that Reddit doesn’t actually delete usernames/ userinfo when users delete their accounts, just puts up a [deleted user] interstitial in place of displaying the username if the account has a flag set
Given what we now know of Twitter’s userinfo security model …
February 5, 2024 at 7:09 PM
Given what we now know of Twitter’s userinfo security model …
We could borrow some OIDC stuff, such as the "/userinfo" endpoint.
We didn't because we already have atproto endpoint to achieve this, and because we want to keep the requirements needed to implement a PDS as light as possibe.
We didn't because we already have atproto endpoint to achieve this, and because we want to keep the requirements needed to implement a PDS as light as possibe.
October 7, 2024 at 9:08 AM
We could borrow some OIDC stuff, such as the "/userinfo" endpoint.
We didn't because we already have atproto endpoint to achieve this, and because we want to keep the requirements needed to implement a PDS as light as possibe.
We didn't because we already have atproto endpoint to achieve this, and because we want to keep the requirements needed to implement a PDS as light as possibe.
I can only assume that is part of the issues contributing to Spoutible’s reported userinfo breach.
A public facing db instance can’t leak a password hash through a user details api if it’s not there to leak
A public facing db instance can’t leak a password hash through a user details api if it’s not there to leak
February 5, 2024 at 7:44 PM
I can only assume that is part of the issues contributing to Spoutible’s reported userinfo breach.
A public facing db instance can’t leak a password hash through a user details api if it’s not there to leak
A public facing db instance can’t leak a password hash through a user details api if it’s not there to leak
SMS-delivered phish, abusing UserInfo spoofing and guiding user to disabling link protections by replying to the message.
August 25, 2025 at 1:45 PM
SMS-delivered phish, abusing UserInfo spoofing and guiding user to disabling link protections by replying to the message.
🚀 Swift 6.2's brand new concurrency-safe notification system is here!
Solving the three major pain points of traditional NotificationCenter:
❌ Error-prone string identifiers
❌ Poor type safety with userInfo
❌ Unclear thread behavior
fatbobman.com/en/posts/not...
Solving the three major pain points of traditional NotificationCenter:
❌ Error-prone string identifiers
❌ Poor type safety with userInfo
❌ Unclear thread behavior
fatbobman.com/en/posts/not...
NotificationCenter.Message - A New Concurrency-Safe Notification Experience in Swift 6.2
Discover Swift 6.2’s new concurrency-safe NotificationCenter.Message APIs to ensure type safety, eliminate runtime errors, and streamline notification handling.
fatbobman.com
June 25, 2025 at 12:24 PM
🚀 Swift 6.2's brand new concurrency-safe notification system is here!
Solving the three major pain points of traditional NotificationCenter:
❌ Error-prone string identifiers
❌ Poor type safety with userInfo
❌ Unclear thread behavior
fatbobman.com/en/posts/not...
Solving the three major pain points of traditional NotificationCenter:
❌ Error-prone string identifiers
❌ Poor type safety with userInfo
❌ Unclear thread behavior
fatbobman.com/en/posts/not...
Love this idea :)
iPhone 14 Plus installed app
Tried to download R1 got errors
iPhone 14 Plus installed app
Tried to download R1 got errors
![Screenshot error message - Failed: dataCorrupted(Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data was not valid JSON.", underlyingError: Optional(Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected character '<' around line 1, column 1." UserInfo={NSJSONSerializationErrorIndex=0, NSDebugDescription=Unexpected character '<' around line 1, column 1.})))](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:dk3iwtkbpdovkfcauplleken/bafkreictlhlsqvygd2o6okd5glgupdv2lnqlbt4euww4trvs6mv5jkfcqm)
February 12, 2025 at 2:36 PM
Love this idea :)
iPhone 14 Plus installed app
Tried to download R1 got errors
iPhone 14 Plus installed app
Tried to download R1 got errors
#Tech #TechCEO’s #TechMoralResponsibility
#TechCrunch
#FreeSpeech
#TechWorkers > Thank You
for helping us all with more conscious #Values
> NO #UserInfo TO #DHS
💲☠️🇺🇸☠️💲
#TechCrunch
#FreeSpeech
#TechWorkers > Thank You
for helping us all with more conscious #Values
> NO #UserInfo TO #DHS
💲☠️🇺🇸☠️💲
February 10, 2026 at 6:07 PM
#Tech #TechCEO’s #TechMoralResponsibility
#TechCrunch
#FreeSpeech
#TechWorkers > Thank You
for helping us all with more conscious #Values
> NO #UserInfo TO #DHS
💲☠️🇺🇸☠️💲
#TechCrunch
#FreeSpeech
#TechWorkers > Thank You
for helping us all with more conscious #Values
> NO #UserInfo TO #DHS
💲☠️🇺🇸☠️💲
It's great to have typed Notifications!
No need for userInfo lookups or manual casting anymore. For example, KeyboardWillShowMessage will contain the animation curve and duration.
Documentation: developer.apple.com/documentatio...
#WWDC25
No need for userInfo lookups or manual casting anymore. For example, KeyboardWillShowMessage will contain the animation curve and duration.
Documentation: developer.apple.com/documentatio...
#WWDC25
June 10, 2025 at 9:59 AM
It's great to have typed Notifications!
No need for userInfo lookups or manual casting anymore. For example, KeyboardWillShowMessage will contain the animation curve and duration.
Documentation: developer.apple.com/documentatio...
#WWDC25
No need for userInfo lookups or manual casting anymore. For example, KeyboardWillShowMessage will contain the animation curve and duration.
Documentation: developer.apple.com/documentatio...
#WWDC25