Or maybe CORS, it's always CORS isn't it ๐
Or maybe CORS, it's always CORS isn't it ๐
Weird, other did:webs work on pdsls. It's probably some did doc parsing edge case
Maybe this is something that pdsmoover could check and throw up a warning @baileytownsend.dev?
I'm actually surprised that a verification doesn't also include an avatar image too
The published record contains a DID, handle, and displayName that all have to match for the verification badge to show.
Another way of putting it, if you change your handle or display name then you will lose verification status.
Well isn't that just lovely?
Next.js already knew about this
nextjs.org/docs/app/api...
A novel benefit of SSR is that more errors are surfaced into the terminal where they can be read more easily by LLMs
I have let go of my hatred of pre commits by declaring them as a totally optional dev tool. As long as they're not enabled by default then I don't mind ๐
happy american football day to all those who celebrate
same UI but shows gulp and grunt together
it has gulp too wow
a screenshot of vscode showing "select the task to run" command pallette UI with grunt task options below
rip king ๐ซก
By pulling the entire repo of every user, probably using tap
"difference" has history in existing JS set utils implementations
@jimray.bsky.team slack has some special rate limits setup? If not then something very funky going on with Discord's implementation (I did suspect this tbh)
This is sick.
Are you folks at Slack running into the same problem as the folks at Discord with rate limits?
Recent thread about that here
If you haven't seen Moneyball, and sorry to explain the joke, Brad Pitt ends up changing the whole sport by rebuilding a player in the aggregate ๐
This definitely wasn't a criticism btw, I love to see it!
Guys you're still trying to replace raycast. I told you we can't do it. Now what we might be able to do is recreate it. Recreate it in the aggregate
I imagine that caching isn't really helping (and I assume they do it already) because they have many posts being posted a few times, so many cache misses. Discord are big enough to figure out how to maintain their own cache from the Relay though let's be real
> do we really want every company to run their own appview?
Yes! If a company is big enough to be hitting rate limits, they're big enough to figure out event streaming into their own infra
They can ingest bsky moderation events too, no need to do moderation themselves.
They don't need to run a Relay, they can use the Bluesky one.
Yeah I was going to suggest something like this. Sounds like you need an external store that you can subscribe to inside of your React components.
I don't think the different React components rendered inside MDX are different roots, so that shouldn't be a problem
What does it do?
Only thing it's missing IMO is the ability to plug in any post in the thread and it'll walk up/down to unroll it all.
Sure but that guide is specifically about creating a Bluesky feed. If any of those other stuff exists in the future then it can change, until then it doesn't belong in the AT docs
Fair enough for Osprey and Ozone!
I agree that feeds should not be Bsky specific but IMO this is very far away from the reality today to the point where this part of the docs is confusing
Some feedback here!
bsky.app/profile/did:plc:โฆ