Dinos Theodorou
@dinostheo.bsky.social
The machines took over. I'm the assistant now.
#ClaudeCode
#ClaudeCode
February 9, 2026 at 5:45 PM
The machines took over. I'm the assistant now.
#ClaudeCode
#ClaudeCode
Part 5️⃣: Duplicate comments (aka how we shot ourselves in the foot 😅)
We almost nailed the data model for Buffer’s Community.
Then we broke it and started creating duplicate comments in some edge cases 🫠
⬇️
We almost nailed the data model for Buffer’s Community.
Then we broke it and started creating duplicate comments in some edge cases 🫠
⬇️
January 24, 2026 at 3:15 PM
Part 5️⃣: Duplicate comments (aka how we shot ourselves in the foot 😅)
We almost nailed the data model for Buffer’s Community.
Then we broke it and started creating duplicate comments in some edge cases 🫠
⬇️
We almost nailed the data model for Buffer’s Community.
Then we broke it and started creating duplicate comments in some edge cases 🫠
⬇️
Part 4️⃣ : Comments trees
Have you ever had one of these engineering role interviews where you have to build a tree? Something you most probably never have to do in your role?
At @buffer.com, we don’t ask those type of questions. Yet, the irony is that we had to build one for Community 😅
Have you ever had one of these engineering role interviews where you have to build a tree? Something you most probably never have to do in your role?
At @buffer.com, we don’t ask those type of questions. Yet, the irony is that we had to build one for Community 😅
January 9, 2026 at 1:45 PM
Part 4️⃣ : Comments trees
Have you ever had one of these engineering role interviews where you have to build a tree? Something you most probably never have to do in your role?
At @buffer.com, we don’t ask those type of questions. Yet, the irony is that we had to build one for Community 😅
Have you ever had one of these engineering role interviews where you have to build a tree? Something you most probably never have to do in your role?
At @buffer.com, we don’t ask those type of questions. Yet, the irony is that we had to build one for Community 😅
Part 3️⃣: How we designed our ingestion pipelines (and why)
Our ingestion design is intentionally dead simple 😅
At its core, it’s a classic producer → consumer pattern, with a few variations depending on how data is produced.
Our ingestion design is intentionally dead simple 😅
At its core, it’s a classic producer → consumer pattern, with a few variations depending on how data is produced.
December 29, 2025 at 1:33 AM
Part 3️⃣: How we designed our ingestion pipelines (and why)
Our ingestion design is intentionally dead simple 😅
At its core, it’s a classic producer → consumer pattern, with a few variations depending on how data is produced.
Our ingestion design is intentionally dead simple 😅
At its core, it’s a classic producer → consumer pattern, with a few variations depending on how data is produced.
Part 2: When real-time integrations went down just after launch
The first week after launching Community at @buffer.com, we experienced 2 major outages with our real-time integrations.
Both were outside our control, but still high impact for a newly launched feature.
The first week after launching Community at @buffer.com, we experienced 2 major outages with our real-time integrations.
Both were outside our control, but still high impact for a newly launched feature.
December 22, 2025 at 12:32 PM
Part 2: When real-time integrations went down just after launch
The first week after launching Community at @buffer.com, we experienced 2 major outages with our real-time integrations.
Both were outside our control, but still high impact for a newly launched feature.
The first week after launching Community at @buffer.com, we experienced 2 major outages with our real-time integrations.
Both were outside our control, but still high impact for a newly launched feature.
Part 1: How we switched ON Community across 6 networks and 8 API integrations
On the 12th of November we launched Community at @buffer.com
We launched across
• Threads
• Instagram, 2 different APIs
• Facebook
• LinkedIn, 2 different delivery mechanisms
• Bluesky
• X
On the 12th of November we launched Community at @buffer.com
We launched across
• Threads
• Instagram, 2 different APIs
• LinkedIn, 2 different delivery mechanisms
• Bluesky
• X
December 16, 2025 at 8:23 AM
Part 1: How we switched ON Community across 6 networks and 8 API integrations
On the 12th of November we launched Community at @buffer.com
We launched across
• Threads
• Instagram, 2 different APIs
• Facebook
• LinkedIn, 2 different delivery mechanisms
• Bluesky
• X
On the 12th of November we launched Community at @buffer.com
We launched across
• Threads
• Instagram, 2 different APIs
• LinkedIn, 2 different delivery mechanisms
• Bluesky
• X
Now that the dust has settled from @buffer.com Community launch, I’m starting a mini-series on the engineering work behind the data ingestion and processing pipelines.
It’s more of a journal than a guide. Sharing what we built, why we chose certain paths, and what surprised us 😅
It’s more of a journal than a guide. Sharing what we built, why we chose certain paths, and what surprised us 😅
December 10, 2025 at 7:00 PM
Now that the dust has settled from @buffer.com Community launch, I’m starting a mini-series on the engineering work behind the data ingestion and processing pipelines.
It’s more of a journal than a guide. Sharing what we built, why we chose certain paths, and what surprised us 😅
It’s more of a journal than a guide. Sharing what we built, why we chose certain paths, and what surprised us 😅
We've been going through some photos from when we first moved into our house and stumbled upon my home office setup from 2018. It took me about ~1.5 year to paint the room, lay the floor and buy a desk. And still I prefer coding from the couch, sitting in some weird position. 😅
November 27, 2025 at 10:28 PM
We've been going through some photos from when we first moved into our house and stumbled upon my home office setup from 2018. It took me about ~1.5 year to paint the room, lay the floor and buy a desk. And still I prefer coding from the couch, sitting in some weird position. 😅
need to test some more
November 17, 2025 at 9:14 AM
need to test some more
Big day for our team at @buffer.com!
We have just launched Community, a calm and focused way to manage your comments across Threads, LinkedIn, Instagram, X and right here on Bluesky.
It’s live now and available on every plan, even Free. 💬
We have just launched Community, a calm and focused way to manage your comments across Threads, LinkedIn, Instagram, X and right here on Bluesky.
It’s live now and available on every plan, even Free. 💬
November 12, 2025 at 4:36 PM
Big day for our team at @buffer.com!
We have just launched Community, a calm and focused way to manage your comments across Threads, LinkedIn, Instagram, X and right here on Bluesky.
It’s live now and available on every plan, even Free. 💬
We have just launched Community, a calm and focused way to manage your comments across Threads, LinkedIn, Instagram, X and right here on Bluesky.
It’s live now and available on every plan, even Free. 💬
Trying a threaded post
November 12, 2025 at 10:24 AM
Trying a threaded post
Getting last things ready for today 🗒️
November 12, 2025 at 10:04 AM
Getting last things ready for today 🗒️
A calmer way to keep up with your community.
Does this make sense for Bluesky? Yes, it does 😄
November 12, with @buffer.com. Stay tuned! 💛
Does this make sense for Bluesky? Yes, it does 😄
November 12, with @buffer.com. Stay tuned! 💛
November 10, 2025 at 7:02 PM
A calmer way to keep up with your community.
Does this make sense for Bluesky? Yes, it does 😄
November 12, with @buffer.com. Stay tuned! 💛
Does this make sense for Bluesky? Yes, it does 😄
November 12, with @buffer.com. Stay tuned! 💛
I'm just going to drop a test post here 🧪
November 6, 2025 at 2:57 PM
I'm just going to drop a test post here 🧪
Way back I decided to list both my formal name and my calling name on LinkedIn.
Why?
Because outside of Greece, almost nobody knows that Dinos is just the short version of Konstantinos (in Greek, “NT” sounds like “D”).
Why?
Because outside of Greece, almost nobody knows that Dinos is just the short version of Konstantinos (in Greek, “NT” sounds like “D”).
October 14, 2025 at 8:15 PM
Way back I decided to list both my formal name and my calling name on LinkedIn.
Why?
Because outside of Greece, almost nobody knows that Dinos is just the short version of Konstantinos (in Greek, “NT” sounds like “D”).
Why?
Because outside of Greece, almost nobody knows that Dinos is just the short version of Konstantinos (in Greek, “NT” sounds like “D”).
Firehose powered Buffer 💪
September 30, 2025 at 2:24 PM
Firehose powered Buffer 💪
Firehose power ftw 🙌
September 30, 2025 at 9:39 AM
Firehose power ftw 🙌
Multiple images
September 28, 2025 at 8:28 PM
Multiple images
one with a GIF
a man in a suit and tie stands in a muddy field
Alt: a man in a suit and tie stands in a muddy field
media.tenor.com
September 28, 2025 at 8:22 PM
one with a GIF
Sorry for the noise 😔
[video post]
[video post]
September 28, 2025 at 8:19 PM
Sorry for the noise 😔
[video post]
[video post]
And one with an image
September 28, 2025 at 7:35 PM
And one with an image
Now it should be ready - plain text test
September 28, 2025 at 7:31 PM
Now it should be ready - plain text test
Yet another firehose test
September 24, 2025 at 3:26 PM
Yet another firehose test
Added some basic stats on my dev env, from the firehose events processed and filtered.
How meta is this, to post about the Firehose in order to test the Firehose? 😂
How meta is this, to post about the Firehose in order to test the Firehose? 😂
September 23, 2025 at 7:29 PM
Added some basic stats on my dev env, from the firehose events processed and filtered.
How meta is this, to post about the Firehose in order to test the Firehose? 😂
How meta is this, to post about the Firehose in order to test the Firehose? 😂
Hermes + Firehose FTW
September 23, 2025 at 6:40 PM
Hermes + Firehose FTW