DracoBlue

Passionated IT Consultant for DevOps, APIs, Javascript, Java, PHP & HTML/CSS. All opinions expressed here are my own.

[DracoBlue @DracoBlue]

My next day in the #notai written blog series about building https://t.co/mg18xQc6ox is about expo OTA challenges, wrong strict types and char limit harmonization. Thanks for reading.
https://t.co/mweZGPvdgh

#buildinpublic #postalgorithm

[DracoBlue @DracoBlue]

My next day in the #notai written blog series about building https://t.co/mg18xQc6ox is about failing happy path implementation (oembed and refresh mode)! Thanks for reading.

https://t.co/cT7UcofSft

#buildinpublic

[DracoBlue @DracoBlue]

@rauchg Making public entity Information available (in germany) as rss feeds and icals https://t.co/EDTzXhDgtj

Built with sonnet 4.6

[Mario Zechner @badlogicgames]

me: do it
gpt: totally did it
me: dude
gpt: totally did it now
me: wtf
gpt: i so did it, you won't believe how hard i did it

gpt 5.5, thinking off.

[DracoBlue @DracoBlue]

My next day in the #notai written blog series about building https://t.co/mg18xQc6ox is about adding #mastodon (activitypub or #fediverse) and the free audio tab! Thanks for reading.

https://t.co/hvL7PATsma

#buildinpublic

[DracoBlue @DracoBlue]

My next day in the #notai written blog series about building https://t.co/mg18xQc6ox is today about Youtube Error 153, duplicate videos (reposts!) and an empty video feed because of caching. Thanks for reading.

https://t.co/UrPFX9lJQr

#buildinpublic #atproto #fediverse

[AI SDK @aisdk]

AI SDK 7 canary has a new telemetry system.

Register telemetry once, then all AI SDK calls emit telemetry by default.

[Mira Murati @miramurati]

Today we're sharing our work on interaction models. A new class of model trained from scratch to handle real-time interaction natively, instead of gluing it onto a turn-based one.
https://t.co/MoS5s4cm60

[DracoBlue @DracoBlue]

My next day in the #notai written blog series about building https://t.co/mg18xQc6ox is today about a consent for third party content and how I use oEmbed to discover if content is available before embedding the webview.

https://t.co/1K08PpU5XS #buildinpublic #privacymatters

[Mario Zechner @badlogicgames]

recommended reading. i too am concerned about what agents mean for genuine learning. i think what tobi propsoses here is one piece of the puzzle.

[DracoBlue @DracoBlue]

My second day in the #notai written blog series about building kiesel app is today about resolving custom PDS in atproto, introducing darkmode and pretending likes are stored before they are. Thanks for reading.

https://t.co/hf9wYlyJDo #buildinpublic #atproto

[DracoBlue @DracoBlue]

Während ich heute gearbeitet hab, hat mein Claude Code Assistant mal recherchiert, welche Quellen für Veranstaltungen und Meldungen aus den Kommunen in Deutschland (initiale ein Landkreis aus Brandenburg) es gibt. Der aktuelle Stand #buildinpublic https://t.co/EDTzXhDgtj

[Mitchell Hashimoto @mitchellh]

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. https://t.co/DQDemHdytV

[DracoBlue @DracoBlue]

@xlcizor @steipete @useblacksmith This. :)

[Mario Zechner @badlogicgames]

i'm sort of addicted to working my butt off, always have been. in oss, that can consume you. constant feeling of urgency, as issues stream into the repo. been there many, many times with my other oss.

but that urgency is not real. if something is truely broken, a large number of people will scream at you on all channels. which has happened exactly zero times so far, or was caught minutes after a botched release and immediately fixed.

it's kind of crazy that some people expect better support from an oss project than from commercial software. i think that's largely due to most commercial software corps not giving a fuck. try filing an issue with corporate and getting it fixed within 24h or less plus a personal response.

and as oss builders don't have a corporate facade shielding them from direct contact with users, some sort of bidirectional parasocial relationship establishes itself. at a certain scale, that becomes entirely unhealthy.

for every 10 kind and thoughtful people, there is 1 asshole. and whatever the asshole says or feels entitled to, sticks with you much more than positive feedback.

obv. also happens in corpo environments, especially if you do comms or dev rel, where you put your face and name out there.

but a corp that can afford dev rel usually also has a large team in the back, which can soften the negative aspects.

in oss, you are largely on your own. and unpaid. that too is a choice of course, and nobody is forcing anyone to do oss.

but if you want oss to work, consider that there are other people at the end of that issue tracker/social media account, with lives and squishy human parts. also consider that you are paying nothing for their service, and you are owed exactly nothing, neither code nor attention to your every wish.

[DracoBlue @DracoBlue]

Today atproto-push-gateway is released as v1.2.0 with several security hardenings. Thanks a lot to ave. for giving it a try and contributing! #BuildInPublic https://t.co/wVgSjWnVrx

[DracoBlue @DracoBlue]

I started my (non-ai-written) blog on "building https://t.co/mg18xQc6ox" on #offprint. let's see how this works and goes. Thanks for reading!

https://t.co/ghkTlrE011

[DracoBlue @DracoBlue]

I have been building my first opensource atproto project to make app.bsky.notifications.registerPush possible with your own push service. Find the first release at https://t.co/zJ4zyhgJpY - looking forward to your feedback. #BuildInPublic

[Guillermo Rauch @rauchg]

Next.js 16.2 is an agent-native framework.

𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 + bundled docs make your agent an expert in the exact version of Next.js you’re using.

@𝚟𝚎𝚛𝚌𝚎𝚕/𝚗𝚎𝚡𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛 gets your agent a purpose-built tool to debug & optimize your frontend.

We proved these in production at Vercel. Agents shipped optimizations that expert frontend engineers missed or struggled to write manually.

The thing I’m most excited about is that agents will be able to harness the full power of the newer advanced React and Next.js capabilities that were conceived for humans to have the best possible end-user experience.

[Pedro @sillydarket]

https://t.co/epmvq8bsBQ