the history and group syncing is complete garbage right now. it has a level of inconsistency i would absolutely not expect from an alleged ‘production-ready’ sdk. the v3 sdk is not production ready, yet we’re being forced to migrate.
so guys, if you’re gonna put out a preset brownout schedule, at least have the common decency to stick with it ffs
Hey @sycore, appreciate the feedback. Can you share more about the issues you’re seeing with history, group syncing, and the brownout schedule? I’d love to chat live to make sure we fully understand where your experience went sideways. Here is my scheduling link: Notion Calendar
Thanks,
Saul
@sycore I agree with you, the SDK is useless, i think they should start working on V4 instead, cause V3 is just broken.
Streams don’t work as expected, and don’t get me started on the behaviour if you open in multiple tabs.
the history syncing is inconsistent; you never know whether it’s going to actually work or not. i get the reason for the switch to MLS, but right now i have zero confidence in our dapp being able to work as seamlessly as it does now across platforms.
it’s also pretty terrible that group messages don’t sync across installations. esp considering that you can’t have multiple DMs with different ‘topics’ with a single recipient like in v2. (i’m less confident in this one so correct me if i’m wrong)
i’ve had to spend days debugging mismatched ‘epoch’ errors for message syncing. finally after enough digging, i gave up and just revoked and cleared out all installation data, specifically OPFS. it appears to be working but i’m not feeling great about it.
the brownout schedule seems to have gotten thrown out the window (thankfully) because i can’t imagine anyone on the dev team thinks it appropriate considering the state of v3.
everything just feels super fragile and yet v2 is allegedly set for full deprecation in 2 weeks.
or, idk, maybe just keep v2 and expand upon it since it’s been rock solid for several years now? it feels like v3 wasn’t really an upgrade and more of a “let’s build a shiny new thing using these other shiny things” type of thing.
@saul no comments?
Hey @sycore @Saqlain_Riaz – thanks for following up.
V2 was really nice and simple to work with. Unfortunately, it was the wrong foundation for 1) decentralizing XMTP and 2) delivering things devs were asking us for, like
The last on that list came with a big trade-off. Maintain instant sync message history, or protect past and future messages from compromise.
We chose the latter. You can read more about that trade-off and how it affects history sync here.
I’m disappointed you’ve run into issues. V3 needs to be a rock solid foundation for devs. Streams can’t be flaky. Installations can’t just get into weird states. History sync should be easy to implement. Everything should work exactly as documented. Only once we’re batting 100% do we have the privilege to decentralize.
And, you should be able to get help from our team when you need it. If there is anything we can do to unblock you, please let us know.
Appreciate your direct feedback. It makes us better.
i do appreciate the responses. it’s nice to see people actually paying attention.
my main “blocker” is the sync inconsistency across groups and dms (ie history syncing). because our users use our dapp across multiple devices over the course of a single session, having history syncing be seamless across installations is of paramount importance.
considering our conversation, this thread, and the current state of v3, is v2 still slated for full deprecation in a week?
@saul any insights on the question above re: deprecation?
@saul ?
homeboy must’ve gotten fired cuz that calendar link is ded now
Hey @sycore, saw Nick shared the updated timeline in your other thread.
Sorry for the expired link. Grab any time here: cal.com/saul