Thank you, Google. You didn't have to, but you did. We (the Pebble team and community) are extraordinarily grateful.
I wrote a blog post about our plans to bring Pebble back, sustainably. https://ericmigi.com/blog/why-were-bringing-pebble-back
We got our original start on HN (https://news.ycombinator.com/item?id=3827868), it's a pleasure to be back.
> And as the time progressed, Pebble became the first platform to get Weathergraph - my graphical weather watchface.
> Weathergraph was then ported to Garmin (as Pebble shut down), and then to Apple Watch widget
Thanks for bringing Weathergraph to life. I found it on the Pebble and used it religiously until I experienced enough challenges with Rebble to switch to a Garmin watch. I was thoroughly chuffed when I saw that you had brought Weathergraph along with you.
Are you saying I'd have to get an Apple Watch to get the third-generation Weathergraph? ;-)
Indeed, I forgive Google about 40 of their killed projects for giving us pebble in return.
Forgiven, yes, but I still cannot trust them.
A decade of messing with my search results (they only cannot do that anymore since I switched to Kagi) and the killing of Google+ (still interested if anyone have alternatives. Despite its problematic start it became the only social network I ever enjoyed).
Google+ had amazing original content from a very creative community. Unfortunately the moderation of comments went downhill until Google abandoned the project. I am still a bit heartbroken.
not the reader though
It's strange to see the naivety around Reader.
If Facebook had created it, people would recognise the initiative to gate-keep, regulate and curate the Wild West of RSS. "They're trying to keep you inside their walled garden!"
Reader made tons of people use RSS who otherwise wouldn’t, and who now don’t.
It did not live long enough to become a villain (though it certainly would have — there is no reason why G wouldn’t have added recommendations, an algo feed, and all it brings). Therefore it’s remembered well.
Reader died because people were switching to social media.
Reader also had no vendor lock in at all. There’s no network effect like Facebook. There’s no massive infrastructure demands like Google. No corporate sales process like Oracle, Microsoft, etc.
You could very easily create a competitor and after it died, few even tried to replace it. I miss it but not enough to find another RSS reader.
You’re never really the villain if there are viable alternatives and next to no switching cost. It would have been hard to make that product evil.
> Reader died because people were switching to social media.
Which especially sucks, because its friend-of-a-friend model for making comments visible on shared items was better for discovering interesting people, constructively limiting the social impact of popular posts, reducing the dangers of unintentionally poor posts, and disincentivizing trolling than any social network has implemented since.
For the few people who even knew Reader had a social network—a group which certainly didn't include Google—it was a better social network than any of the ones credited with killing it.
I think it was just as much that the people who wrote blogs were switching to writing in the walled gardens of social media as it was the consumers. But yeah, I greatly prefer the days of blogs and RSS readers.
Now you have Substack and Medium and such, which are pretty decent.
The Fediverse is a bit like that. Anyone can post replies on things, but they don't spread through the whole network, only to people who are following the replier, and people on the replier's server, and the person who posted the thing being replied to.
It doesn’t seem to work quite like that. I don’t know the technical details, but I definitely see replies from people I don’t follow, from other instances, on posts of people I don’t follow on different (again) instances from mine and the replies.
Perhaps it could be that I’m seeing replies from people that others on my instance follow? Or perhaps there’s some other mechanism to fetch replies.
Probably that. Actually if your server receives the reply for any reason, it displays it, usually. There isn't a mechanism to fetch replies, so this is a kind of accidental filtering, while ATproto is the opposite and tries to make everything globally visible.
I use my own server with only me, so it only receives replies because I'm following the person who replied or their whole-server feed.
> Reader also had no vendor lock in at all. There’s no network effect like Facebook.
Reader had a massive social graph and strong network effects. There were social feeds that only existed in Reader and vanished when Reader shut down. I know I had friends that didn't blog but curated fascinating social feeds in Reader based on how widely they read. There were shared comments that only existed in Reader and entire discussions that happened in the margins of feeds that were lost.
Those social feeds were a discoverability joy. You'd find new feeds for yourself. You'd encourage friends to follow feeds you most recommended. None of the replacements have ever quite felt the same. (I love Newsblur, and it has versions of most of those social features, but it has never had the network effect, and probably never will.)
At one point too, the feeds in Reader included full histories up until the date someone first added the feed to Reader. You could scroll back through time "forever" on some feeds all the way to their first posts, sometimes posts that even the site itself had deleted since (and still read Reader-only comments on them). RSS feeds generally only provide the most recent dozen or so posts. Reader was tracking everything. That was a massive infrastructure demand in the Google scale that just about only Google could have done. None of the replacements try, and generally only keep about 45-90 days of feed activity.
Sure, it wasn't a completely walled garden, like Facebook, but it's still a case of Google killing the largest social network it had with the most beloved network effects for a marginal increase in vendor lock-in. They had good vendor lock-in that few could have competed with, and the replacements today are still scored on how much they can't compete with it, despite matching features.
Reader died because Google was switching to social media, not because people did.
> It would have been hard to make that product evil.
You can just treat RSS data as content to bring in new users, while building your lock through other means. Sharing, recommendations, algo feeds, commenting, and, eventually, posting. Then apply demands to RSS feeds, leveraging your audience, and lock out new ones.
This is all very easy and the playbook is well understood at this point.
This is just completely untrue.
It’s possible social media could have killed Reader.
But Reader died because Google killed anything that wasn’t directly contributing to Google+, and Reader was competition to Google+.
Also, I doubt Reader would have lost to social media. If Reader had stuck around it would most likely have been a Twitter alternative.
It was from a time where Google's ethos was still "Don't be evil" and generally speaking the naked greed triggered by AdSense hadn't infected the rest of the company yet.
So I think a lot of nostalgia is not just for the reader but also for the company Google used to be.
I wonder if in 20 years time there will be the next generation of programmers sneering over vapour-ware Google products while middle managers still buy them products because "no-one ever got fired for buying Google".
Because we miss what Reader was and not what it could have become.
As a more prolific blog writer at the time I also liked that their bot would include number of people who were subscribed to my blog in their User Agent.
> As a more prolific blog writer at the time I also liked that their bot would include number of people who were subscribed to my blog in their User Agent.
Something I generally appreciate with Google: The level of craftsmanship and the amount of elegant designs like this they come up with. (There are also… other things, but their standards are high compared to many competitors.)
These were different times, people hadn't burned themselves on Embrace, extend, and extinguish that much yet.
That’s not how I remember Reader at all.
I never used the web interface.
Google Reader provided syncing for nearly every 3rd party RSS app.
It wasn’t just a walled garden. It was also critical infrastructure for most RSS apps at the time.
Never forget.
not the reader indeed
What happens when they kill it again?
Open source licenses are irrevocable. You can quit providing the source, but you can't sue someone for using a copy they already took.
40 down, 400 to go.
> Weathergraph was then ported to Garmin (as Pebble shut down), and then to Apple Watch widget
I don't think I was a particularly early user of Weathergraph - but when I finally had to retire my Pebble Time I only considered platforms that had your watchface.
Thanks very much for the attention to detail!
Thank you!
I loved weathergraph. Was my favourite watch face on my pebble and garmin, until my eyes got too old and I couldn't read the smaller text anymore. Now I use a watch face for older guys like me, but miss the graph.
Thank you! I'm sorry - it's tricky to put in all the data, plus the Garmin app is now hard to maintain as it ran into a memory limit on older watches (they are very tight + a need to cache a large chart), and much of code simplicity has been sacrificed to make it run. I should probably try a re-do as newer watches and language features remove a lot of constraints.
Hi Tom, I just tried to donate on https://weathergraph.app/garmin, but was met with an error in your paypal integration. I've sent you a support email.
Thank you, replying!
Weathergraph is the best weather app I've ever used, thank you so much for it!
Thank you! I hope to keep it that way :).
There was a post here a couple weeks ago about smart phones with a very fancy reflective display and I immediately thought how good that would be on something like a pebble.