11–20 of 104 posts
I'm increasingly disinclined to feed the subscription-based software economy, especially for the personal tools I use.
Over all, I like how it looks, but the price seems high. $3 a month is almost as much as I pay for email service. Plus it seems weird to double drip. I’m already subscribed to you for the email service and you want me to almost double that price for a client to use it? Will the existing Fastmail app be deprecated to force folks to the new subscription app?
this isn't a first-party app for Fastmail, at least afaict. I had the same initial reaction before realizing this. (I still have the same reaction to the pricing... but at least it's not double dipping by Fastmail themselves)
This looks good, but I'm not clear why it's a subscription. I'm happy to pay for upgrades when a new version with new features is offered; and I'm happy to not pay if the new version isn't compelling enough. (Sometimes support for major OS upgrades is enough of a feature.) I'm increasingly disinclined to feed the subscription-based software economy, especially for the personal tools I use.
Great work! Will def. try it out
I like the look of it but I don't know what JMAP is and what the advantage is over say IMAP / SMTP.
The UI looks almost identical to https://mimestream.com/
I like the look of it but I don't know what JMAP is and what the advantage is over say IMAP / SMTP.
It's a reworked email protocol, created by fastmail. Basically email over json (send + receive) instead of imap+smtp. https://jmap.io/
Edit: I've got 99 problems and 98 of them are JSON on a regular basis. Poor parsers, problems dealing with numeric values, terrible terrible schema support, poor encapsulation support, large things attached to it in base64 (difficult to stream on most parsers), difficult to read without external tools which actually tend to mung or fix the problem you are trying to see (jq does this), completely arbitrary and random metadata jammed in everywhere by everyone trying to make it self-describing, shitty enapsulated types i.e. ISO 8601 date in a text field rather than a principal type.
Urgh kill me. It's a hammer made of poo and no one knows any better any more. It's the PHP of wire formats. The COBOL of representation encapsulation.
Edit 2: the only positive is it's probably less bad than CalDAV but that's not even supposed to be part of an email stack is it? Everyone has outlook brain.
Earlier quoted context omitted.
It's a reworked email protocol, created by fastmail. Basically email over json (send + receive) instead of imap+smtp. https://jmap.io/
Got it. Fuck that. JSON has no part in an email stack. Have we not learned from our failures as a species. Edit: I've got 99 problems and 98 of them are JSON on a regular basis. Poor parsers, problems dealing with numeric values, terrible terrible schema support, poor encapsulation support, large things attached to it in base64 (difficult to stream on most parsers), difficult to read without external tools which actu…
It's a great achievement of our species.