Thanks for the help, #GoogleReader. Before retirement, let's read 2 more, for old time's sake.

TiK Tok. Just a reminder that Book 1 in the Glass Ceiling Club series is just 99 cents on Amazon through Friday. @bookblog @by_murtaza @booktok_app @_RaeRadford @BookReviews03 @BookBoostNow @googlereader @BookChat_ @cozymysteryclub @CozyMystery_com

❓Are You Using the Right Sales Commission Fee? #GoogleAlerts #AI #GoogleAI #GoogleReader #RealEstate #SanDiegoCA

Our blog at @Censys now has a proper RSS feed censys.com/feed/ (cc: @Feedly #GoogleReader)

I put RSS feeds from dozens of news outlets in @googlereader. JK. They retired it. I use @Inoreader.

We’re overthinking AI chat history — just like Chrome did with web history. 20 years ago, Chrome indexed every page users visited and designed detailed UIs for them to explore it. But users didn’t care. They just searched again. Here's what AI tools can learn from this 👇 Chrome’s web history dataset was rich, personal, and full of possibility. Designers explored everything from subway-map visualizations, to timeline UIs, to GoogleReader-style feeds — imagining people would want to explore their own browsing history. When they realized it was just easier, faster, and more intuitive for users to search again, Chrome shifted course. Web history became infrastructure — powering suggestions, surfacing shortcuts, and tucked behind “Command Y.” Today, AI teams are replaying this same debate and trying to “solve” chat history. But people don’t want to manage their chat history. They just want models to remember intelligently so that every conversation feels smoother, smarter, and more personal. History should live in the background, supercharging personalization, context, and recall across the core product. The best designed products weave history in when it makes sense, but focus on propelling users forward. Full post in comments.

自分にとってはGoogleReader終わったとき「おいまじかこれ切るんか」というのがあったのでパスワード管理はChrome任せにするの抵抗あって、生成させてなかったんだけど、最近はなし崩し的にお任せになってきてしまっている…それより一番やばいのはGmailで、過去23年分の集積があそこにしかない…

pocketも終了か。まぁGoogleReaderの時で凝りたから、自鯖のwallbagに移行してたんで問題ないけど🐷 RSSリーダーもFreshRSS自鯖に立ててるし、やっぱ無料サービス系のでなくなると困るやつは自鯖に限る（有料サービスでもええんだけど有料でもなくなるときはなくなるからな） itmedia.co.jp/news/articles/…

I still haven't forgiven Google for killing googlereader

Googleの継続性の件 昔は「別に、他のメーカーもサービス終了ぐらいあるだろ」と思ってたが 【ある程度ユーザー数が居たにも関わらず】 ・GoogleReader ・Google という二大裏切りがあり、そこから信用しなくなった

Shipping RSS support today. It's still a thing! anyone want to build AI-powered @googlereader? 😀

Given Google's loooooooooooooooong history of killing off products (even successful and beloved products like @GoogleReader), that announcement is more encouraging than the "we're shooting it in the head, it's gone, suck it up" I would have expected. killedbygoogle.com/

certainly at some point in my life i really keep that time in my heart and it meant more to me then enjoying ever has, certain YouTube videos with less than 100 views that I'll never forget or days spent on early googlereader watching music videos in awe never to my room mate

ついにGooglePodcastの終了通知が来た 以前同じようにGoogleReaderが終わった時はInoreaderに移行することになった 一応YoutubeMusicにデータ移行はしておいたけど、より良いところがないか探すことにしよう

個人的には、Google とGoogleReaderで Googleはすぐ辞めるイメージの決定打になったわ x.com/sesere115/status/17470…

Need to check out what @alex_norcliffe is building! Era.app

Intuit shutting down @mint is another @googlereader shutdown moment. Not many good alternatives, many people love it but the company failed to monetize it? Good product case studies and I'd be interested to read experts' opinion.

The next step towards getting rid of visual junk around me and resisting temptation to scroll more and more. YouTube subscriptions will also go there soon. The feed was exported as an OPML from Feedly and is running locally now. Haven't figured out how to integrate a smartphone into this, but probably it's even better as I want to cut down my smartphone use anyways. My use of RSS: GoogleReader -> local Reeder on Ipad/iPhone -> Feedly -> local Newsboat.