In the setup you are describing the EV would only be used for long trips. EVs are just not great for that.
140 karma · joined December 5, 2019
In the setup you are describing the EV would only be used for long trips. EVs are just not great for that.
If you live in a European city, you should be using a car for commuting.
Something like: "blog posts which talk about using sending emails to yourself as a notes taking mechanism".
The output could look like: "note taking" OR "notes" ("emailing yourself" OR "email to myself" OR "email yourself") (inurl:blog OR inurl:posts OR site:medium.com OR site:substack.com)
https://lists.sr.ht/~machocam/public-inbox/%3C46e343ec-c932-...
The efficiency of the servers is also insane. The smallest VPS can handle over 10k users.
The clients are great (they have reactions!)
there is even a really good app store associated : https://webxdc.org/
RSS is just a protocol. You could make a reader now with any algorithm you want that displays feeds. In fact, I can’t imagine that no one is using the AI boom to say they will build a decentralized Twitter using rss plus ai for the algorithm
Is that the case? I find that super interesting. No sexy Slack or Teams type of thing?
- Donald Knuth
Start with a gsheet, when it breaks build something else.
> They used the tool that was available at that time. I am sure they use internal chat apps as well in today's environment.
Surprisingly, Google for example uses email + real time chat today. All communication of value, meaning thoughtful "actual" exchange of ideas happens over email. Chat is has auto disappear so it's not used for anything which remains on record, it's for small quick asks. There might be a googler in this thread who could give us more insight.
> Given that Slack has integrations with various tools (incident reporting, various bots, feed submissions, apps of all sorts), video/voice chats, file storage, rich messages, advanced notifications, and, most importantly, seamless communications with clients using it, it is just a tool that has replaced so many different tools.
I hear you on the integrations. There is no shortage of tools which plug into email too though. If the integration doesn't exist, it's typically trivial to set it up since email is just plain text.
> Not sure have you received any of the long quoted emails recently, I have, and it can be a nightmare (and ridiculous that an email client from a USD 3 trillion dollar company cannot render it properly).
For sure! and it sucks. That is why I promote email heavily for *internal* communications where the community itself enforces rules to keep the mailing list sane. That tends to happen organically in most open source mailing lists.
> Given that Slack has integrations with various tools (incident reporting, various bots, feed submissions, apps of all sorts), video/voice chats, file storage, rich messages, advanced notifications, and, most importantly, seamless communications with clients using it, it is just a tool that has replaced so many different tools.
There are few tools which are not integrated to email. But I hear you, if you like working in a monolith that makes sense. I like using the best tools for each piece. Best real time chat, best video chat platform, best asynchronous com, best file storage solution etc.
> This type of contribution is so incredibly both tone deaf and unempathetic, I wonder if you understand even how incredibly selfish the attitude is? Especially in using the word “just”.
I don't see how a comment which proposes a solution to the problem at hand can be "selfish".
I am the owner of a small business myself and am well aware of what switching tools requires. I'm also sorry that you think that modern tools like Slack or Mattermost for that matter improve communication over what email provides; then again that is obviously a matter of opinion.
> “Just” do this incredibly complex switch, which is utterly unsuitable to your users and how they work together, and which doesn’t actually solve your problem at hand since the article is about something else.
The article is about a simple yet painful problem. I am proposing a solution, I don't see how my comment is not pertinent. As for my use of the word "just", simple does not mean easy.
> Even with the absolute best reading of intentions I can give to your comment, I can only imagine you wrote it to make some microsubset of people still using mailing lists feel better about their choice and validated in one of the ever rarer advantages there are to using email as primary communication. > > Either that or you don’t actually know what Slack is. But then why comment?
False dichotomy. I truly believe that mailing lists are a great way to collaborate. Especially given the case that data ownership is now even more important to the author of the post.
Slack/Mattermost try to combine real-time chat with asynchronous information exchange. I think that that is not a great way to work, this is close enough to what I think of these solutions to [link to](https://basecamp.com/guides/group-chat-problems). Not only that but your data will always be locked away in their non-standard format.
Moreover, I emailed the author (good thing this "clunky" system exists), and offered help with a potential switch to using email. Thank you nonetheless for taking my comment into consideration. I can only hope it was more useful for other readers than it was for you.
Not to mention that basically every scientific breakthrough achieved since 1995 was achieved using email as the *only* form of communication (other than physical letters here and there).
All of our real discussions are sent to a mailing list with a web archive (like lkml.org, except private). That way we can still reference precise messages easily. It has been working great for us.
but in all seriousness, i do think that there is a lot of merit in the LKML way of doing things. otherwise all of our servers would be on fire now!
maybe and the insane capacity to sell things from the githubs, gitlabs of the world have brainwashed us!