oursqlcommunity-org / planet

Planet for the MySQL Community
13 stars 15 forks source link

Better filtering when no content:encoded. #130

Open jfg956 opened 5 days ago

jfg956 commented 5 days ago

Less and less feeds include content:encoded, they only include a description.

An example is Percona, and because Percona is an important MySQL player, this have their dedicated issues:

Tracing other examples in this issue...

Eventually, it would be good to be able to filter on both title and description (and maybe more), but current filtering (https://siftrss.com/) only allow filtering on one or the other.

jfg956 commented 5 days ago

Example:

Extract:

<item>
<title>Migrating in-place from PostgreSQL to MySQL</title>
<description>The Yelp Reservations service (yelp_res) is the service that powers reservations on Yelp. It was acquired along with Seatme in 2013, and is a Django service and webapp. It powers the reservation backend and logic for Yelp Guest Manager, our iPad app for restaurants, and handles diner and partner flows that create reservations. Along with that, it serves a web UI and backend API for our Yelp Reservations app, which has been superseded by Yelp Guest Manager but is still used by many of our restaurant customers. This service was built using a DB-centric architecture, and uses a “DB sync”...</description>
<pubDate>Mon, 07 Oct 2024 00:00:00 +0000</pubDate>
<link>https://engineeringblog.yelp.com/2024/10/migrating-from-postgres-to-mysql.html</link>
<guid isPermaLink="true">https://engineeringblog.yelp.com/2024/10/migrating-from-postgres-to-mysql.html</guid>
<dc:creator> Alex Toumazis, Software Engineer </dc:creator>
<previewImage>http://engineeringblog.yelp.com/images/previews/2024-09-27-postgresmysql.jpg</previewImage>
<authorImage>http://engineeringblog.yelp.com/images/authors/alext.png</authorImage>
</item>