RSS aka RDF Site Summary aka Rich Site Summary aka Really Simple Syndication is a standardized web format that works for you.
At least it would work for you if you would use a a tool which would allow you to “subscribe” to RSS feeds from all sorts of websites. These tools are called feed-reader.
The website you are reading this on offers such a link. By subscribing to its feed you will be able to see all content but without having to actually go to each of your subscriptions one by one. That is done by the feed reader. This process of aggregation is it why feed readers are also called aggregator.
Invented exactly 20 years ago this month on the back-end of a feverish dot-com boom, RSS (Real Simple Syndication) has persisted as a technology despite Google’s infamous abandonment with the death of Google Reader and Silicon Valley social media companies trying and succeeding to supplant it. In the six years since Google shut down Reader, there have been a million words written about the technology’s rise and apparent fall. Here’s what’s important: RSS is very much still here. Better yet, RSS can be a healthy alternative…
I am using Liferea as my feed reader on desktop and Reeder on all that is iOS/macOS.
I’ve found that by using RSS feeds and not following a pre-filtered timeline I would not “follow” 1000 sources of information but choose more carefully whom to follow.
Some do not offer any feeds – so my decision in these cases is wether or not I would invest the time to create a custom parser for their content to pull in.
After RSS being just another XML format you quickly realize that HTML is just another XML format as well. There are simple ways to convert between both on the fly. Like fetchrss.com or your command-line.
Of course RSS is not the only feed format: ATOM would be another one worth mentioning.
Many use and love archive.org. A service that roams the public internet and archives whatever it finds. It even creates timelines of websites so you can dive right into history.
Have a piece of history right here:
You can have something similar hosted in your own environment. There are numerous open source projects dedicated to this archival purpose. One of them is ArchiveBox.
ArchiveBox takes a list of website URLs you want to archive, and creates a local, static, browsable HTML clone of the content from those websites (it saves HTML, JS, media files, PDFs, images and more).
I’ve done my set-up of ArchiveBox with the provided Dockerfile. Every once in a while it will start the docker container and check my Pocket feed for any new bookmarks. If found it will then archive those bookmarks.
As the HTML as well as PDF and Screenshot is saved this is extremely useful for later look-ups and even full-text search indexing.
There are some things that, when looked at closely, just amaze you. This picture was like that for me:
I stumbled on this picture on Twitter. At first it looks like your average japanese train. With the blue seat cushions. The adverts and hand rails. All normal, right?
If you read the text or start to zoom in you will find that this is not a picture taken with a camera. This is a drawing.
This visual art is called Hyperrealism and it takes a lot of dedication and skill when done free-hand.
The artist had posted this picture on his Twitter feed. He explains that he had drawn it whilst commuting on the train over the course of a month. He used an iPad Pro and MediBang Paint. Of course he also names the train-type: Tobu Series 5050 used by the Tobu line in the greater Tokyo area.
This experiment great since it’s completely effortless. You link your block lists once and from thereon you keep using Twitter like you always did. Whenever you see a paid promotion you “block it”. Everybody from thereon will not see promotions and timeline entries from this specific Twitter user (unless you would actively follow them).
And the effect after about a week is just great! I cannot see a downside so far but the amount of promotion content on my timeline has shrunk to a degree where I do not see any at all.
This is a great way to get rid of content you’ve never wanted and focus on the information you want.
In the interesting field of IoT a lot of buzz is made around the predictive maintenance use cases. What is predictive maintenance?
The main promise of predictive maintenance is to allow convenient scheduling of corrective maintenance, and to prevent unexpected equipment failures.
The key is “the right information in the right time”. By knowing which equipment needs maintenance, maintenance work can be better planned (spare parts, people, etc.) and what would have been “unplanned stops” are transformed to shorter and fewer “planned stops”, thus increasing plant availability. Other potential advantages include increased equipment lifetime, increased plant safety, fewer accidents with negative impact on environment, and optimized spare parts handling.
So in simpler terms: If you can predict that something will break you can repair it before it breaks. This improvse reliability and save costs, even though you repaired something that did not yet need repairs. At least you would be able to reduce inconveniences by repairing/maintaining when it still is easy to be done rather than under stress.
You would probably agree with me that these are a very industry-specific use cases. It’s easy to understand when it is tied to an actual case that happened.
Let me tell you a case that happened here last week. It happened to Leela – a 10 year old white British short hair lady cat with gorgeous blue eyes:
Ever since her sister had developed a severe kidney issue we started to unobtrusively monitor their behavior and vital signs. Simple things like weight, food intake, water intake, movement, regularities (how often x/y/z).
When Leela now visits her litter box she is automatically weighed and it’s taken note that she actually used it.
A lot of data is aggregated on this and a lot of things are being done to that data to generate indications of issues and alerts.
This alerted us last weekend that there could be an issue with Leelas health as she was suddenly visiting the litter box a lot more often across the day.
We did not notice anything with Leela. She behaved as she would everyday, but the monitoring did detect something was not right.
What had happened?
On the morning of March 9th Leela already had been to the litter box above average. So much above average that it tripped the alerting system. You can see the faded read area in the top of the graph above showing the alert threshold. The red vertical line was drawn in by me because this was when we got alerted.
Now what? She behaved totally normal just that she went a lot more to the litter box. We where concerned as it matched her sisters behavior so we went through all the checklists with her on what the issue could be.
We monitored her closely and increased the water supplied as well as changed her food so she could fight a potential bladder infection (or worse).
By Monday she did still not behave different to a degree that anyone would have been suspicious. Nevertheless my wife took her to the vet. And of course a bladder infection was diagnosed after all tests run.
She got antibiotics and around Wednesday (13th March) she actually started to behave much like a sick cat would. By then she already was on day 3 of antibiotics and after just one day of presumable pain she was back to fully normal.
Interestingly all of this can be followed up with the monitoring. Even that she must have felt worse on the 13th.
With everything back to normal now it seems that this monitoring has really lead us to a case of “predictive cat maintenance”. We hopefully could prevent a lot of pain with acting quick. Which only was possible through the monitoring in place.
Health is a huge topic for the future of devices and gadgets. Everyone will casually start to have more and more devices in their daily lifes. Unfortunately most of those won’t be under your own control if you do not insist on being in control.
You do not have to build stuff yourself like I did. You only need to make the right purchase decisions according to things important to you. And one of these things on that checklist should be: “am I in full control of the data flow and data storage”.
If you are not. Do not buy!
By coincidence the idea of having the owner of the data in full control of the data itself is central to my current job at MindSphere. With all the buzz and whistles around the Industry IoT platform it all breaks down to keep the actual owner of the data in control and in charge. A story for another post!
My usual twitter use looks like this: I am scrolling through the timeline reading up things and I see an ad. I click block and never again will I see anything from this advertiser. As I’ve written here earlier.
As Twitter is also a place of very disturbing content there are numerous services built around the official block list functionality. One of those services is “Block Together“.
Block Together is designed to reduce the burden of blocking when many accounts are attacking you, or when a few accounts are attacking many people in your community. It uses the Twitter API. If you choose to share your list of blocks, your friends can subscribe to your list so that when you block an account, they block that account automatically. You can also use Block Together without sharing your blocks with anyone.
I had redone the header of this blog a while ago but since I was trying around some things on the template I wanted something more dynamic but without any additional dependencies.
So I searched and found:
Tim Holman did a very nice implementation of this “worm generator” with only using the HTML5 canvas tag and some math. I made some very slight changes and integrated it into the header graphic. It will react to your mouse movement and resets if you click anywhere. Give it a go!
PWA simply put is a standardized way to add some context to websites and package them up so they behave as much like a native mobile application. A mobile application that you are used to install onto your phone or tablet most likely using an app store of some sort.
The aim of PWA is to provide a framework and tooling so that the website is able to provide features like push notifications, background updates, offline modes and so on.
Very neat. I’ve just today have enabled the PWA mode of this website, so you’re now free to add it to your home screen. But fear not: You won’t be pestered with push notifications or any background stuff taking place. It’s merely a more convenient optional shortcut.
I am currently in the process of reducing my presence on the usual social networks. Here is my reasoning and how I will do it.
Facebook, Twitter, Instagram and alike are seemingly at the peak of their popularity and more and more users get more and more concerned about how their data and privacy is handled by those social networks. So am I.
Now my main concern is not so much on the privacy side. I never published anything on a social network – private or public – that I would not be published or freely distributed/leak. But:
I have published content with the intention that it would be accessible to everyone now and in the future. The increasing risk is that those publishing platforms are going to fade away and thus will render the content I had published there inaccessible.
My preferred way of publishing content and making sure that it stays accessible is this website – my personal blog.
I am doing this since 2004. The exact year that Facebook was founded. And apparently this website and it’s content has a good chance of being available longer than the biggest social network at the present time.
So what does this mean? 3 basic implications:
I will become a “lurker” on the social networks. Now and in the future.
All comments and reactions I will make will be either directly in private or through my personal website publicly available and linkable.
As you can see: This is not about a cut or abstinence. I get information out of social networks, tweet message flows. But I do not put any trust in the longevity of both the platforms and the content published there.
The next steps for me will be a complete overaul of this website. Get everything up to current standards to streamline my publishing process.
Expect a lot of content and change – and: welcome to my blog!
A couple of days ago the well known and much read Nerdcore weblog author created a page he calls NC-Sources which lists all the sources he has in his RSS reader to get new information from. As you can imagine, this is pure gold for those who want to get interesting links to all-nerd pages.
Unfortunately NC-Sources is just available as a web-page which lists the name and the RSS feed URL. You cannot import that into your RSS Reader to use it for your own informational needs.
Here I am to the rescue. I’ve taken all the URLs from that NC Source page. That resulted in a file that lists the page url and the rss-feed url in alternating lines. A short trip to the command line and the use of awk helped to filter just the rss-feed urls to a new file and that was filled into an opml generator.
So now you can download the OPML file to import it into your own RSS reader. Get it here.
For several years now I am interested in this home automation thing – I even got a little bit of my own home automation going. But with websites like domotica you can get an idea of what is achieveable and how it might look for the people actually using it every day.
In an accompanying step they just released the 2011 version of the Windows Live Writer. Actually I think it’s a shame that there is no comparable tool on Mac OS X … which is quite unusual since those types of tools in that quality are more common on the apple platform.
The new Window Live Writer 2011 comes with the Ribbon UI already known from Office 2007 and 2010 (and 2011 now).
…switch this website to another weblog software in the future. The dasBlog development isn’t exactly what I would call fast-paced. It even seems that there was no movement at all for the last year at all regarding new features.
I took a short look at a current WordPress installation we did for our Developer Website at sones – and I have to admit that feature-wise this WordPress is way beyond anything I could achieve in dasBlog anytime soon.
Additionally the fact that the skin of this site seems to be broken (especially for older browsers) I would have to do a skin-redesign – turns out that this is way easier in WordPress than it is in dasBlog.
The internet comes up with new ideas of information transformation and management every day. Yahoo now came up with a great idea of how the users could almost freely transform syndicateable data to anything they like.
Yahoo says this about it’s new baby:
“Pipes is an interactive feed aggregator and manipulator. Using Pipes, you can create feeds that are more powerful, useful and relevant.”
If you ever wanted to connect NY Times articles to Flickr, you can do this and many other things now. You even get a decent editor:
Note the large section in your web.config and the mobile theme that is required for this support.
Huge (100x+) speedup in Macro execution – from Scott
Support for If-Not-Modified to speed up execution, improve RSS bandwidth and CPU cycles – from Scott
Direct Feedburner Support with 301 redirection for RSS and Atom feeds. Don’t lose a single subscriber. We’re the only blog with direct support for Feedburner and Feedflare I believe. – from Scott
I encourage you to check out FeedBurner. You can add FeedFlare to your posts, and modify your feed in ways DasBlog can’t. They also handle your Feed bandwidth and provide rich statistics. It’s free ($ for advanced stats) and it’s very powerful. Do be aware that when you make the decision to move over to FeedBurner your existing feeds will start redirecting folks to FeedBurner immediately. That’s part of the power of the whole thing, but be warned.
Delete comments directly from your mail reader – from Omar
Comment moderation option
New themes out of the box, 18 at last count – from Many Folks
New XML-RPC support for newMediaObject and new version of XML-RPC.NET from Charles Cook – from Omar and Giuseppe Dipietro
Macros for Next Post and Previous Post – Justice Gray
Check the DasBlog theme or add this line to the top of your itemtemplate.blogtemplate. <%PreviousLink("« ",25)%><%MainPageEntryLink("Main", "|")%><%NextLink(" »",25)%>
A few security and XSS fixes
Support for Gravatars, images of your choosing that appear next to your comments – John Forsythe
Support for limited HTML markup in comments – Alexander Groß
Emails removed to avoid having email addresses stolen from Feeds
Added an Email page for leaving comments to the author, includes Captcha
New support for RSD so client software can autoconfigure itself – from Omar
Pluggable Rich Text Editor, choose from the latest version of FreeTextBox or FCKEditor or write your own adapter – from Josh Flanagan
Automatic disabling of Comments after a certain number of days. Also manual “close comments” support – from Omar
ContentLookAhead show future dated posts – from Josh Flanagan
Other fixes and suggestions from Tomas Restrepo, Jason Follas, Rene Lebherz and Steven Rockarts. Added entry CPU usage optimizatons from George V. Reilly.
Ajax Autosave Drafts support from Steven Rockarts and Justice Gray.
Better strings and support for German, Portueguese, Turkish and Vietnamese from Ph?m Ð?c H?i.
Many great new themes
Updated readme.rtf from Tim Sherill
Single-handed support of DasBlog.info and DasBlog.us to the enthusiastic and tireless Tom Watts!
Welcome to new team members Alexander Groß, Paul Van Brenck, and John Forsythe who really did a lot of work to make this release possible! Thanks to Jacob Proffitt for doing some crazy debugging of caching on FireFox that will be in a point release soon.
“A CAPTCHA (an acronym for “completely automated public Turing test to tell computers and humans apart”, trademarked by Carnegie Mellon University) is a type of challenge-response test used in computing to determine whether or not the user is human.”
This technology is mainly used to filter all those spammers from the normal commenting users. Schrankmonster even uses this technology. Kiesow doesn’t like very long captchas and I don’t like dumb ones…like this one which was sent in by Tomasz Naumowicz: