Sometimes being a developer with all kinds of keys lying around makes it a lot harder to keep track of which ones are important. 😅

The only reason mine got unread again was because of another spam attack.

Not forever broken, but you do have to contact support to get it fixed. 🙁

We really appreciate everybody who's been following along and who've been able to test it out and tell us what breaks for them!

We're super excited about what's around the corner for Roomy!

As soon as that's done, we'll be ready to explain exactly how everything works, and we'll start trying to get Roomy into serious real-world use.

Each of these represents a distinct feature needed in our new chat server implementation.

We have the design all spec'ed out, we've just got to finish it off, integrate it, and test it out before we finally have what we need to really start focusing on making the app solid and reliable.

We've held off on an explanation because there's still a few important things we need to get working first: partial loading, ephemeral events like typing notifications, and proper unread tracking.

Yeah, that's happened to me, too. I had to contact support last time to get it fixed. And then it just happened again.

I haven't bothered contacting support again and my notifications are forever unread...

Not yet. We do have partially functional unread markers, but not yet notification.

Yeah, exactly!

It was kind of a joke between me and my bros when I was like, "what does it mean if it feels like you know _less_ after I explain this?".

Then I realized, well, that actually is progress, though not the ideal ending point. 😄

This was a great talk, loved it!