3 ms·
"offline-first system with mandatory redundant caching and no unattended cache flushing." Something like email "Ideally it should also intend clients to distri
by Out_of_Characte 6y ago
"offline-first system with mandatory redundant caching and no unattended cache flushing."
Something like email
"Ideally it should also intend clients to distribute seen messages between each-other."
Maybe a mailing list
"overquoting tradition"
Like I'm doing on this UTF-8 enabled page with compatible HTML. Yes, quoting can be redundant but on email it preserves sometimes valuable context in a redundant way.
Aren't you reinventing email exept its compatibility to every device on the world? Compatibility and availability are sometimes more usefull than the tax of legacy systems.
- qwerty456127 6y ago> Aren't you reinventing email exept its compatibility to every device on the world? No, in fact I'm just dreaming about the return of FidoNet, which already had none of these problems back in the 1990-ies ;-) Sure, there was no UTF-8 yet, but a standardized set of 8-bit ASCII codepages was already not bad though - you could always tell the codepage given the language/country and you didn't have to fit a symbol into 7 bits. And this is an illustration of FidoNet-style concise quoting: quote just an atomic idea, answer it, then quote the next one: > ... This way. Whoever needs to see the whole original message you are answering - it's up there in the thread tree, just a button away. And it is meant to be automatically pre-downloaded for you. Meanwhile, almost every single e-mail message I get just includes the whole thread quoted under its actual body (duplication level = insane). And it looks and works very weird when people actually need to respond to particular parts of my message paragraph-by-paragraph.