Here’s the crux of the matter: I fail to discern how an update/broadcast system would alleviate such occurrences - and not for lack of understanding your arguments. Rather for considering and refuting your arguments. A mailing list would be the nearest approximation of a system similar to your proposed one to lessen the frequency of these posts, but I do not believe that you envision broadcasting an entire mailing list throughout the Network. Surely not.
This “posting questions to known hangups” is a familiar issue with FOSS enthusiasts. Standard practice (and trust me, many systems have been tried and tested) is to put it in a repository to be searched - or linked to by experienced members of the community (such as yourself) in answer to such questions in a forum or mailing list type system.
No, what you are talking about is a news feed full of update announcements, developments in development (<- like what I did there???), and other news.
News is not support. Support is a two-way street. Broadcasts (of this sort) are one-way, and not suited for support.
Forums and mailing list type support also have the added benefit of being collaborative, editable and searchable. All of which this “broadcast system” would be without.
Also, what happens when I don’t log in for weeks? Well, it’s not done via
mpid_messaging so it would have to find another way to live on the Network while I’m offline. And when I do logon, will I need to view those before I’m able to log into the Network? If not, what’s the use of them to warning me about the Network changes?
< smacz-being-a-dick > So once again: nay. If you would like to argue specific points of your proposal instead of asserting baseless conclusions, I would be all ears (or…well…eyes). Here are some that we’ve gone through:
- Is not modular (only allows “official” updates - no other entity could utlize the protocol)
- Is unsolicited
- Can feasibly be set up on the network separately and interactively
- We already have mpid_messaging that can handle offline notifications and messages
- does not offer the tech-savvy early adopters the benefits that you claim it does (no matter how many times you insist the contrary)
- does not take into account future variations on launcher
- does not notify the people who need update alerts the most - farmers
- does not offer support ability for people in the community with questions
Basically you just created something for my Nana - who isn’t an early adopter. Here’s a thought: design the Network (in the early stages) for the people who are actually going to use it. < \ok-i’m-done >
To your credit, it is something that I considered earlier. I didn’t make a post about it because I dismissed it in deference to the more thought-out “RSS/Atom news feed”-like system as @Tim87 mentioned. Now what might be effective is to distribute the launcher with a news feed system addon inside of the Launcher with the “official” channel pre-loaded. Something to think about.