Bramus, a google engineer did an inoffical workaround:
https://mastodon.social/@bramus@front-end.social/11144816695...
We don't have official RSS feed support for now, but we're working on a solution
111–120 of 253 posts
Re: We don't have official RSS feed support for now, but we're working on a solution
#112"Removed" implies it was there at some point; is this true? Or has this blog just never had RSS support? (I searched for this blog in Feedly and it didn't show up any older feed, but that may not be a reliable method for checking?)
Yes, it used to have RSS then they migrated to a new publishing platform that doesn't support RSS
For now this can be used: https://chrome-for-developers-rss.bramus.workers.dev/blog or /articles or /case-studies
Re: We don't have official RSS feed support for now, but we're working on a solution
#113Cue...
- 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
Re: We don't have official RSS feed support for now, but we're working on a solution
#114Earlier quoted context omitted.
You run a search engine and don't understand why defaults matter? Google pays billions to be the default. I don't understand what you don't understand. RSS was the default. Then it "died" (became non-default) and we got the Facebook feed and Twitter's toxic impression-pumping algorithms, and it's so much worse. Journalists depended on Reader the way they came to depend on Twitter. They didn't move to another reader.
RSS feeds are still very much around regardless of Google's actions. I'm looking at it from a user's perspective, not the operator's perspective, at what service is being offered? My question was why google reader was good, not why it was popular. As for my search engine, I genuinely don't track my users, so I really don't have the fainest how many users I have. 4 people or a million people use my search engine, and…
> My question was why google reader was good, not why it was popular.
Once you learn about Venn diagrams it's going to completely blow your mind. One easy first pass at making inferences as to best services is to use popularity as an imperfect first proxy. So if someone says that a service became a de facto standard used by all of the internet, it's one of the ways to helpfully frame the conversation about whether the service proved to be useful. Of course there will be exceptions, but it's one of those functional literacy things where everyone can understand the significance of why people would bring that up in the context of a conversation that ultimately was closing in on making assessments about the value of the user experience.
Google's RSS reader was simple, ad free, fast, had an elegant design, didn't attempt to push superfluous services or subscriptions, set a standard for accessible anywhere at a time when many popular RSS readers were used on the desktop, and, in contrast to most of the best services now around, was free. I would go so far as to say it was almost unimproveable because it had one job and it did it correctly and didn't try to do other things, which used to be one of the things Google did best.
And I feel like none of this information is new, hard to discover, controversial, but is instead part of the generally accepted canon of internet history. So it's a bizarre question to me, if I'm being honest.
Edit: regarding the prevalence of RSS adoption in the present day, it may be true that as a numeric total there are more sites using it, but that as a percentage it is down. The same way that a winning candidate for president from the 1940s will have fewer votes then a losing candidate from the present day. Numbers will grow over time just due to population growth. Or in the case of the internet, The growth in the number of sites. But to understand whether RSS enjoys the same status as a de facto standard it's necessary to look at more than just the numbers, but at the proportion of adoption today compared to the proportion as an existed in the past.
Re: We don't have official RSS feed support for now, but we're working on a solution
#115RSS requires a lot of developer resources to work with. 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.
> AdSense, for example, is super hard to fit into RSS. How do you do it?
You don't.
Re: We don't have official RSS feed support for now, but we're working on a solution
#116Re: We don't have official RSS feed support for now, but we're working on a solution
#117RSS requires a lot of developer resources to work with. 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.
[deleted]
Re: We don't have official RSS feed support for now, but we're working on a solution
#118When chrome started taking over, all other major browsers (probably even internet explorer) had native RSS read support (read at least). They use to show rss icon in the url bar or some other indictor that this site has RSS available. But Chrome ever since has been throwing raw xml at you when you try to open an rss feed link and never indicates if there is RSS here. I believe this to be the main reason for decline of RSS.
Re: We don't have official RSS feed support for now, but we're working on a solution
#119The web seems to be becoming paradoxically less and less machine/automation friendly. I recently had to modify 150+ accounts in a Google Workspace. Twenty years ago, I would be doing this in a Unix environment with a very simple shell script. Instead, I had to click-copy-paste-click, 20 times per page, like a monkey. I'm sure there must be some sort of API, but it would have taken 100 times the time it would have tak…
You can automate a lot of that stuff in the DevTools command-line, using basic DOM APIs. It's not ideal, but it allows you do to most of the things you'd do manually (click things, read text, write to textboxes) and it's easy to learn.
Re: We don't have official RSS feed support for now, but we're working on a solution
#120Earlier quoted context omitted.
Your general point definitely stands - there is a pretty nice third party solution for google workspace though: https://github.com/GAM-team/GAM
I doubt how many admins are comfortable with (or allowed to) using a non-approved third-party tool to manage their organization, despite open source and all that
The third party tool is based on the official google-api-python-client. It’s about as non-approved as ad hoc shell scripts.