3 ms·
> "Users shouldn't have needed to know the name." How would they communicate with each other about it then? These things don't expand in a vacuum. Perhaps not
by chiefalchemist 8y ago
> "Users shouldn't have needed to know the name."
How would they communicate with each other about it then? These things don't expand in a vacuum. Perhaps not in a modern social media sense, but there is always a network effect.
Calling it RSS was too plain and too clinical.
- taeric 8y agoThis is the elephant in the room here. With google reader, they actually had a good integration with google buzz so that I could have a small social circle around some posts. I could put a comment on an RSS item and my friends and I could have a conversation on it. Then, they killed it hoping to get everyone discussing things in a plus feed. Something I have no interest in. Especially because I can't really see the discussions in my email. Which is ultimately what is killing things here. Many of us built up real workflows for correspondence using email. It works great for that. Instead of trying to help build on these correspondence workflows, companies would rather find ways of owning that correspondence, such that now I have to use Facebook or Google Plus or whatever in order to have basic back and forths with friends/family/strangers.
- chiefalchemist 8y agoAgreed. That said the typical email UI could easily become an RSS reader. - Sender = publisher / source - Subject = title + author - Body = body The same can be said for SMS. Shifting the email client to a one-stop comms dashboard would make a lot of sense (to me). Add in drag & drop to a TODO list(s) and I'm more effective and happier.