Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://vowe.net/index.rdf

  1. <?xml version="1.0" encoding="iso-8859-1"?>
  2.  
  3. <rss version="2.0"
  4.  xmlns:dc="http://purl.org/dc/elements/1.1/"
  5.  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  6.  xmlns:admin="http://webns.net/mvcb/"
  7.  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  8.  xmlns:atom="http://www.w3.org/2005/Atom">
  9.  
  10. <channel>
  11. <title>:: vowe dot net ::</title>
  12. <link>https://vowe.net/</link>
  13. <description>communicate :: collaborate :: commemorate</description>
  14.  
  15. <dc:language>en-us</dc:language>
  16. <dc:creator>Volker Weber</dc:creator>
  17. <dc:date>2017-07-26T13:08:23+02:00</dc:date>
  18.  
  19. <admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.661" />
  20. <atom:link href="https://vowe.net/index.rdf" rel="self" type="application/rss+xml" />
  21. <sy:updatePeriod>hourly</sy:updatePeriod>
  22. <sy:updateFrequency>1</sy:updateFrequency>
  23. <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
  24.  
  25. <item>
  26. <title>IBM Connections Engagement Center V6.0 becomes available</title>
  27. <link>https://vowe.net/archives/016490.html</link>
  28. <description><![CDATA[<p>At the end of May, IBM announced it had acquired an asset from Timetoact that was known as XCC and that it would become available as IBM Connections Engagement Center. This acquisition was driven by Ed Brill, Vice President Product Management and Design, IBM Collaboration Solutions, and Felix Binsack, founder and CEO of Timetoact Group. It probably helped that both have known and trusted each other for many years.</p>
  29.  
  30. <p>In less than two months IBM and Timetoact have completed the "bluewashing" of the asset. That means you have to touch every single line of code, vet the intellectual property, provide proper language support and turn a business partner product into an IBM product. Here is the <a href="http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS217-317/index.html&amp;request_locale=en">annoucement letter</a>, availability is in two days.</p>
  31.  
  32. <p>If you read the announcement letter, it may not become perfectly clear what the product does. But it's quite simple. Engagement Center augments the collaborate applications from Connections with additional modules you would find in an intranet. It completes the experience, and I believe it's a must-have for a successful Connections portal. Employees will find everything in one place.</p>
  33.  
  34. <p>Engagement Center is priced between 28 and 35 \x80 per user, if you acquire a license for on premises installation. For enterprise customers, IBM likes to provide special bids.</p>]]></description>
  35. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  36. <dc:creator>Volker Weber</dc:creator>
  37. <dc:date>2017-07-26T13:08:23+02:00</dc:date>
  38. </item>
  39.  
  40. <item>
  41. <title>Moto Z2 Force announced</title>
  42. <link>https://vowe.net/archives/016488.html</link>
  43. <description><![CDATA[<p><img alt="z2force" src="https://vowe.net/images/z2force-20170726101200.jpg" width="640" height="641" /></p>
  44.  
  45. <p>What makes the Moto Z2 Force so interesting is a 5.5-inch Quad HD POLED display with ShatterShield, which is a layer of shatter resistant coating on top. It makes the display more prone to scratches but it is highly unlikely you ever damage the display by dropping your phone. The Z2 is ridiculously thin and built from reinforced 7000 series aluminum for added rigidity.</p>
  46.  
  47. <p>On the back of the phone is a new dual camera system witout optical image stabilisation, consisting of two 12 megapixel f2.0 cameras. One captures full color and the other is monochrome. The Qualcomm Snapdragon 835 chipset brings signal processing to the table that will combine both sensors for color photos with a shallow depth of field. You can also shoot monochrome images with the second sensor only.</p>
  48.  
  49. <p>The Z2 Force is a flagship smartphone, given its chipset and cameras, and comes with gigabit LTE, dual band Wi-Fi 802.11ac with MIMO, Bluetooth 4.2 with 5.0 support coming with Android O update. It has water repellant nano coating, a USB-C port for data and audio, but no headphone jack. Battery capacity is 2730mAh and thus 10% less than the Z2 Play. It should charge reasonably fast with its 15 W charger. The battery capacity and wireless charging can be upgraded via Moto Mods.</p>
  50.  
  51. <p>Pricing and availability hasn't been announced for Europe. While the US version comes with 4 GB of RAM, the EU version is rumored to have 6 GB. Internal storage of 64 GB can be expanded via MicroSD.</p>]]></description>
  52. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  53. <dc:creator>Volker Weber</dc:creator>
  54. <dc:date>2017-07-26T12:12:00+02:00</dc:date>
  55. </item>
  56.  
  57. <item>
  58. <title>IBM Connections Mobile 6.0 now available for iOS and Android</title>
  59. <link>https://vowe.net/archives/016489.html</link>
  60. <description><![CDATA[<p><img alt="Screen-Shot-2017-07-25-at-11.28" src="https://vowe.net/images/screen-shot-2017-07-25-at-11.28.22-am-768x571-20170726101943.png" width="640" height="475" /></p>
  61.  
  62. <blockquote>The IBM Connections Mobile app now provides a new tabbed navigation which allows users to easily switch between the different Connections services.  The navigation is customizable allowing individuals to determine which of the services they want displayed in the navigation menu. Also available in this release is the new updates view,  allowing users to quickly see the most recent updates in the network.
  63.  
  64. <p></blockquote><a href="https://www.ibm.com/blogs/ibm-social-software/2017/07/25/ibm-connections-mobile-6-0-now-available-ios-android/">More &gt;</a></p>]]></description>
  65. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  66. <dc:creator>Volker Weber</dc:creator>
  67. <dc:date>2017-07-26T10:19:43+02:00</dc:date>
  68. </item>
  69.  
  70. <item>
  71. <title>Stuff that works :: Marshall Monitor Bluetooth</title>
  72. <link>https://vowe.net/archives/016487.html</link>
  73. <description><![CDATA[<p><img src="//vowe.net/images/5d227c00dc05813404f0620c92ca9a59.jpg" alt="5d227c00dc05813404f0620c92ca9a59" width="640" height="640" /></p>
  74.  
  75. <p>The AirPods are my favorite earbuds. And the Marshall Monitor is my favorite over-the-ear headset. It fits my large head and my ears, it plays well with my very own set of music, and the battery seems to last forever. No active noise cancellation but excellent passive isolation, a single brass knob to control everything. Not to forget that is goes to eleven.</p>
  76.  
  77. <p><img src="//vowe.net/images/cce4d06d07243b1320372e1669bfc09e.jpg" alt="cce4d06d07243b1320372e1669bfc09e" width="640" height="423" /></p>
  78.  
  79. <p>Update for Ralph: yes, it shows its battery level both in the header and the widget. More importantly, volume is coordinated. It does not matter if you adjust it via the brass knob, the iPhone volume rocker or the Apple Watch. Be careful here. I hardly ever have this headset over 50 percent volume. </p>]]></description>
  80. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  81. <dc:creator>Volker Weber</dc:creator>
  82. <dc:date>2017-07-25T11:03:56+02:00</dc:date>
  83. </item>
  84.  
  85. <item>
  86. <title>Wishlist for #Sonos :: The results</title>
  87. <link>https://vowe.net/archives/016486.html</link>
  88. <description><![CDATA[<p><img alt="Sketch" src="https://vowe.net/images/sketch-54-20170725131046.png" width="640" height="363" /></p>
  89.  
  90. <p>Thank you for your votes on this poll. A few comments:</p>
  91.  
  92. <ul>
  93. <li>A poll can only have four choices. I selected these because they directly affect the user experience. They are in alphabetical order.</li>
  94. <li>Twitter analytics say the poll was seen by ten times the votes. Only one in ten people voted.</li>
  95. <li>The results have been very stable. From the first 50 votes to 250, it was always one in two who wanted AirPlay, three in ten wanted Alexa (and other voice assistants). And the remaining votes were split between a new desktop and mobile app.</li>
  96. </ul>
  97.  
  98. <p>The strong vote for AirPlay is even more significant if you take into account that only Apple users will benefit from this. Android users couldn't care less. I deduct that almost all Apple users want AirPlay support.  We know that Sonos is working on Alexa integration as announced last year in New York, but we don't know about the other options.</p>
  99.  
  100. <p>I also got a lot of other suggestions as replies to this poll. Here is a short list: battery-powered PLAY:1, Apple Watch and Siri integration, a kids' mode for the app, a touch-friendly Windows 10 app, support for IPv6, Audible, Bluetooth, SMBv2/v3, 24/96, and TV remotes, list albums by year, HDMI switch in/out on Playbar/Playbase.</p>
  101.  
  102. <p>I think the strong vote for AirPlay and Alexa means that people are OK with their current remotes but want additional alternative options. I am using Sonos mostly via Spotify Connect these days. And the biggest item I have isn't even on the list. I want to be able to direct any sound, from a Windows PC, a Mac, an Android or an iPhone to a Sonos speaker. And I want the choices to be presented to be smart. There are many ways to detect a speaker near me.</p>]]></description>
  103. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  104. <dc:creator>Volker Weber</dc:creator>
  105. <dc:date>2017-07-24T14:01:52+02:00</dc:date>
  106. </item>
  107.  
  108. <item>
  109. <title>Bad streaming and good streaming</title>
  110. <link>https://vowe.net/archives/016485.html</link>
  111. <description><![CDATA[<p><img alt="Sketch" src="https://vowe.net/images/sketch-53-20170723141117.png" width="640" height="459" /></p>
  112.  
  113. <p>When Apple started AirPlay, it would stream everything three times across the network. From your library or music service through your access point to the app on your device, then back to the access point, then to your speaker. When you stream to a Bluetooth connected speaker, you are also streaming everything to your app and then via Bluetooth to the speaker. That's bad streaming.</p>
  114.  
  115. <p><img src="//vowe.net/images/1c808ce41ea4f4fd67d8e3b79f750b92.jpg" alt="1c808ce41ea4f4fd67d8e3b79f750b92" width="315" height="473" /> <img src="//vowe.net/images/f4b54e6ffbe7d1f0df500a1d85fa68cb.jpg" alt="f4b54e6ffbe7d1f0df500a1d85fa68cb" width="315" height="473" /></p>
  116.  
  117. <p>What Spotify Connect does is good streaming. You start streaming to your app, but then you tell it to cast to your speaker instead. A Spotify Connect enabled speaker knows how to pull your music from the service, without going through your phone. There are plenty of Spotify Connect certified speakers and amps on the market, and Sonos only entered this game in 2017. The downside of Spotify Connect is that it only works with Spotify, not with anything else. If you want to switch to Apple Music, you are locked in.</p>
  118.  
  119. <p>Sonos is agnostic to streaming services. When you add them to your household, they will all use good streaming. Your controller tells your players what to pull from where, and the music traverses your network only once. If you stream to multiple rooms, the music is pulled from the service only once and then distributed inside your local network from Sonos speaker to Sonos speaker. You will also notice that you can play multiple different streams from Spotify and it only counts as one user. The downside is that you have to use the Sonos controller plugin to select your music and fill your queue. That plugin is often less capable than the native app.</p>
  120.  
  121. <p>How do you know you are using good streaming? Take your device off the network by going into flight mode. If the music stops, you are using bad streaming. Sonos calls this the beer test. Can you leave the party to get more beer without the music stopping?</p>
  122.  
  123. <p><img src="//vowe.net/images/5172fe916c647dbf7690459106235c84.jpg" alt="5172fe916c647dbf7690459106235c84" width="315" height="473" /> <img src="//vowe.net/images/dcfddb20334f1fcdb837f318d3e1942e.jpg" alt="dcfddb20334f1fcdb837f318d3e1942e" width="315" height="473" /></p>
  124.  
  125. <p>Spotify is not the only service that can cast to your Sonos speaker directly from the native app using good streaming. On Android you can also use Google Play Music and then cast to your Sonos speaker, at which point it will pull directly from Google without going through your device. If you try the same on iOS, you will find that Google Play Music has no mechanism to cast to Sonos.</p>
  126.  
  127. <p><img src="//vowe.net/images/2d29827d71e4d323ef0adfc438d2dd2d.jpg" alt="2d29827d71e4d323ef0adfc438d2dd2d" width="315" height="560" /> <img src="//vowe.net/images/fd0ca7014b3940779525e1ec45feab20.jpg" alt="fd0ca7014b3940779525e1ec45feab20" width="315" height="560" /></p>
  128.  
  129. <p>What is badly missing is a way to tell Apple Music to play to Sonos from its native app. That is going to become very obvious when Apple HomePod ships. iOS users are likely to be Apple Music subscribers and Sonos speakers will be at a terrible disadvantage. If a customer buys a HomePod instead of a PLAY:1 he is unlikely to buy a PLAY:5 or other Sonos speakers later. And if an existing Sonos customer with Apple Music buys a HomePod, he may be using his Sonos speakers a lot less.</p>
  130.  
  131. <p>When AirPlay launched you needed to buy a piece of silicon from Apple to enable your speaker to receivce the encrypted stream. That is no longer the case and you can build an AirPlay-compatible device in software. I always thought that Apple was hard to work with but I have learned they are actually pushing vendors to support their architecture.</p>
  132.  
  133. <p>Now would be a good time for Sonos customers to convince their vendor to support AirPlay.</p>]]></description>
  134. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  135. <dc:creator>Volker Weber</dc:creator>
  136. <dc:date>2017-07-23T14:11:18+02:00</dc:date>
  137. </item>
  138.  
  139. <item>
  140. <title>Sonos, please update your ancient network stack</title>
  141. <link>https://vowe.net/archives/016484.html</link>
  142. <description><![CDATA[<p><img alt="sonoszpcr" src="https://vowe.net/images/sonoszpcr-20170721143712.jpg" width="500" height="289" /></p>
  143.  
  144. <p>We love that Sonos keeps its old gear updated and functional. That is pretty much unheard of in this industry. However, there is one big omission. You really need to work on your network stack. Two problems:</p>
  145.  
  146. <ol>
  147. <li>Every recent piece of malware used SMBv1 as its attack vector. If you <a href="https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows">disable</a> it Sonos is unable to find its music libary anymore. No support for SMBv2 or SMBv3. This needs to be fixed ASAP.</li>
  148. <li>Your STP implementation is ancient. If you add Sonos to a network with smart components that use STP (spanning tree protocol) it messes up the network. Yes, you can fix the path costs everywhere else, but why don't you just fix it in your own stack? This discussion is already <a href="https://en.community.sonos.com/troubleshooting-228999/sonos-and-the-spanning-tree-protocol-16973">seven years old</a>.</li>
  149. </ol>
  150.  
  151. <p>If you like to discuss this, you know where to find me.</p>]]></description>
  152. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  153. <dc:creator>Volker Weber</dc:creator>
  154. <dc:date>2017-07-21T14:37:13+02:00</dc:date>
  155. </item>
  156.  
  157. <item>
  158. <title>IBM Dumps Remote Work, Blows Off Its Productivity Kneecap</title>
  159. <link>https://vowe.net/archives/016483.html</link>
  160. <description><![CDATA[<p>With a focus on US policy:</p>
  161.  
  162. <blockquote>IBM has destroyed a remote work policy that brought them provable gains, because a fashion exec says it&rsquo;ll save the entire company. The IBM decision-makers are either voluntarily ignorant, or they think they&rsquo;re above the market.<br /><br />20 straight quarters of declining revenue says they are wrong.</blockquote>
  163.  
  164. <p>Make that 21.</p>
  165.  
  166. <p><a href="http://remotework.works/2017/06/10/ibm-dumps-remote-work-blows-off-productivity-kneecap/">More &gt;</a></p>]]></description>
  167. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  168. <dc:creator>Volker Weber</dc:creator>
  169. <dc:date>2017-07-20T18:32:15+02:00</dc:date>
  170. </item>
  171.  
  172. <item>
  173. <title>Listen to podcasts on Sonos</title>
  174. <link>https://vowe.net/archives/016482.html</link>
  175. <description><![CDATA[<p><img alt="pocketcasts-sonos2x" src="https://vowe.net/images/pocketcasts-sonos2x-20170720130747.png" width="640" height="426" /></p>
  176.  
  177. <blockquote>Today we&rsquo;re excited to announce that Pocket Casts support for Sonos has gone into Beta! Judging by the amount of tweets and emails we&rsquo;ve had over the years this is one of your most requested features and we&rsquo;re excited to finally share it with you.</blockquote>
  178.  
  179. <p><a href="https://blog.shiftyjelly.com/2017/07/20/pocket-casts-sonos-support-beta/">More &gt;</a></p>]]></description>
  180. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  181. <dc:creator>Volker Weber</dc:creator>
  182. <dc:date>2017-07-20T13:07:49+02:00</dc:date>
  183. </item>
  184.  
  185. <item>
  186. <title>Drei Android-Smartphones</title>
  187. <link>https://vowe.net/archives/016481.html</link>
  188. <description><![CDATA[<p><img alt="IMG 0126" src="https://vowe.net/images/img_0126-20170719095355.jpg" width="640" height="479" /></p>
  189.  
  190. <p>Die Welt ist ein bisschen einfacher geworden f&uuml;r mich. Fr&uuml;her hatte ich ein halbes Dutzend verschiedene Smartphone-Betriebssysteme im Auge zu behalten. Heute sind es nur noch zwei. Damit ich nicht nur das iPhone kenne, benutze ich t&auml;glich mehrere Stunden auch ein Android-Ger&auml;t. Bisher waren das zwei: BlackBerry KEYone und Huawei P10. Jetzt ist mit dem Moto Z2 Play ein drittes dazu gekommen. Bemerkenswert beim Moto: wenn man es nur im Standby rumliegt, dann sagt es nach zwei Tagen, es habe noch Saft f&uuml;r sechs weitere.</p>
  191.  
  192. <p>Ich k&ouml;nnte mich nur sehr schwer f&uuml;r eines dieses Telefone entscheiden. Das KEYone hat die aktuellste Software und ist am dichtesten dran an Pure Android. Es greift sich am besten, das hei&szlig;t man kann es sehr leicht aufnehmen und in der Hand halten. Deshalb nutze ich es gerne, um Nachrichten zu lesen. Das Hardware-Keyboard macht mich nicht schneller, wie man eigentlich meinen sollte.</p>
  193.  
  194. <p>Das P10 ist das mit Abstand eleganteste. Sehr zur&uuml;ckhaltend, ohne hervorstechende Merkmale. Die Kamera passt komplett in das d&uuml;nne Geh&auml;use. Anders als bei den anderen beiden ist es nicht so leicht zu f&uuml;hlen, ob man es richtig herum in der Hand hat. Und ich bin immer etwas besorgt, dass es mir aus der Hand f&auml;llt. Wenn ich auf dem Sofa l&uuml;mmle, dann passiert das ziemlich oft, nat&uuml;rlich ohne Schaden. Mittlerweile nutze ich die P10-Kamera bevorzugt, weil sie gute Makro-Shots produziert. </p>
  195.  
  196. <p>Moto und Huawei sind bei den Security Patches hinten dran. Bei Huawei wird das wegen der umfangreichen Android-Anpassungen wohl auch nicht besser. Moto h&auml;tte die Chance. Ich warte auf die gro&szlig;e Malware-Epidemie, bei der das &Uuml;berleben stark von aktueller Software abh&auml;ngt. Immerhin ist erkennbar, dass sich immer mehr Hersteller darum bem&uuml;hen.</p>
  197.  
  198. <p>Was mich bei jedem Einschalten flasht, ist der Sperrbildschirm des P10. Huawei hat eine wunderbare Auswahl wechselnder Bilder, die mich tats&auml;chlich den Einschaltknopf vor dem blitzschnellen Fingerabdrucksensor dr&uuml;cken l&auml;sst.</p>]]></description>
  199. <guid isPermaLink="false">[email protected]://vowe.net/</guid>
  200. <dc:creator>Volker Weber</dc:creator>
  201. <dc:date>2017-07-19T09:53:53+02:00</dc:date>
  202. </item>
  203.  
  204.  
  205.  
  206. </channel>
  207. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//vowe.net/index.rdf

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda