Long Ngo
@longngo0617.bsky.social
Reposted by Long Ngo
fantastic article from @alan.norbauer.com about “Relay-style GraphQL”. i think these ideas haven’t been as broadly understood in the open source react graphql community as they deserve to be. (the exact comparisons with Apollo might be somewhat outdated; i have not checked. principles are solid.)
Relay-style GraphQL
GraphQL best practices for 2023
alan.norbauer.com
May 21, 2025 at 2:21 AM
fantastic article from @alan.norbauer.com about “Relay-style GraphQL”. i think these ideas haven’t been as broadly understood in the open source react graphql community as they deserve to be. (the exact comparisons with Apollo might be somewhat outdated; i have not checked. principles are solid.)
Reposted by Long Ngo
my main “bluesky tip” is simply — like and follow posts and people you enjoy seeing in your feed, and “show less” what you don’t enjoy.
“training” Discover algorithm takes annoyingly long for now — but it does get more specific with time, and the team will be making it more responsive. data helps.
“training” Discover algorithm takes annoyingly long for now — but it does get more specific with time, and the team will be making it more responsive. data helps.
November 8, 2024 at 11:30 AM
my main “bluesky tip” is simply — like and follow posts and people you enjoy seeing in your feed, and “show less” what you don’t enjoy.
“training” Discover algorithm takes annoyingly long for now — but it does get more specific with time, and the team will be making it more responsive. data helps.
“training” Discover algorithm takes annoyingly long for now — but it does get more specific with time, and the team will be making it more responsive. data helps.
Reposted by Long Ngo
atproto aha moments:
- you can host your data
- it's just json
- it's typed but any app dev can invent those types
- records have URIs
- records are signed so cacheable without trust
- relay aggregates everyone’s events into a global stream
- backends subscribe to relay and update local DBs
- you can host your data
- it's just json
- it's typed but any app dev can invent those types
- records have URIs
- records are signed so cacheable without trust
- relay aggregates everyone’s events into a global stream
- backends subscribe to relay and update local DBs
November 1, 2024 at 12:02 AM
atproto aha moments:
- you can host your data
- it's just json
- it's typed but any app dev can invent those types
- records have URIs
- records are signed so cacheable without trust
- relay aggregates everyone’s events into a global stream
- backends subscribe to relay and update local DBs
- you can host your data
- it's just json
- it's typed but any app dev can invent those types
- records have URIs
- records are signed so cacheable without trust
- relay aggregates everyone’s events into a global stream
- backends subscribe to relay and update local DBs
Reposted by Long Ngo
November 5, 2024 at 2:21 PM
Reposted by Long Ngo
🌠 For years, the #1 most requested feature in CSS was Container Queries. We wanted them so badly!
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
A Friendly Introduction to Container Queries • Josh W. Comeau
It’s been a couple of years since container queries started landing in browsers… so why isn’t anyone using them? It turns out that container queries are kinda tricky; they’re not as straightforward as...
www.joshwcomeau.com
November 4, 2024 at 4:36 PM
🌠 For years, the #1 most requested feature in CSS was Container Queries. We wanted them so badly!
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
Reposted by Long Ngo
old twitter friends — ask me anything about how bluesky/atproto works and i’ll try to answer!
November 3, 2024 at 8:44 PM
old twitter friends — ask me anything about how bluesky/atproto works and i’ll try to answer!
Reposted by Long Ngo
yup! there are other atproto apps tho:
- frontpage.fyi
- whtwnd.com
- smokesignal.events
they’re pretty barebones but show the potential
- frontpage.fyi
- whtwnd.com
- smokesignal.events
they’re pretty barebones but show the potential
i'm trying to understand the at protocol better.
in this diagram there are multiple applications. but currently there's only one application, right? the one run by the bluesky team?
(applications are different from clients, right?)
in this diagram there are multiple applications. but currently there's only one application, right? the one run by the bluesky team?
(applications are different from clients, right?)
i wonder if diagrams like these might help draw the distinction between ActivityPub (and how Mastodon uses it) and AT Protocol (and how it’s used by Bluesky and atproto apps)?
with AP, instance = application + hosting. data gets sent between instances.
with AT, data flows *from* hosting *to* apps
with AP, instance = application + hosting. data gets sent between instances.
with AT, data flows *from* hosting *to* apps
November 2, 2024 at 4:25 PM
yup! there are other atproto apps tho:
- frontpage.fyi
- whtwnd.com
- smokesignal.events
they’re pretty barebones but show the potential
- frontpage.fyi
- whtwnd.com
- smokesignal.events
they’re pretty barebones but show the potential
Reposted by Long Ngo
1. make it work
2. make it right
3. make it fast
4. make it work on android
2. make it right
3. make it fast
4. make it work on android
October 31, 2024 at 11:16 PM
1. make it work
2. make it right
3. make it fast
4. make it work on android
2. make it right
3. make it fast
4. make it work on android