In this release, the coding focus has been on moving to PHP 8.1+ and refactoring the integration of the SimplePie library (which was long due). At the same time, plenty of new features have been added. Enjoy! 🎄
Breaking changes 💥:
Require PHP 8.1+ (and improved support of PHP 8.4+)
Require PostgreSQL 10+ or MariaDB 10.0.5+ or MySQL 8+
⚠️ Advanced regex syntax for searches depends on the database used (SQLite, PostgreSQL, MariaDB, MySQL),
but FreshRSS filter actions such as auto-mark-as-read and auto-favourite always use PHP PCRE2 syntax.
Allow dynamic search operator in user queries, like search:UserQueryA date:P1d
New feed mode HTML+XPath+JSON dot notation (JSON in HTML)
Better HTTP compliance with support for HTTP response headers Cache-Control: max-age and Expires
New unicity policies and heuristic for feeds with bad article IDs (reduce the problem of duplicated articles)
New option to automatically mark new articles as read if an identical title already exists in the same category
Add ability to remove content from articles with CSS selectors, also when not using full content
New condition option to selectively retrieve full content of articles
New UI feature to download a user’ SQLite database or a database SQLite export (to be produced by CLI)
⚠️ Advanced regex syntax for searches depends on the database used (SQLite, PostgreSQL, MariaDB, MySQL),
but FreshRSS filter actions such as auto-mark-as-read and auto-favourite always use PHP PCRE2 syntax.
Allow dynamic search operator in user queries, like search:UserQueryA date:P1d#6851
New feed mode HTML+XPath+JSON dot notation (JSON in HTML) #6888
Better HTTP compliance with support for HTTP response headers Cache-Control: max-age and Expires#6812, FreshRSS/simplepie#26
Support custom HTTP request headers per feed (e.g. for Authorization) #6820
New unicity policies and heuristic for feeds with bad article IDs #4487, #6900
ChatGPT impressed millions of internet users when it was first launched in December 2022. To Filipino Elmer Peramo, though, it felt familiar. After typing in some prompts and seeing the...
Dec 19, 05:03 UTC Resolved - From 1:23 UTC to 3:04 UTC, users may have experienced issues with events being stuck or delayed, such as powering on/off, and resizing Droplets in the NYC3, AMS2, BLR1, SGP1, and SYD1 regions. Additionally, Managed Database creates were delayed in all regions.
Our Engineering team has confirmed full resolution of the issue, delayed events and new events should complete as normal now.
Thank you for your patience through this issue. If you continue to experience any issues, please open a support ticket from within your account.
Dec 19, 04:28 UTC Update - Our Engineering team has confirmed that new events are succeeding, and we're finalizing cleaning up any stalled events. We will post an update as soon this issue is fully resolved.
Dec 19, 03:08 UTC Monitoring - Events in NYC3 has been enabled now and users may continue to submit new events. We are starting to see success rates with event processing go up.
We will post another update soon. Thank you for your patience.
Dec 19, 02:42 UTC Update - Our Engineering team continues to work to mitigate the issue with event processing in multiple regions.
To help address the issue, we are temporarily disabling all Droplet-related actions in the NYC3 region for a period of 20 minutes. During this time, users in NYC3 will not be able to submit actions, such as creating, resizing, powering on/off, etc.
We apologize for the inconvenience and appreciate your patience as we work to resolve this issue. Further updates will be shared as they become available.
Dec 19, 01:45 UTC Investigating - Our Engineering team is investigating an issue impacting Droplet event processing in multiple regions.
At this time, users may experience issues with events appearing to be stuck or delayed, such as powering on/off, and resizing Droplets in NYC3, AMS2, BLR1, SGP1, and SYD1 regions. Additionally, Managed Database creates are delayed in all regions.
We apologize for the inconvenience and will share an update once we have more information.
The social media feed of Indonesian singer and content creator Vicky Shu generally features her clothes, makeup, and family. But when she decided to run for the regional elections in...
The day mass transit startup Swvl announced its decision to downsize operations in Pakistan in June 2022, its country general manager Maha Shahzad fully grasped the dire circumstances that female...
Dec 13, 13:25 UTC Resolved - From 13:25 to 14:45 UTC, our Engineering team observed a Networking issue in our NYC3 region. During this time, users may have experienced Droplet and VPC connectivity issue, Users should no longer be experiencing these issues. We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.
Dec 13, 11:01 UTC Resolved - Our Engineering team has confirmed that the issues with Spaces CDN functionality has been fully resolved. Users should now be able to use CDN functionality normally.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Dec 13, 10:55 UTC Monitoring - Our Engineering team has implemented a fix to resolve the CDN functionality issue and is currently monitoring the situation.
We will continue to monitor this at our end and will share an update once the issue is resolved completely.
Dec 13, 09:55 UTC Investigating - Our Engineering team is investigating an issue affecting Spaces CDN functionality globally. During this time, users may experience issues when enabling Spaces CDN and with existing CDN services.
We apologize for the inconvenience and will share an update once we have more information.
When Alois Kachere decided to order a Starlink kit after the company’s launch in Zimbabwe in September, he hoped to be the first person in his neighborhood to get the...
Dec 13, 04:05 UTC Resolved - Our Engineering team has confirmed the full resolution of the issue impacting Managed Database Operations, and all systems are now operating normally. Users may safely resume operations, including upgrades, resizes, forking, and ad-hoc maintenance patches.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Dec 13, 03:13 UTC Monitoring - Our Engineering team has implemented a fix for the issue impacting Managed Database Operations. The team is monitoring the situation, and we will share an update once this is fully resolved.
Dec 12, 22:03 UTC Update - Our Engineering team is continuing to work on investigating the root cause of the issue affecting Managed Database Operations. At this time, we are seeing improvement and some new cluster creations are completing successfully.
To avoid potential downtime, we continue to ask users to refrain from performing operations that trigger node rotations, such as upgrades, resizes, forking, and ad-hoc maintenance patches.
We apologize for any inconvenience caused and appreciate your patience. We will post further updates as soon we have more information.
Dec 12, 19:35 UTC Update - During our investigation, we identified that operations triggering node rotation, such as upgrades, resizes, forking and ad-hoc maintenance patches, may cause issues connecting to the cluster.
To prevent potential downtime, we recommend avoiding these operations until the issue is fully resolved.
We apologize for the inconvenience and appreciate your patience as we work to address the situation.
Dec 12, 18:34 UTC Investigating - Our Engineering team is investigating an issue with the Managed Database clusters which is causing forks, restores and new creates to fail. The Mongo clusters are unaffected and should be operating normally.
Our team is currently assessing the root cause and working to resolve the issue as quickly as possible.
We apologize for any inconvenience this may cause and will share an update as soon as we have more information.
Dec 13, 01:24 UTC Resolved - Our Engineering team has confirmed that the issues with Authoritative DNS resolution in NYC1 has been fully resolved. DNS queries should now be resolving normally.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Dec 13, 01:10 UTC Monitoring - Our Engineering team has implemented a fix to resolve the issues with Authoritative DNS Resolution in NYC1 and is currently monitoring the situation.
We will continue to monitor this at our end and will share an update once the issue is resolved completely.
Dec 12, 23:20 UTC Investigating - Our Engineering team is investigating an issue with intermittent failures and increased latency in DNS resolution in NYC1.
During this time, a subset of users may experience issues with DNS resolution, or see errors returned when querying DNS records which are hosted on the DigitalOcean authoritative DNS infrastructure.
We apologize for the inconvenience and will share an update once we have more information.
Malaysian digital artist Kitty Misa, like many other creators in the country, had long used the ArtStation site to showcase her work. Since the site was blocked by the government...
Last fall, school administrators at the University of Yucatán asked Abraham Slim, a 23-year-old medical student, to fill out a survey on his smartphone. The questions on the survey did...
Dec 11, 23:33 UTC Resolved - Our Engineering team has resolved the issue impacting prohibiting a subset of users from logging in, and the login flow is now operating normally.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Dec 11, 22:53 UTC Monitoring - Our Engineering team has implemented a fix for the issue prohibiting a subset of users from logging in. The team is monitoring the situation, and we will share an update once this is fully resolved.
Dec 11, 19:33 UTC Investigating - Our Engineering team is currently investigating an issue prohibiting users from logging in if they are flagged for an additional security challenge.
We are actively reviewing the root cause and working closely to resolve the issue as quickly as possible.
We apologize for the inconvenience and will provide updates as more information becomes available. Thank you for your patience.
Login
