![]() Heavier than JSON, but not drastically so, unless you decide you also need three types of schemas, two types of XPath, XSLT, etc. Though Yxml is probably overdoing it, what with its lack of Unicode handling or tree construction, a couple of tens of kilobytes seems like the right order of magnitude to me. ![]() Many of the replacements or pseudo-replacements that people come up with seem fine, but the problem - as always - is getting people to actually use it, which mostly never happens.Ī parser for what most people think of as XML can be fairly simple, certainly simpler than a performant or even just error-tolerant parser for HTML. I think feeds are pretty much doomed to keep breaking and disappearing. But it also sucks, and it's not any surprise that mostly only technical people use it. It's what we've got and we should continue to make the most of it. lots of posts include iframes, or content that only makes sense with JS enabledĭespite this, I still love RSS. if I want to follow any link I get kicked back out to a bloated web page If you want your feed to always have all posts available, you need to include the entirety of your archive in every feed response. there's no pagination mechanism, or way for a client to ask for "all posts since last Friday". every day I deal with broken links and broken images because my feed reader doesn't know from which URL it should resolve relative links I'm a very happy daily RSS user, but we ought to be upfront about its ginormous deficiencies: Thinking about, how is the state of accessibility-technologies today? Could it be used for easy and reliable parsing? This could easily sold with support for accessibility, and everyone would win here. Or just adapt the feedreader to better support the already existing structures? Something came out of this, but maybe we should light up that flame again and move it more into a direction where it could be used for our feedreaders. For example, there was a movement for embedding semantic and structural data right into a document. Instead, we should find ways to ease their work and help them satisfy our demands. We don't need to communicate better to the publisher to force our will onto them. The mass of user used to be bigger, but not to the level where it could be called a mass medium. Newsfeeds were always a minority-feature. > It used to be that the masses consumed RSS feeds. But there are also other ways and other tools for this. The point of RSS is to receive changes in a structured way. This would be good, but it seems most people are too focused on RSS and not much on the actual usage. (UDP) you can also use the get parameter version which can allow the growl request to behave using the older v1.x protocol.> Instead of focusing on a technology, let's focus on a problem. Notification Serviceīark://hostname/device_key1/device_key2/device_keyN Click on any of the services listed below to get more details on how you can configure Apprise to access them. The table below identifies the services this tool supports and some example service urls you need to use in order to take advantage of it. Check out the wiki for more information on the supported modules here. The section identifies all of the services supported by this library. Everything is already wrapped and supported within the apprise command line tool (CLI) that ships with this product. System Administrators and DevOps who wish to send a notification now no longer need to find the right tool for the job. They just need to include this one library and then they can immediately gain access to almost all of the notifications services available to us today. They no longer need to try to adapt to the new ones that comeout thereafter. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |