In the old Google, it would have been easier for anyone to just fix this internally.
(Disclaimer: work at Google but not on anything related to this; all my information comes from links in this HN thread. Which is ironic / symptom of the same problem.)
[1]: https://front-end.social/@bramus/111448166340277056 and https://github.com/bramus/web-dev-rss / https://github.com/bramus/chrome-for-developers-rss
[2]: https://chrome-for-developers-rss.bramus.workers.dev/blog
[3]: https://issuetracker.google.com/issues/314910854#comment2
This is actually ironic in light of popular HN sentiment in Google-related articles, where many seem to imagine Google acting as a single whole, rather than different teams working in their own interests and not thinking of the big picture. E.g. people in this thread imagining that "Google" thought about RSS support and made a decision based on advertising revenue (or whatever imaginative reason), when in fact the team working on the "DevSite" infrastructure probably barely thought about RSS at all. Maybe they should have, but the reality that RSS (unfortunately) doesn't matter much seems harder to swallow for many, than theories about maliciously breaking it.
And the culture changed at the same time. Lots of seemingly needless rules to protect rising fiefdoms that started the sclerosis that only got worse over time. Gamergate internally felt like a Civil War waged over Google+.
Google+ itself was the height of Google’s hubris, thinking they could kill a beloved product (Google Reader) to kill a different company’s beloved (at the time) product, Facebook. I remember being deeply disappointed with the release of Google+ like I was when the Segway was released. All this hype and promise for a secret product built with an enormous group of highly-talented people, kept away from the teeming masses of similarly talented people that could’ve told them that it was a dumb idea and here are the reasons why.
Really, if I had to blame one thing, it would be Google+ because of the corrosive effects of social media. Before Google+, my colleagues were just my colleagues who brought their whole selves to the office but we still mostly talked about work. Folks had mailing lists I wasn’t subscribed to where they would talk about their abhorrent political beliefs so I wouldn’t find out about them.
And then, all of a sudden, after Google+ came out, some guy I thought was cool revealed that he didn’t want women to be able have abortions. And some other guy was a randroid, hellbent on not understanding that taxes pay for roads. And on and on…seemingly everyone just spent a lot of time being mad at each other.
Obviously it’s hard for me to point to a specific thing or time period, but the writing was on the wall in the early 2010s (to me, anyways) and I bounced by the middle of the decade.
I know they still dabble in search but that’s not the point.
http://googlepress.blogspot.com/2000/10/google-launches-self...
We moved our site to a different infrastructure that doesn't support the automatic generation of RSS feeds.
I'm painfully aware that this isn't the best solution right now. I needed our team to hit a deadline for migrating all the content to the new system, and then manage cleanup of known missing functionality after.
We are working on making sure this lands asap.
Paul
I had been wondering why https://developer.chrome.com/feeds suddenly died.
> I needed our team to hit a deadline
Why?
The majority of corporate deadlines are fictional in the sense that there is not a regulatory or legislative component to them, so it's easy to hand-wave them away and say that $THING should be a higher priority than the deadline. But that doesn't make them any less real for the people who have that deadline imposed by their boss (or more realistically, their boss's boss's boss's boss).
There is a freeze to the new infrastructure's product features until after the new year and we needed to get this in before then (we can land feed support without a product feature change)
The people I have working on the older infrastructure will be on new projects for our team in the new year.
I'm leaning toward giving the benefit of the doubt in this case, but why be oblique like this? Why not say "We are working on adding RSS" or "we are aiming to restore RSS support"?
> RSS is alive https://paul.kinlan.me/index.xml
* Google Reader is often cited as the best RSS Reader but was killed, which reduced amount of users (I never used it, thus can't judge it)
* Many publishers want people to go to their site, thus don't provide full feeds, only headlines and limit it in additional ways.
* People went to Twitter and Facebook as their news aggregators, depending on the social graph to preselect "relevant" news.
Aside I think the pure list of entries only works to a limited degree for news sites: in RSS all articles are equal, but for news many people want to see the "main" news highlighted as on a news page. For some of my feeds on some news days the feed is barely usable when they push a main story combined with different detail articles, making it hard to find the main story (for instance on election day there is a main article for summary and then bunch of articles for different districts, different parties, ... which appear equal while they aren't equal, also the article with first results is already outdated and replaced ...)
1. Google Reader was not necessarily the best reader. The anger and frustration with the handling of Google Reader lies in the fact that Google Reader was the first reader from a major tech company. That essentially killed all the other innovation in this space and then Google Reader was itself killed in such a short span that there wasn’t an opportunity to have a smooth transition for the entire industry with it.
2. The one spade that did see a lot of competition growth and innovation were off-web RSS clients (precisely because Google Reader wasn’t a player in this space). But even these were completely handicapped by the elimination of Google Reader because Google Reader has become the de facto syncing solution for your RSS list and read states, etc. Again, the short time between announcement and end of life meant many of the popular clients couldn’t find a smooth transition for their users.
3. Google Reader had a social network effect component where someone could publish RSS articles they were reading and others could subscribe to their feed. In this sense it almost acted as an alternative to Twitter. The Twitter implosion has shown exactly how hard it is for alternatives to a social network to arise (because you invariably get many alternatives and it’s hard to get everyone onto one).
And the RSS reader social network space was nascent so the fragmentation as a result of the destruction of Google Reader meant a lot of people migrated to Twitter instead (Google had hoped they would migrate to Google+ instead but Google+ was awful so that didn’t happen).
No FTP, RSS, etc.
For me it shows an alert asking if I want to subscribe in my installed feed reader.
Opera (my main browser back then) use to have so much stuff built in (RSS, email, IRC, note taking, mouse gestures). Chrome use to have a resizable extension bar recently. OneNote use to have a more colorful and compact UI. Start menu and taskbar used to be useful before windows 11/10/8.
Reminds of an article posted here about removing less used keys/letters from keyboard. https://www.marginalia.nu/log/48-i-have-no-capslock/
So not saying Vivaldi's RSS is bad, mostly want to mention that Thunderbird can do RSS too, if one happens to use it anyway.
Less distributed/democratized machine/automation friendly... But definitely automation friendly for giant search scrapers, with lots of compute, cash, IP blocks and AI.
I'd like to change that. I originally created BrowserBox^0 as a platform to serve "web scraping authoring tools". These tools are normally served as extensions, or even downloadable electron apps. But what about something easier to distribute, more powerful, more lightweight, and less beholden to walled-garden gatekeeping? BrowserBox changes all that, as it's clientless and runs in a regular web browser even on mobile. Anyone can build a scraping script on top of it, even from your mobile device while riding the bus. That's the vision anyway. But I got side-tracked by how the "embeddable browser" is a useful product in its own right. I still intend to return to fulfilling its original purpose however.
The key is to build a good "extensions-like"-but better-API atop the Chrome DevTools protocol and our BrowserBox functionality. We're open source so come visit if you'd liked to get involved or check it out! :)
> GAM is a command line tool for Google Workspace admins to manage domain and user settings quickly and easily.
I need this about once per year, but every time it's invaluable.
There is, but somehow, rather than being a workspace API, it's a GCP api ; and so if you want to use it, there is a big step to climb.
Perhaps I should interview at Google and teach them my amazing solution.
> Unfortunately, we don't have official RSS feed support for now, but we're actively working on a solution.
Well, that certainly means they are going to have RSS feeds in the future. Right?
RSS could be that solution!
Did Google develop a new internal blogging platform and just didn't get around to supporting RSS?
https://mastodon.social/@bramus@front-end.social/11144816695...
Yeah exactly, what kind of bs is that
The last article pushed to the feed was "Changes to the web.dev infrastructure" few months ago https://web.dev/blog/webdev-migration
The feed still there but with no updates https://web.dev/feed.xml and on the site you can see new articles published.
Is sad that on a infrastructure revamp of a modern site, the RSS feed was left out of the features list (at least for now).
https://mastodon.social/@bramus@front-end.social/11144816695...
I'm still angry at Google for killing Reader. It was the best way to consume content on the web.
RSS is a menace to Google's bottom line!
I never used Reader so I'm not genuinely curious, what about it makes it difficult for someone to just create a copy of the service?
That’s the best solution if you’re on Apple.
TheOldReader.com is also very good (UI is very heavily Google Reader inspired).
I’m happy, it lead to an explosion of available readers, including many self-hosted ones.
I understand RSS completely and the goals, but honestly? I don't find it useful at all. I'm always surprised how many people on HN claim to still use it.
Internet users can't have nice things.
curl -sA "" https://developer.chrome.com/blog/sitemap.xml \
|sed -n '
1i\
<?xml version="1.0" encoding="UTF-8" ?>\
<rss version="2.0">\
<channel>
s}\(<loc>\)\(.*\)\(</loc>\)}\
<item>\
<title>\2</title>\
<description>\2</description>\
<link>\2</link>\
</item>}p;
$a\
</channel>\
</rss>
'
If this isn't correct RSS, please forgive me. I'm not an "engineer". I prefer a personalised, simple HTML made from URLs as opposed to XML. I write filters to generate this in C.NB. The public sitemap.xml still refers to an (unofficial?) RSS feed.
Please, Expose Your RSS
For now this can be used: https://chrome-for-developers-rss.bramus.workers.dev/blog or /articles or /case-studies
Also, I note the wording of the error message, that they're actively working on it.
Loss of the ability to contribute via GitHub pull request is unfortunate, hopefully there will be a better way to contribute again in the future.
- commercial AI refusing to generate RSS XMLs from a webpages' content. - "illegal" AI that is willing to browse webpages without disclosing that their'e bots
As I can no longer watch yt without getting annoyed, looks like it's time to get a new email provider (as well) .
@ yahoo seem to have few(er?) problems.
There are probably others. Can anyone recommend a good search engine?
uBlock Origin + EFF Privacy Badger should take care of it. I've never seen any ads on YouTube (except the ones the stream includes inherently).
In a cohesive organization they would improve Blogger to fulfill their needs, but instead they just waste resources recreating a one-off solution over and over again.
please donate: https://patreon.com/leafac
- https://changedetection.io/#features
- https://github.com/dgtlmoon/changedetection.io
> Create RSS feeds based on changes in web content
Now, what's Google's goal to monetize social networks? They have non as far as I know. They lost all opportunities in the social space and they lost their lead in RSS. The Web lost too.
that’s the world Google wants. Money sloshing around the system and them getting a cut each time.
Sometimes I think the jokes about Google having no management are true.
Google management too busy doing evil
Cue some "googler" show up defending this move and how it makes the world better.
But they historically had several feed systems [1] [2] which were fully under their control.
> Cue some "googler" show up defending this move and how it makes the world better.
Of course. 'We have a better system that uses 2FA to securely text you every ten minutes to generate a code that, in combination with a 16 character unicode password, allows you to check whether Google approved content has been updated.'
I don't think Google's fear is who's in control of any one particular RSS. I think Google's fear is what if people realize that, for the purposes of subscribing to updates from a source, RSS is objectively better than Google. They're afraid of losing the mindshare of being the unquestionably better option for everything.
(Ok, you and I are probably not the most "mainstream" people in the world, but what I mean is these ideas aren't understood exclusively by antitrust lawyers anymore)
Companies are catching up too though. Google coaches its employees on what language to use internally.
"Surely my user base will continue coming to the landing page of my website to check for updates every day."
So they have some stupid conversation like “patching the rss code will take 5 units of labor, but I want to cyberdize the whoozit that also takes 5 units. Does anyone even care about rss and use it? Oh the analytics show zero. Let’s de prioritize that.”
I think the bigger problem is people on the team not using rss and knowing this is super dumb. And PMs now knowing the world their metrics don’t track.
Seems to kind with google once being great and now full of fat rich peoples’ kids just riding the slow and gradual suck. (Based on the theory that smart people have weak, pampered kids; then weak kids get destroyed by jerk fascists; then jerk fascists get overturned by smart people and the cycle completes).
Of course the dumb kids think they are geniuses because their parents are part. And the parents want to pretend their kids are smart. Etc etc
Facebook did that with emails - slowly remove all the content to turn them into traffic generators for the feed team.
Hilariously when they launched workplace, the corporate productive product, they did the same thing, viciously spamming you with emails that have the first 15 characters of the workplace post that triggered them (and 2 more for the notification and every comment).
zero respect for your time, everything must drive traffic.
In the real world, the options aren't just an RSS feed vs. "load the page daily". Readers also come from search engines, social media, link aggregators and non-RSS news feeds.
If it was the latter, it's almost certainly a cynical drive to get more 'page impressions' by making people visit the actual website to read the blog posts.
Feel free to get in touch with me if you need help or have questions.
[0]: https://monitoro.co
AdSense, for example, is super hard to fit into RSS. How do you do it?
Sorry, we tried everything but the user agent support for Javascript in RSS is simply lacking. Unfortunately, it has to be dropped, there is no alternative.