Yohan Yukiya Sese Cuneta 사요한 🦋
@sera.is.youronly.one
♾️ #AutisticActually 🇵🇭 #Philippines
✨ Appeared: «Sports Seoul»; «The Daily Report» Arirang
©️ #CCBYSA4
Main: @youronly.one
🖼️ @gallery.youronly.one
🕹️ 🏁 @gameshogun.is.youronly.one
Feeds: @feeds.at.youronly.one
🐲 #UDIC Yarso Dragon
🐉 #GuildWars2
#️⃣ #fedi22
✨ Appeared: «Sports Seoul»; «The Daily Report» Arirang
©️ #CCBYSA4
Main: @youronly.one
🖼️ @gallery.youronly.one
🕹️ 🏁 @gameshogun.is.youronly.one
Feeds: @feeds.at.youronly.one
🐲 #UDIC Yarso Dragon
🐉 #GuildWars2
#️⃣ #fedi22
Pinned
Mabuhay! 마부하이! ᜋᜊᜓᜑᜌ᜔᜶
♾️ This pinned thread is where I post important information. 👇🏽
♾️ This pinned thread is where I post important information. 👇🏽
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
I put together a little validator for checking verification and lexicon conformance for @standard.site implementations. Let me know if it says something daft and I'll fix it: site-validator.fly.dev
Standard.site Validator
site-validator.fly.dev
January 9, 2026 at 4:07 AM
I put together a little validator for checking verification and lexicon conformance for @standard.site implementations. Let me know if it says something daft and I'll fix it: site-validator.fly.dev
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
The ecosystem aligning on shared lexicons is important to fully realizing this vision too. Happy to see that fairly well happening so far.
@standard.site, for example. Also @popfeed.social using the same lexicons as @bookhive.buzz
Love to see it
@standard.site, for example. Also @popfeed.social using the same lexicons as @bookhive.buzz
Love to see it
I vibe with the general sentiment, but I’d rather say it’s a post-everything-app protocol.
The new paradigm, the Atmosphere, is a bunch of domain-specific apps built on an everything-protocol.
The new paradigm, the Atmosphere, is a bunch of domain-specific apps built on an everything-protocol.
ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.
January 9, 2026 at 5:32 PM
The ecosystem aligning on shared lexicons is important to fully realizing this vision too. Happy to see that fairly well happening so far.
@standard.site, for example. Also @popfeed.social using the same lexicons as @bookhive.buzz
Love to see it
@standard.site, for example. Also @popfeed.social using the same lexicons as @bookhive.buzz
Love to see it
👇🏽 This!
- Article footers, sometimes you may want to create a shared footer within your articles, you will be able to set it once, and update it everywhere easily. No editing multiple articles to change a word or link.
January 10, 2026 at 7:18 AM
👇🏽 This!
I don't know react native but it's react native. 😆
January 5, 2026 at 6:22 PM
I don't know react native but it's react native. 😆
- CORE: Create Once, Release Everywhere
- PORES: Post Once, Release Everywhere Simultaneously
- PORES: Post Once, Release Everywhere Simultaneously
January 5, 2026 at 5:42 PM
- CORE: Create Once, Release Everywhere
- PORES: Post Once, Release Everywhere Simultaneously
- PORES: Post Once, Release Everywhere Simultaneously
Yep. I hope Greengale will support viewing content found via site.standard lexicon, and maybe even add GG unique features so when someone views the blog or posts from GG, it's showing the way authors want it (like themes, which I think is one of GG's strength, each post can have a separate theme).
January 5, 2026 at 4:58 PM
Yep. I hope Greengale will support viewing content found via site.standard lexicon, and maybe even add GG unique features so when someone views the blog or posts from GG, it's showing the way authors want it (like themes, which I think is one of GG's strength, each post can have a separate theme).
I haven't seen one yet. However, @greengale.app list the latest content seen via the site.standard. lexicon and redirects it to the actual URL.
January 5, 2026 at 4:49 PM
I haven't seen one yet. However, @greengale.app list the latest content seen via the site.standard. lexicon and redirects it to the actual URL.
It's going to be very interesting. For one, if they do that, they'll be the first publishing service connected to both ATmosphere and Fediverse networks. It could translate to widest reach, too.
January 5, 2026 at 1:06 PM
It's going to be very interesting. For one, if they do that, they'll be the first publishing service connected to both ATmosphere and Fediverse networks. It could translate to widest reach, too.
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
Interoperability update: you can now select "Enable standard.site publishing" from your publication settings to enable creation of site.standard records whenever you create a GreenGale post.
Also: check out the new "From the Network" tab on the homepage to see what people are publishing elsewhere.
Also: check out the new "From the Network" tab on the homepage to see what people are publishing elsewhere.
January 5, 2026 at 12:28 PM
Interoperability update: you can now select "Enable standard.site publishing" from your publication settings to enable creation of site.standard records whenever you create a GreenGale post.
Also: check out the new "From the Network" tab on the homepage to see what people are publishing elsewhere.
Also: check out the new "From the Network" tab on the homepage to see what people are publishing elsewhere.
Hmm… if you want to try the community, try setting up @atprotofans.com and share the link. Who knows, you might have enough to cover the domain for a year or two.
Just a thought. (I might go that route myself 6 months from now, I'm drying out.)
Just a thought. (I might go that route myself 6 months from now, I'm drying out.)
January 5, 2026 at 12:55 PM
Hmm… if you want to try the community, try setting up @atprotofans.com and share the link. Who knows, you might have enough to cover the domain for a year or two.
Just a thought. (I might go that route myself 6 months from now, I'm drying out.)
Just a thought. (I might go that route myself 6 months from now, I'm drying out.)
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
If you’re interested in integration with Bluesky, I recommend any of these - you just look w the same account you use on Bluesky (which is really an ATmosphere account):
leaflet.pub
pipup.social
pckt.blog (beta, @brookie.blog)
greengale.app (beta)
offprint.app (Soon^TM)
weaver.sh (Soon^TM I think)
leaflet.pub
pipup.social
pckt.blog (beta, @brookie.blog)
greengale.app (beta)
offprint.app (Soon^TM)
weaver.sh (Soon^TM I think)
December 29, 2025 at 5:31 AM
If you’re interested in integration with Bluesky, I recommend any of these - you just look w the same account you use on Bluesky (which is really an ATmosphere account):
leaflet.pub
pipup.social
pckt.blog (beta, @brookie.blog)
greengale.app (beta)
offprint.app (Soon^TM)
weaver.sh (Soon^TM I think)
leaflet.pub
pipup.social
pckt.blog (beta, @brookie.blog)
greengale.app (beta)
offprint.app (Soon^TM)
weaver.sh (Soon^TM I think)
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
Made a tiny app - goals.garden - Track your new year goals and habits on atproto!
New Year, New Goals
Introducing goals.garden - Goal and habit tracking on ATProto
sri.leaflet.pub
January 2, 2026 at 4:55 AM
Made a tiny app - goals.garden - Track your new year goals and habits on atproto!
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
ATmosphere / ATproto Importers list
Lists/Collections via:
- kipclip: kipclip.com/share/did:pl...
- Monomarks: monomarks.at/t/importers
- Semble: semble.so/profile/your...
Lists/Collections via:
- kipclip: kipclip.com/share/did:pl...
- Monomarks: monomarks.at/t/importers
- Semble: semble.so/profile/your...
Importers (by JC John Sese Cuneta 사요한 謝雪矢 🦋) — Semble
Tools, scripts, services, that can import data into your ATmosphere account.
semble.so
January 2, 2026 at 12:10 AM
ATmosphere / ATproto Importers list
Lists/Collections via:
- kipclip: kipclip.com/share/did:pl...
- Monomarks: monomarks.at/t/importers
- Semble: semble.so/profile/your...
Lists/Collections via:
- kipclip: kipclip.com/share/did:pl...
- Monomarks: monomarks.at/t/importers
- Semble: semble.so/profile/your...
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
We've been busy working on an atproto docs suite, with keynotes in PitchDeck and spreadsheets in DataGrid.
After today's @standard.site document lexicon announcement, we’re adding Publisher for creating articles and publications.
Here's a workspace with Publisher, DataGrid, and PitchDeck open.
After today's @standard.site document lexicon announcement, we’re adding Publisher for creating articles and publications.
Here's a workspace with Publisher, DataGrid, and PitchDeck open.
January 2, 2026 at 6:06 AM
We've been busy working on an atproto docs suite, with keynotes in PitchDeck and spreadsheets in DataGrid.
After today's @standard.site document lexicon announcement, we’re adding Publisher for creating articles and publications.
Here's a workspace with Publisher, DataGrid, and PitchDeck open.
After today's @standard.site document lexicon announcement, we’re adding Publisher for creating articles and publications.
Here's a workspace with Publisher, DataGrid, and PitchDeck open.
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
Exactly, thats the goal. We wanted to define the bare minimum for publications and documents, then let platforms add features that fit their needs. Thats why we don't define a content structure at all, since in most cases it will be dependent on the platform.
January 2, 2026 at 2:05 AM
Exactly, thats the goal. We wanted to define the bare minimum for publications and documents, then let platforms add features that fit their needs. Thats why we don't define a content structure at all, since in most cases it will be dependent on the platform.
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
The standard.site lexicons define whats necessary for content to move across social boundaries.
It doesn't define things like complex themes, or content formats, but since lexicons are extensible, each developer can add those themselves.
We think we struck a pretty good balance.
It doesn't define things like complex themes, or content formats, but since lexicons are extensible, each developer can add those themselves.
We think we struck a pretty good balance.
January 2, 2026 at 12:51 AM
The standard.site lexicons define whats necessary for content to move across social boundaries.
It doesn't define things like complex themes, or content formats, but since lexicons are extensible, each developer can add those themselves.
We think we struck a pretty good balance.
It doesn't define things like complex themes, or content formats, but since lexicons are extensible, each developer can add those themselves.
We think we struck a pretty good balance.
- The lexicon is schema.org
- The data is provided by the user
- The services use the lexicon and decide how to present the existing data (like a frontend with its own extra features)
We avoid duplication, too. 🖖🏽
- The data is provided by the user
- The services use the lexicon and decide how to present the existing data (like a frontend with its own extra features)
We avoid duplication, too. 🖖🏽
January 2, 2026 at 1:43 AM
- The lexicon is schema.org
- The data is provided by the user
- The services use the lexicon and decide how to present the existing data (like a frontend with its own extra features)
We avoid duplication, too. 🖖🏽
- The data is provided by the user
- The services use the lexicon and decide how to present the existing data (like a frontend with its own extra features)
We avoid duplication, too. 🖖🏽
… and so on.
Everything else like themes, blocks, fonts, extra features, are per platform.
Think MusicBrainz and TMDB. They provide the data, anyone can use it and present it in any way they want, and add features only they have.
Everything else like themes, blocks, fonts, extra features, are per platform.
Think MusicBrainz and TMDB. They provide the data, anyone can use it and present it in any way they want, and add features only they have.
January 2, 2026 at 1:43 AM
… and so on.
Everything else like themes, blocks, fonts, extra features, are per platform.
Think MusicBrainz and TMDB. They provide the data, anyone can use it and present it in any way they want, and add features only they have.
Everything else like themes, blocks, fonts, extra features, are per platform.
Think MusicBrainz and TMDB. They provide the data, anyone can use it and present it in any way they want, and add features only they have.
This! What I've been trying to explain.
For everything data, standard lexicon. Likes, emoji reactions, title, subtitle, categories, tags, authors (for multi-authoring), Canonical URL (for search engine bot use to avoid getting penalised), publish datetime (UTC), last edited datetime (UTC), …
For everything data, standard lexicon. Likes, emoji reactions, title, subtitle, categories, tags, authors (for multi-authoring), Canonical URL (for search engine bot use to avoid getting penalised), publish datetime (UTC), last edited datetime (UTC), …
January 2, 2026 at 1:43 AM
This! What I've been trying to explain.
For everything data, standard lexicon. Likes, emoji reactions, title, subtitle, categories, tags, authors (for multi-authoring), Canonical URL (for search engine bot use to avoid getting penalised), publish datetime (UTC), last edited datetime (UTC), …
For everything data, standard lexicon. Likes, emoji reactions, title, subtitle, categories, tags, authors (for multi-authoring), Canonical URL (for search engine bot use to avoid getting penalised), publish datetime (UTC), last edited datetime (UTC), …
Reposted by Yohan Yukiya Sese Cuneta 사요한 🦋
Hello atmosphere ! Over the last few weeks, a bunch of us have been collaborating on a new set of lexicons for publishing, indexing, and building out social features across long-form reading and writing apps ! 🧵1/7
Standard.site - One schema. Every platform.
Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
standard.site
January 2, 2026 at 12:51 AM
Hello atmosphere ! Over the last few weeks, a bunch of us have been collaborating on a new set of lexicons for publishing, indexing, and building out social features across long-form reading and writing apps ! 🧵1/7
Goodbye 2025! Hello 2026!
#HappyNewYear to everyone in the ACT ( #ASEAN Common Time ) timezone and the rest of UTC+8!
#NewYear #NewYear2026 #HappyNewYear2026 #Philippines
#HappyNewYear to everyone in the ACT ( #ASEAN Common Time ) timezone and the rest of UTC+8!
#NewYear #NewYear2026 #HappyNewYear2026 #Philippines
December 31, 2025 at 4:00 PM
Goodbye 2025! Hello 2026!
#HappyNewYear to everyone in the ACT ( #ASEAN Common Time ) timezone and the rest of UTC+8!
#NewYear #NewYear2026 #HappyNewYear2026 #Philippines
#HappyNewYear to everyone in the ACT ( #ASEAN Common Time ) timezone and the rest of UTC+8!
#NewYear #NewYear2026 #HappyNewYear2026 #Philippines
2025年さようなら！ こんにちは! 2026！
韓国の皆さん、明けましておめでとうございます！
~ フィリピンから🫰🏽
韓国の皆さん、明けましておめでとうございます！
~ フィリピンから🫰🏽
December 31, 2025 at 3:02 PM
2025年さようなら！ こんにちは! 2026！
韓国の皆さん、明けましておめでとうございます！
~ フィリピンから🫰🏽
韓国の皆さん、明けましておめでとうございます！
~ フィリピンから🫰🏽
안녕 2025! 안녕 2026!
한국에 계신 모든 분들께 새해 복 많이 받으세요!
~ 필리핀에서 🫰🏽
한국에 계신 모든 분들께 새해 복 많이 받으세요!
~ 필리핀에서 🫰🏽
December 31, 2025 at 3:01 PM
안녕 2025! 안녕 2026!
한국에 계신 모든 분들께 새해 복 많이 받으세요!
~ 필리핀에서 🫰🏽
한국에 계신 모든 분들께 새해 복 많이 받으세요!
~ 필리핀에서 🫰🏽
You can use this: blue.mackuba.eu/scanner/
Label Scanner
blue.mackuba.eu
December 30, 2025 at 9:04 AM
You can use this: blue.mackuba.eu/scanner/
Same thoughts! I want to see the now defunct Foodspotting service/idea but in ATproto. So much data was lost when they closed shop years ago. I was using it to track the food I'm eating because gout. 😅
December 28, 2025 at 1:02 AM
Same thoughts! I want to see the now defunct Foodspotting service/idea but in ATproto. So much data was lost when they closed shop years ago. I was using it to track the food I'm eating because gout. 😅