neko
@neko.moe.observer
like and subscribe for ramblings about atproto, and copious reposts of moe/bishoujo illustrations. if you only like one or the other, i'm sorry- i'm sorry, i'm trying to fix it
it/its - sweden
it/its - sweden
Pinned
Reposted by neko
Reposted by neko
November 16, 2025 at 6:39 AM
Reposted by neko
November 17, 2025 at 6:00 AM
Reposted by neko
Reposted by neko
Reposted by neko
Reposted by neko
Reposted by neko
Reposted by neko
BIL-IL sent me this. Apparently this is one hundred percent real photo of a skydiver.
Titled: Icarus
Insane work.
Titled: Icarus
Insane work.
November 14, 2025 at 11:20 PM
BIL-IL sent me this. Apparently this is one hundred percent real photo of a skydiver.
Titled: Icarus
Insane work.
Titled: Icarus
Insane work.
Reposted by neko
November 16, 2025 at 11:06 AM
Reposted by neko
every service that's part of the chain would need to be able to handle did:twitter, but it's relatively little code that would just call out to a trusted service to fetch and format the data. then everything else would hopefully *just work*
November 16, 2025 at 10:59 AM
every service that's part of the chain would need to be able to handle did:twitter, but it's relatively little code that would just call out to a trusted service to fetch and format the data. then everything else would hopefully *just work*
Reposted by neko
every twitter user would get a did (did:twitter:1234), and every twitter post would get a pure atproto record (at://did:twitter:1234/host.ileinterop.com.twitter.post/5678) and a bsky-ified version (at://did:twitter:1234/app.bsky.feed.post/2222222222f4w) (tweet_id is u64, encode with base32-sortable)
November 16, 2025 at 10:59 AM
every twitter user would get a did (did:twitter:1234), and every twitter post would get a pure atproto record (at://did:twitter:1234/host.ileinterop.com.twitter.post/5678) and a bsky-ified version (at://did:twitter:1234/app.bsky.feed.post/2222222222f4w) (tweet_id is u64, encode with base32-sortable)
Reposted by neko
i realize i am very much trying to force a square peg in a round hole here but this is really just to reuse existing tooling and allow, well... interoperability! any service could skip this step if they wanted to, but i want existing feedgens and the like to just be able to represent tweets.
November 16, 2025 at 10:59 AM
i realize i am very much trying to force a square peg in a round hole here but this is really just to reuse existing tooling and allow, well... interoperability! any service could skip this step if they wanted to, but i want existing feedgens and the like to just be able to represent tweets.
Reposted by neko
in my mind, `did:twitter_id:1234` can't literally resolve to a did document somewhere, but it can conceptually resolve to one that's generated at request time by our custom twitter-did module that gets the request. these would only exist ephemerally in the service. could look something like this:
did:twitter:1234.json · by @neko.moe.observer
silly mockup for a standardized did document for hostile twitter read-only interoperability for bluesky users and atproto at large
tangled.org
November 16, 2025 at 10:59 AM
in my mind, `did:twitter_id:1234` can't literally resolve to a did document somewhere, but it can conceptually resolve to one that's generated at request time by our custom twitter-did module that gets the request. these would only exist ephemerally in the service. could look something like this:
Reposted by neko
what i want is ways to reference live data in the form of "i am reposting the x post with tweet_id 1234", "i follow x user with user_id 1234", and then every service that wants to make use of that data would have to either personally fetch that or make use of an intermediary like nitter(?).
November 16, 2025 at 10:59 AM
what i want is ways to reference live data in the form of "i am reposting the x post with tweet_id 1234", "i follow x user with user_id 1234", and then every service that wants to make use of that data would have to either personally fetch that or make use of an intermediary like nitter(?).
Reposted by neko
November 16, 2025 at 4:40 AM
Reposted by neko
Reposted by neko
Reposted by neko
koharu maido :3 she will become acrylic stand!
May 13, 2025 at 4:34 AM
koharu maido :3 she will become acrylic stand!
Reposted by neko
it looks like OAuth permission scopes are getting attention.
we know the stakes and urgency. we hoped to have this fully documented by now, and are very close. hold tight just a bit longer please
we know the stakes and urgency. we hoped to have this fully documented by now, and are very close. hold tight just a bit longer please
November 16, 2025 at 12:42 AM
it looks like OAuth permission scopes are getting attention.
we know the stakes and urgency. we hoped to have this fully documented by now, and are very close. hold tight just a bit longer please
we know the stakes and urgency. we hoped to have this fully documented by now, and are very close. hold tight just a bit longer please
Reposted by neko
This is true of Streamplace and every other ATProto OAuth application. This will change in the future when Bluesky lets us know that OAuth permission sets are ready for us to use. Until then, we don't have a choice!
November 15, 2025 at 11:58 PM
This is true of Streamplace and every other ATProto OAuth application. This will change in the future when Bluesky lets us know that OAuth permission sets are ready for us to use. Until then, we don't have a choice!
Reposted by neko
Getting some questions about Streamplace's login page, so wanted to do a quick clarification.
"Streamplace, why do you ask for so many permissions on my Bluesky account?"
Current guidance from Bluesky is that these are the scopes that should be requested by all production applications. That's it.
"Streamplace, why do you ask for so many permissions on my Bluesky account?"
Current guidance from Bluesky is that these are the scopes that should be requested by all production applications. That's it.
November 15, 2025 at 11:58 PM
Getting some questions about Streamplace's login page, so wanted to do a quick clarification.
"Streamplace, why do you ask for so many permissions on my Bluesky account?"
Current guidance from Bluesky is that these are the scopes that should be requested by all production applications. That's it.
"Streamplace, why do you ask for so many permissions on my Bluesky account?"
Current guidance from Bluesky is that these are the scopes that should be requested by all production applications. That's it.
Reposted by neko
Reposted by neko
the stress from this obviously frivolous lawsuit (which the corp won btw) was so bad it contributed to the deaths of the lead singer's father and the flute player which both happened within the span of a couple years. copyright law quite literally has resulted in creatives dying! fuck copyright law
November 15, 2025 at 8:38 PM
the stress from this obviously frivolous lawsuit (which the corp won btw) was so bad it contributed to the deaths of the lead singer's father and the flute player which both happened within the span of a couple years. copyright law quite literally has resulted in creatives dying! fuck copyright law