Merged!

I must admit that I haven’t had time to work on it due to my lifestage changes and it won’t improve soon (probably the opposite would be the case).
I don’t mind you forking the project as you said in another mention.

うげ先月のAWSコストなんか5倍になってんな…

@tanzpunk.bsky.social Thank you for reporting!
It was indeed an issue of WhiteWind and was fixed.

バグも直せずすみません🙇
世にいる個人開発者、マジでどう時間工面してんだろ

プライベート立て込みすぎで何も更新できてないですが生きてます

Tech Talk: Building Long Form Blogging with WhiteWind YouTube video by AT Protocol Development

But that's not all! Act now, and you too can watch the great talk we hosted last year with @knksm5.final-techblog.com fantastic presentation about @whtwnd.com, the #atproto long form Markdown blogging Lexicon + app.

Tech Talk: Building Long Form Blogging with WhiteWind A Tech Talk about Long form blogging with WhiteWind, with developer K-NKSM. A third party app view and lexicon defining Markdown blogging for AT Protocol.

Thank you very much for @knksm5.final-techblog.com for presenting to us early morning JST, and for the #atproto Japanese developer community for joining in.

Thank you to @chadkoh.com for Japanese communications support.

Links to the slide deck and everything else about @whtwnd.com on the blog.

WhiteWind atproto techtalk - Google スライド WhiteWind Special tech talk AT Protocol Development

Here's the slide link!
docs.google.com/presentation/d/1lvQnJotX...

トーク中のコメントといつも使っていただきありがとうございます😊
バグは調査しておきます～

Thank you very much, Boris!
It was a great opportunity for me to talk with atproto enthusiast like you and Nick!

あんま人が来すぎるとプレッシャーになるので当日よりも録画の方を宣伝することにした

後1時間ちょいではじまるで~！

1 more hour until launch 🚀 🚀 🚀

Tech Talk: Building Long Form Blogging with WhiteWind A Tech Talk about Long form blogging with WhiteWind, with developer K-NKSM. A third party app view and lexicon defining Markdown blogging for AT Protocol.

This Friday, we're hosting our last Tech Talk of the year, with the first custom Lexicon #atproto app: Long form blogging with @whtwnd.com

Thank you to WhiteWind developer @knksm5.final-techblog.com for joining us!

フロントエンドのレベルが高いな

I'm doing it, consider this the soft-launch of bookhive.buzz

Review, rate, manage your books. Based on AT Protocol which powers bsky!
OSS: github.com/nperez0111/b...
Consider this very beta, but I wanted to ship something that is usable now.
My profile: bookhive.buzz/profile/nick...

Comment below!

山貂さんのモデレーションのやつを読んでいる

Last Week in the ATmosphere – 2412.a Bluesky is cementing it's position for news, conversations on verification, book reviews with Skylights, and much more.

Last Week in Bluesky and the ATmosphere

This week's news:
- continued calls verification on bluesky
- more ai datasets with bluesky posts appear
- book reviews on ATProto with Skylights
- Lexicon.community for devs to collaborate on lexicons

and a ton of links

fediversereport.com/last-week-in...

Hi, thank you for heavily using WhiteWInd!
I added scroll bar to the uploaded pics page.
Does it work for you?

Sure!

Hybrid blog post and announcement! I liked WhiteWind but wanted to have it my way, so I made a frontend for it! Check out a demo of WhiteBreeze (and the blog post itself!) here:
blog.hugeblank.dev/3lcgcrdoo3s2a

Hi, I am the dev of WhiteWind.
You can reach the login page but the password is rejected, right?
Could you use main password of Bluesky, not application password?

This is talking about the reaction number counting shown in entry card.
All the bsky mentions and replies are rendered in the reaction section as before.

Updated WhiteWind so that it doesn't include bsky replies.
It also no longer double-checks the actual existence of the records so some number inconsistency might occur.
e.g. someone posts something while WhiteWind relay consumer is down

修正しました！
お手数ですが確認いただいてもよろしいでしょうか？

報告ありがとうございます！
調査します！

自分以外の人も記事かけてるみたいだしとりあえず目立った問題はなさそう

なんかだーいたいoauth動くようになってきたな
そろそろ本番にデプロイしてみるか？

It's ready(ish), review books on ATProto!
Here are mine, show me yours: skylights.my/profile/watw...

Interestingly, I checked your PDS but your blog data seems to have been deleted.
I do remember I could see your blogpost when I replied you.
Just to confirm, did you delete the entry somehow by yourself?