![]() ![]() Built-in Social Media plugin support (Youtube, Youtube Search, Facebook, Twitter, Instagram, VK, LinkedIn Groups, LinkedIn home feed, LinkedIn Jobs, LinkedIn hashtag feed, Yammer, Bitchute, Vimeo, SlideShare, Pinterest, Reddit, Telegram, Rumble, Dribbble, eBay (4.13.0+), DeviantArt, Behance) Full standalone feed reader (RSS, Atom, RDF) as a Firefox/Chrome/Vivaldi extension - no online services needed We believe privacy is important so that only you know what sources you follow. ![]() Therefore it is vital to learn new things every day and follow relevant and valuable sources of information effortlessly. We believe that the faster you learn, gain new knowledge and information the better you will succeed in life as an individual and as an organization. We believe that all the new information that you are interested in, should be automatically aggregated into one place from various sources you care about (both Internet and intranet) into easy-to-read format and automatically filtered based on the rules you define. We believe it is waste of valuable time to spend minutes or even hours every day to go through dozens of websites, blogs, news sites and social media sites manually. View the entire comment thread.We believe time is our most valuable asset. Once the feature becomes available, I'm sure many organizations will allow, and even encourage, the use of the RSS channel as an alternative to automated emails, and of course develop the required server modules. In order to get the whole thing working, mobile reader software developers must first implement the required client functionality. The client reader software on my phone will automatically decrypt the feeds upon arrival. The organization server will deliver a public key to my Blackberry and encrypt all RSS feeds with the corresponding private key before delivery. I think the best way to implement feed encryption is to use RSA public key cryptography. This solution has been suggested many times, but I don't see the feature getting implemented in any of the feed readers I tried in my blackberry. Of course we can trust those companies, but be sure our boss won't do it.įeed encryption is the way to go, for both the title and the description fields of the feed. The main reason they stand in the middle is to provide a better service, because the device has only one server to poll which will deliver the feeds in a compressed format. In order to do that, they require us to send them the password, which will be stored and used by their servers. Most feed reader clients, specially those available in mobile phones, will retrieve the feeds from a third party company, which in turn does the polling of the feeds from the feed servers. Password protected feeds are of no use either. The URL can be guessed, but even in case it's impossible to guess, most users access their feeds via feed aggregators, making both the URL and the feed content available to third party companies. Using custom feed URLs for each user will not keep the feeds private. The feeds have to be readable only for the user they are addressed to. I understand issues of certain classes my require immediate attention and will still need to be notified in particular, but for all others it would be nice to receive a single mail every day with a summary of our pending notifications, which we can read using our feed reader of choice.īut the key problem here is privacy. What if we could read all those notifications whenever we want to, using our favorite RSS reader? They send us tons of mails everyday in an attempt to keep us informed of every management aspect of the organization, including posts in the intranet forums, task assignments and deadlines, status of indicators, addition or changes in important records, etc. Many intranet applications, used at the organization level to manage internal information, are no more no less than huge spammers. First of all I want to state I'm not an expert in the field of cryptography, so I apologize in advance if this article is flawed either by misconceptions or technical details. ![]()
0 Comments
Leave a Reply. |