You would think the very idea of years of your work being rendered unplayable in an instant would be enough incentive to signal boost any effort against this industry practice.
Instead, developer discourse has revolved around just how hard it would be to do what this is petition is asking for. You are an engineer for crying out loud. If you solved a problem but a new constraint arrives in the form of a law, you figure out how to solve the problem under the new constraint. Just because something is hard, doesn't mean it's not worth doing.
It's almost like flexing your skills and signalling your elite knowledge is more important to people than simply defending what's right.
https://rsshub.app/twitter/user/{username} for twitter accounts
Append .rss to any subreddit URL you want updates on
YouTube also has an RSS feed for channels
This has been one of the key programs for me to move 90% of my "timeline" into an rss reader.
If you self-host it, you can also pass it authentication tokens to RSSify things like:
- your twitter timeline
- github notifications, issues, commits
- discord messages
- youtube subscriptions
- spotify/twitch/steam/etc.
Why not push/pop warnings to ignore in the library?
_Pragma("GCC diagnostic push")
_Pragma("GCC diagnostic ignored \"-Wshadow\"")
int a = 1;
{
int a = 2;
}
_Pragma("GCC diagnostic pop")
The best way in many languages for flags is using unsigned integers that are botwise-ORed together.
In pseudocode:
Whatever language you are using, it probably has some namespaced way to define flags as `(1 << 0)` and `(1 << 1)` etc.