Some general out of left field networking ideas

@Cthulhu-throwaway Given all the amazing improvements you've made to the networking code, I've been brainstorming some more ideas that could help the user experience on RetroArch that still have to do with networking code -

• Some way to 'scrape' Libretro articles or certain thumbnails from our website, along with some header text and short descriptions. The user interface code would have to be written by somebody other than you (i.e. me and others), but you'd have to figure out the details of how we'd fetch this data from the network in a mostly secure manner so that it can then be presented.

The aim here would be to make the menu more of a 'live' place, like the Nintendo Switch homescreen where certain 'news' items appear onscreen. This way, the project can share new developments about RetroArch and cores to the user from within RetroArch.

• Following up on that idea, if the user would click on any of these menu elements, we could then open an associated webbrowser taking them to the linked URL. Again, this code doesn't have to be written by you (the user interaction parts), as long as the networking code facilitates being able to fetch this kind of data.

This just serves as a RFC. By no means am I imploring you to drop whatever you are doing and focus on this, of course not. I'd very much prefer for you to continue working on the things that interest you. Just stating some general things of interest and ideas I had and just wanted to query where you stand on this.

This is a broad RFC for fetching Libretro articles or thumbnails, presenting them in the menu, and opening linked URLs; no files, tests, or entry points are named. Start by surveying RetroArch's existing networking code and menu integration, then establish a concrete scope and acceptance criteria before implementation.