|
|
|
|
|
|
by hyperpape
2915 days ago
|
|
|
> and also addressed in the article towards the end. Your perception might be that they're addressed, because you see your vision of how things should work. But to me, I can't see more than "trust me, I'm working on it". The value of that assurance depends on how well you see the limitations of the older workflows, not just their advantages. If you build it, that will assuage most worries, but talking about what you need in addition to the pure email workflow, and showing how it can be built would also help your case. |
|
|
https://sr.ht
There's more tangible stuff here than "trust me, I'm working on it", I hope. A lot of the non-mail-related work exists and I'm getting started on mail stuff now, so I'm starting to write about it to spurn discussion and start paying attention to people's concerns with the approach.
You can also see some of the specific email-related stuff I have going if you want to dig some more:
https://git.sr.ht/~sircmpwn/lists.sr.ht/
https://git.sr.ht/~emersion/python-emailthreads/
The latter in particular could give some good insight into how this stuff is going to take shape. Would love to hear more of your concerns, keep them coming!