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://feed.informer.com/digests/AYKA2HVQUK/feeder.rss

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:docs="http://schemas.google.com/docs/2007" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml" xmlns:itms="http://phobos.apple.com/rss/1.0/modules/itms/" xmlns:twitter="http://api.twitter.com" version="2.0">
  3.  <channel>
  4.    <title>Chris Whisonant Blogs</title>
  5.    <link>http://feed.informer.com/digests/AYKA2HVQUK/feeder</link>
  6.    <description>Chris Whisonant Blogs</description>
  7.    <copyright>Respective post owners and feed distributors</copyright>
  8.    <pubDate>Thu, 12 Dec 2013 13:13:34 -0500</pubDate>
  9.    <generator>Feed Informer http://feed.informer.com/</generator>
  10.    <atom:link href="http://feed.informer.com/digests/AYKA2HVQUK/feeder" rel="self" type="application/rss+xml"/>
  11.    <item>
  12.      <title>Yosemite Bluetooth Audio Issues, Anyone?</title>
  13.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/yosemitebtlag?lang=en_us</link>
  14.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  15.      <guid isPermaLink="false">urn:uuid:d99a5649-807b-c8d9-8c3f-7cbc72e353fe</guid>
  16.      <pubDate>Tue, 18 Nov 2014 10:05:21 -0500</pubDate>
  17.      <description>I&amp;#39;m wondering if any of my readers have found any solutions to this or have run into it yourselves? I was hoping that the .1 update to Yosemite would fix this, but I see from comments&amp;nbsp;at&amp;nbsp;this&amp;nbsp;post that I&amp;#39;m not alone in my woes. Below is...</description>
  18.      <content:encoded>&lt;p dir="ltr"&gt;
  19. I&amp;#39;m wondering if any of my readers have found any solutions to this or have run into it yourselves? I was hoping that the .1 update to Yosemite would fix this, but I see from &lt;a href="http://www.idownloadblog.com/2014/11/17/apple-releases-yosemite-10-10-1/" target="_blank"&gt;comments&amp;nbsp;at&amp;nbsp;this&amp;nbsp;post&lt;/a&gt; that I&amp;#39;m not alone in my woes. Below is my comment related to the issue...&lt;/p&gt;
  20. &lt;blockquote dir="ltr"&gt;
  21. &lt;p&gt;
  22. I&amp;#39;m very disappointed with the bluetooth audio lag. We&amp;#39;re not talking about sub-second delays or &amp;quot;some lag&amp;quot; that would be expected with Bluetooth audio devices. What&amp;#39;s happening since the Yosemite 10.10 and STILL with 10.10.1 updates is that Bluetooth audio is unusable with video because it will quickly go from being in sync with the lips to having an audio lag of over a second or more. None of the &amp;quot;fixes&amp;quot; people have suggested (reboot, unpairing devices and re-pairing them, pram reset, etc...) actually work. From seeing other threads (just google: &lt;a href="https://www.google.com/search?q=mac+yosemite+bluetooth+audio+lag" target="_blank"&gt;mac&amp;nbsp;yosemite&amp;nbsp;bluetooth&amp;nbsp;audio&amp;nbsp;lag&lt;/a&gt;), this is quite widespread. I never had issues with lag on my LG HBS-730 in the past 2 years with a Macbook Air or my current Macbook Pro Retina. Well, I never had issues until the day I upgraded to Yosemite and now to the 10.10.1 release. Hopefully Apple will actually address this issue. There are also reports of Bluetooth keyboard and mouse issues with Yosemite.&lt;br&gt;
  23. &lt;br&gt;
  24. So, for now, I just plug in some iPhone earbuds so that audio is usable. :(&lt;/p&gt;
  25. &lt;/blockquote&gt;
  26. &lt;p dir="ltr"&gt;
  27. Any solutions out there for me to look into? I&amp;#39;m hoping that Apple will actually fix this issue reported on day 1 of Yosemite&amp;#39;s release...&lt;/p&gt;</content:encoded>
  28.    </item>
  29.    <item>
  30.      <title>On the Insidiousness of Facebook Messenger's App Permissions</title>
  31.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/on_the_insidiousness_of_facebook_messenger_s_app_permissions?lang=en_us</link>
  32.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  33.      <guid isPermaLink="false">urn:uuid:6cccc899-854d-8bc1-3aec-4ef5fb975433</guid>
  34.      <pubDate>Thu, 07 Aug 2014 08:38:28 -0400</pubDate>
  35.      <description>Much has been said lately about how horrible it is that Facebook is not only forcing their mobile users to use their new Messenger application (in order to send one-on-one or group messages), but also this app has permissions that no sane person should accept....</description>
  36.      <content:encoded>&lt;p dir="ltr"&gt;
  37. Much has been said lately about how horrible it is that Facebook is not only forcing their mobile users to use their new Messenger application (in order to send one-on-one or group messages), but also this app has permissions that no sane person should accept. The theory is that Facebook is overstepping their bounds and is now intruding (even further) into our lives.&lt;/p&gt;
  38. &lt;p dir="ltr"&gt;
  39. Being the logical person I can be, I knew that the full Facebook app just &lt;strong&gt;had&lt;/strong&gt; to have similar permissions. Yet it seems that nobody cares about those permissions - people will even use their mobile app to post about how horrible that new-fangled Messenger&amp;#39;s app permissions are.&lt;/p&gt;
  40. &lt;p dir="ltr"&gt;
  41. I hope the table below is helpful - I have a row for each set of permissions as taken from the Google Play store information just today for the most current versions. As you will be able to clearly see, the most &amp;quot;insidious&amp;quot; of permissions that we read about from the &lt;a href="http://www.washingtonpost.com/news/the-intersect/wp/2014/08/04/yes-the-facebook-messenger-app-requests-creepy-invasive-permissions-but-so-does-every-other-app/"&gt;Washington&amp;nbsp;Post&lt;/a&gt;, &lt;a href="http://www.huffingtonpost.com/sam-fiorella/the-insidiousness-of-face_b_4365645.html?utm_hp_ref=tw"&gt;Huffington&amp;nbsp;Post&lt;/a&gt;, and others are already granted to the main Facebook application. If you&amp;#39;ve been using the Facebook application without concern, then you really don&amp;#39;t have a leg to stand on with regards to increased permissions in the Messenger app (unless you&amp;#39;re REALLY concerned with it now having the ability to not just read but also create and modify text messages). To Washington Post&amp;#39;s credit, at least they headline with the tag that all other apps also request similar permissions. Also, the TOS discussion should be framed in the same way - &amp;quot;is Messenger really asking you to accept terms you haven&amp;#39;t already accepted by using Facebook?&amp;quot;&lt;/p&gt;
  42. &lt;p dir="ltr"&gt;
  43. &lt;/p&gt;
  44. &lt;table align="left" border="0" cellpadding="5" cellspacing="0" dir="ltr" style="width: 705px;" width="100%"&gt;
  45. &lt;colgroup&gt;
  46. &lt;col width="128*"&gt;&lt;/col&gt;
  47. &lt;col width="128*"&gt;&lt;/col&gt;
  48. &lt;/colgroup&gt;
  49. &lt;tbody&gt;
  50. &lt;tr valign="TOP"&gt;
  51. &lt;td style="width: 335px;"&gt;
  52. &lt;p&gt;
  53. &lt;span style="font-size:18px;"&gt;&lt;strong&gt;Facebook&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
  54. &lt;/td&gt;
  55. &lt;td style="width: 342px;"&gt;
  56. &lt;p&gt;
  57. &lt;span style="font-size:18px;"&gt;&lt;strong&gt;Facebook Messenger&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
  58. &lt;/td&gt;
  59. &lt;/tr&gt;
  60. &lt;tr valign="TOP"&gt;
  61. &lt;td style="width: 335px;"&gt;
  62. &lt;p style="margin-bottom: 0in"&gt;
  63. &lt;font size="2"&gt;This app has access to: &lt;/font&gt;&lt;br&gt;
  64. &amp;nbsp;&lt;/p&gt;
  65. &lt;p style="margin-bottom: 0.2in"&gt;
  66. &lt;font size="2"&gt;Device &amp;amp; app history &lt;/font&gt;&lt;/p&gt;
  67. &lt;ul&gt;
  68. &lt;li&gt;
  69. &lt;p&gt;
  70. &lt;font size="2"&gt;&lt;b&gt;retrieve running apps &lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  71. &lt;/li&gt;
  72. &lt;/ul&gt;
  73. &lt;/td&gt;
  74. &lt;td style="width: 342px;"&gt;
  75. &lt;p style="margin-bottom: 0in"&gt;
  76. &lt;font size="2"&gt;This app has access to: &lt;/font&gt;&lt;/p&gt;
  77. &lt;p style="margin-bottom: 0.2in"&gt;
  78. &lt;br&gt;
  79. &amp;nbsp;&lt;/p&gt;
  80. &lt;p&gt;
  81. &amp;nbsp;&lt;/p&gt;
  82. &lt;/td&gt;
  83. &lt;/tr&gt;
  84. &lt;tr valign="TOP"&gt;
  85. &lt;td style="width: 335px;"&gt;
  86. &lt;p&gt;
  87. &lt;font size="2"&gt;Identity &lt;/font&gt;&lt;/p&gt;
  88. &lt;ul&gt;
  89. &lt;li&gt;
  90. &lt;p style="margin-bottom: 0in"&gt;
  91. &lt;font size="2"&gt;find accounts on the device&lt;/font&gt;&lt;/p&gt;
  92. &lt;/li&gt;
  93. &lt;li&gt;
  94. &lt;p style="margin-bottom: 0in"&gt;
  95. &lt;font size="2"&gt;&lt;b&gt;add or remove accounts&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  96. &lt;/li&gt;
  97. &lt;li&gt;
  98. &lt;p&gt;
  99. &lt;font size="2"&gt;read your own contact card &lt;/font&gt;&lt;/p&gt;
  100. &lt;/li&gt;
  101. &lt;/ul&gt;
  102. &lt;/td&gt;
  103. &lt;td style="width: 342px;"&gt;
  104. &lt;p style="margin-bottom: 0.2in"&gt;
  105. &lt;font size="2"&gt;Identity &lt;/font&gt;&lt;/p&gt;
  106. &lt;ul&gt;
  107. &lt;li&gt;
  108. &lt;p style="margin-bottom: 0in"&gt;
  109. &lt;font size="2"&gt;find accounts on the device&lt;/font&gt;&lt;/p&gt;
  110. &lt;/li&gt;
  111. &lt;li&gt;
  112. &lt;p&gt;
  113. &lt;font size="2"&gt;read your own contact card &lt;/font&gt;&lt;/p&gt;
  114. &lt;/li&gt;
  115. &lt;/ul&gt;
  116. &lt;/td&gt;
  117. &lt;/tr&gt;
  118. &lt;tr valign="TOP"&gt;
  119. &lt;td style="width: 335px;"&gt;
  120. &lt;p&gt;
  121. &lt;font size="2"&gt;Contacts/Calendar &lt;/font&gt;&lt;/p&gt;
  122. &lt;ul&gt;
  123. &lt;li&gt;
  124. &lt;p style="margin-bottom: 0in"&gt;
  125. &lt;font size="2"&gt;read your contacts&lt;/font&gt;&lt;/p&gt;
  126. &lt;/li&gt;
  127. &lt;li&gt;
  128. &lt;p style="margin-bottom: 0in"&gt;
  129. &lt;font size="2"&gt;&lt;b&gt;modify your contacts&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  130. &lt;/li&gt;
  131. &lt;li&gt;
  132. &lt;p style="margin-bottom: 0in"&gt;
  133. &lt;font size="2"&gt;&lt;b&gt;read calendar events plus confidential information&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  134. &lt;/li&gt;
  135. &lt;li&gt;
  136. &lt;p&gt;
  137. &lt;font size="2"&gt;&lt;b&gt;add or modify calendar events and send email to guests without owners&amp;#39; knowledge&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  138. &lt;/li&gt;
  139. &lt;/ul&gt;
  140. &lt;/td&gt;
  141. &lt;td style="width: 342px;"&gt;
  142. &lt;p&gt;
  143. &lt;font size="2"&gt;Contacts/Calendar &lt;/font&gt;&lt;/p&gt;
  144. &lt;ul&gt;
  145. &lt;li&gt;
  146. &lt;p&gt;
  147. &lt;font size="2"&gt;read your contacts &lt;/font&gt;&lt;/p&gt;
  148. &lt;/li&gt;
  149. &lt;/ul&gt;
  150. &lt;/td&gt;
  151. &lt;/tr&gt;
  152. &lt;tr valign="TOP"&gt;
  153. &lt;td style="width: 335px;"&gt;
  154. &lt;p&gt;
  155. &lt;font size="2"&gt;Location &lt;/font&gt;&lt;/p&gt;
  156. &lt;ul&gt;
  157. &lt;li&gt;
  158. &lt;p style="margin-bottom: 0in"&gt;
  159. &lt;font size="2"&gt;precise location (GPS and network-based)&lt;/font&gt;&lt;/p&gt;
  160. &lt;/li&gt;
  161. &lt;li&gt;
  162. &lt;p&gt;
  163. &lt;font size="2"&gt;approximate location (network-based) &lt;/font&gt;&lt;/p&gt;
  164. &lt;/li&gt;
  165. &lt;/ul&gt;
  166. &lt;/td&gt;
  167. &lt;td style="width: 342px;"&gt;
  168. &lt;p&gt;
  169. &lt;font size="2"&gt;Location &lt;/font&gt;&lt;/p&gt;
  170. &lt;ul&gt;
  171. &lt;li&gt;
  172. &lt;p style="margin-bottom: 0in"&gt;
  173. &lt;font size="2"&gt;approximate location (network-based)&lt;/font&gt;&lt;/p&gt;
  174. &lt;/li&gt;
  175. &lt;li&gt;
  176. &lt;p&gt;
  177. &lt;font size="2"&gt;precise location (GPS and network-based) &lt;/font&gt;&lt;/p&gt;
  178. &lt;/li&gt;
  179. &lt;/ul&gt;
  180. &lt;/td&gt;
  181. &lt;/tr&gt;
  182. &lt;tr valign="TOP"&gt;
  183. &lt;td style="width: 335px;"&gt;
  184. &lt;p&gt;
  185. &lt;font size="2"&gt;SMS &lt;/font&gt;&lt;/p&gt;
  186. &lt;ul&gt;
  187. &lt;li&gt;
  188. &lt;p&gt;
  189. &lt;font size="2"&gt;read your text messages (SMS or MMS) &lt;/font&gt;&lt;/p&gt;
  190. &lt;/li&gt;
  191. &lt;/ul&gt;
  192. &lt;/td&gt;
  193. &lt;td style="width: 342px;"&gt;
  194. &lt;p&gt;
  195. &lt;font size="2"&gt;SMS &lt;/font&gt;&lt;/p&gt;
  196. &lt;ul&gt;
  197. &lt;li&gt;
  198. &lt;p style="margin-bottom: 0in"&gt;
  199. &lt;font size="2"&gt;&lt;b&gt;edit your text messages (SMS or MMS)&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  200. &lt;/li&gt;
  201. &lt;li&gt;
  202. &lt;p style="margin-bottom: 0in"&gt;
  203. &lt;font size="2"&gt;&lt;b&gt;receive text messages (SMS)&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  204. &lt;/li&gt;
  205. &lt;li&gt;
  206. &lt;p style="margin-bottom: 0in"&gt;
  207. &lt;font size="2"&gt;read your text messages (SMS or MMS)&lt;/font&gt;&lt;/p&gt;
  208. &lt;/li&gt;
  209. &lt;li&gt;
  210. &lt;p style="margin-bottom: 0in"&gt;
  211. &lt;font size="2"&gt;&lt;b&gt;send SMS messages&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  212. &lt;/li&gt;
  213. &lt;li&gt;
  214. &lt;p&gt;
  215. &lt;font size="2"&gt;&lt;b&gt;receive text messages (MMS)&lt;/b&gt; &lt;/font&gt;&lt;/p&gt;
  216. &lt;/li&gt;
  217. &lt;/ul&gt;
  218. &lt;/td&gt;
  219. &lt;/tr&gt;
  220. &lt;tr valign="TOP"&gt;
  221. &lt;td style="width: 335px;"&gt;
  222. &lt;p&gt;
  223. &lt;font size="2"&gt;Phone &lt;/font&gt;&lt;/p&gt;
  224. &lt;ul&gt;
  225. &lt;li&gt;
  226. &lt;p style="margin-bottom: 0in"&gt;
  227. &lt;font size="2"&gt;&lt;b&gt;write call log&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  228. &lt;/li&gt;
  229. &lt;li&gt;
  230. &lt;p style="margin-bottom: 0in"&gt;
  231. &lt;font size="2"&gt;directly call phone numbers&lt;/font&gt;&lt;/p&gt;
  232. &lt;/li&gt;
  233. &lt;li&gt;
  234. &lt;p&gt;
  235. &lt;font size="2"&gt;read call log &lt;/font&gt;&lt;/p&gt;
  236. &lt;/li&gt;
  237. &lt;/ul&gt;
  238. &lt;/td&gt;
  239. &lt;td style="width: 342px;"&gt;
  240. &lt;p&gt;
  241. &lt;font size="2"&gt;Phone &lt;/font&gt;&lt;/p&gt;
  242. &lt;ul&gt;
  243. &lt;li&gt;
  244. &lt;p style="margin-bottom: 0in"&gt;
  245. &lt;font size="2"&gt;directly call phone numbers&lt;/font&gt;&lt;/p&gt;
  246. &lt;/li&gt;
  247. &lt;li&gt;
  248. &lt;p&gt;
  249. &lt;font size="2"&gt;read call log &lt;/font&gt;&lt;/p&gt;
  250. &lt;/li&gt;
  251. &lt;/ul&gt;
  252. &lt;/td&gt;
  253. &lt;/tr&gt;
  254. &lt;tr valign="TOP"&gt;
  255. &lt;td style="width: 335px;"&gt;
  256. &lt;p&gt;
  257. &lt;font size="2"&gt;Photos/Media/Files &lt;/font&gt;&lt;/p&gt;
  258. &lt;ul&gt;
  259. &lt;li&gt;
  260. &lt;p style="margin-bottom: 0in"&gt;
  261. &lt;font size="2"&gt;test access to protected storage&lt;/font&gt;&lt;/p&gt;
  262. &lt;/li&gt;
  263. &lt;li&gt;
  264. &lt;p&gt;
  265. &lt;font size="2"&gt;modify or delete the contents of your USB storage &lt;/font&gt;&lt;/p&gt;
  266. &lt;/li&gt;
  267. &lt;/ul&gt;
  268. &lt;/td&gt;
  269. &lt;td style="width: 342px;"&gt;
  270. &lt;p&gt;
  271. &lt;font size="2"&gt;Photos/Media/Files &lt;/font&gt;&lt;/p&gt;
  272. &lt;ul&gt;
  273. &lt;li&gt;
  274. &lt;p style="margin-bottom: 0in"&gt;
  275. &lt;font size="2"&gt;test access to protected storage&lt;/font&gt;&lt;/p&gt;
  276. &lt;/li&gt;
  277. &lt;li&gt;
  278. &lt;p&gt;
  279. &lt;font size="2"&gt;modify or delete the contents of your USB storage &lt;/font&gt;&lt;/p&gt;
  280. &lt;/li&gt;
  281. &lt;/ul&gt;
  282. &lt;/td&gt;
  283. &lt;/tr&gt;
  284. &lt;tr valign="TOP"&gt;
  285. &lt;td style="width: 335px;"&gt;
  286. &lt;p&gt;
  287. &lt;font size="2"&gt;Camera/Microphone &lt;/font&gt;&lt;/p&gt;
  288. &lt;ul&gt;
  289. &lt;li&gt;
  290. &lt;p style="margin-bottom: 0in"&gt;
  291. &lt;font size="2"&gt;take pictures and videos&lt;/font&gt;&lt;/p&gt;
  292. &lt;/li&gt;
  293. &lt;li&gt;
  294. &lt;p&gt;
  295. &lt;font size="2"&gt;record audio &lt;/font&gt;&lt;/p&gt;
  296. &lt;/li&gt;
  297. &lt;/ul&gt;
  298. &lt;/td&gt;
  299. &lt;td style="width: 342px;"&gt;
  300. &lt;p&gt;
  301. &lt;font size="2"&gt;Camera/Microphone &lt;/font&gt;&lt;/p&gt;
  302. &lt;ul&gt;
  303. &lt;li&gt;
  304. &lt;p style="margin-bottom: 0in"&gt;
  305. &lt;font size="2"&gt;take pictures and videos&lt;/font&gt;&lt;/p&gt;
  306. &lt;/li&gt;
  307. &lt;li&gt;
  308. &lt;p&gt;
  309. &lt;font size="2"&gt;record audio &lt;/font&gt;&lt;/p&gt;
  310. &lt;/li&gt;
  311. &lt;/ul&gt;
  312. &lt;/td&gt;
  313. &lt;/tr&gt;
  314. &lt;tr valign="TOP"&gt;
  315. &lt;td style="width: 335px;"&gt;
  316. &lt;p&gt;
  317. &lt;font size="2"&gt;Wi-Fi connection information &lt;/font&gt;&lt;/p&gt;
  318. &lt;ul&gt;
  319. &lt;li&gt;
  320. &lt;p&gt;
  321. &lt;font size="2"&gt;view Wi-Fi connections &lt;/font&gt;&lt;/p&gt;
  322. &lt;/li&gt;
  323. &lt;/ul&gt;
  324. &lt;/td&gt;
  325. &lt;td style="width: 342px;"&gt;
  326. &lt;p&gt;
  327. &lt;font size="2"&gt;Wi-Fi connection information &lt;/font&gt;&lt;/p&gt;
  328. &lt;ul&gt;
  329. &lt;li&gt;
  330. &lt;p&gt;
  331. &lt;font size="2"&gt;view Wi-Fi connections &lt;/font&gt;&lt;/p&gt;
  332. &lt;/li&gt;
  333. &lt;/ul&gt;
  334. &lt;/td&gt;
  335. &lt;/tr&gt;
  336. &lt;tr valign="TOP"&gt;
  337. &lt;td style="width: 335px;"&gt;
  338. &lt;p&gt;
  339. &lt;font size="2"&gt;Device ID &amp;amp; call information &lt;/font&gt;&lt;/p&gt;
  340. &lt;ul&gt;
  341. &lt;li&gt;
  342. &lt;p&gt;
  343. &lt;font size="2"&gt;read phone status and identity &lt;/font&gt;&lt;/p&gt;
  344. &lt;/li&gt;
  345. &lt;/ul&gt;
  346. &lt;/td&gt;
  347. &lt;td style="width: 342px;"&gt;
  348. &lt;p&gt;
  349. &lt;font size="2"&gt;Device ID &amp;amp; call information &lt;/font&gt;&lt;/p&gt;
  350. &lt;ul&gt;
  351. &lt;li&gt;
  352. &lt;p&gt;
  353. &lt;font size="2"&gt;read phone status and identity &lt;/font&gt;&lt;/p&gt;
  354. &lt;/li&gt;
  355. &lt;/ul&gt;
  356. &lt;/td&gt;
  357. &lt;/tr&gt;
  358. &lt;tr valign="TOP"&gt;
  359. &lt;td style="width: 335px;"&gt;
  360. &lt;p&gt;
  361. &lt;font size="2"&gt;Other &lt;/font&gt;&lt;/p&gt;
  362. &lt;ul&gt;
  363. &lt;li&gt;
  364. &lt;p style="margin-bottom: 0in"&gt;
  365. &lt;font size="2"&gt;receive data from Internet&lt;/font&gt;&lt;/p&gt;
  366. &lt;/li&gt;
  367. &lt;li&gt;
  368. &lt;p style="margin-bottom: 0in"&gt;
  369. &lt;font size="2"&gt;download files without notification&lt;/font&gt;&lt;/p&gt;
  370. &lt;/li&gt;
  371. &lt;li&gt;
  372. &lt;p style="margin-bottom: 0in"&gt;
  373. &lt;font size="2"&gt;&lt;b&gt;adjust your wallpaper size&lt;/b&gt; &lt;/font&gt;&lt;/p&gt;
  374. &lt;/li&gt;
  375. &lt;li&gt;
  376. &lt;p style="margin-bottom: 0in"&gt;
  377. &lt;font size="2"&gt;&lt;b&gt;create accounts and set passwords&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  378. &lt;/li&gt;
  379. &lt;li&gt;
  380. &lt;p style="margin-bottom: 0in"&gt;
  381. &lt;font size="2"&gt;run at startup&lt;/font&gt;&lt;/p&gt;
  382. &lt;/li&gt;
  383. &lt;li&gt;
  384. &lt;p style="margin-bottom: 0in"&gt;
  385. &lt;font size="2"&gt;prevent device from sleeping&lt;/font&gt;&lt;/p&gt;
  386. &lt;/li&gt;
  387. &lt;li&gt;
  388. &lt;p style="margin-bottom: 0in"&gt;
  389. &lt;font size="2"&gt;view network connections&lt;/font&gt;&lt;/p&gt;
  390. &lt;/li&gt;
  391. &lt;li&gt;
  392. &lt;p style="margin-bottom: 0in"&gt;
  393. &lt;font size="2"&gt;install shortcuts&lt;/font&gt;&lt;/p&gt;
  394. &lt;/li&gt;
  395. &lt;li&gt;
  396. &lt;p style="margin-bottom: 0in"&gt;
  397. &lt;font size="2"&gt;change your audio settings&lt;/font&gt;&lt;/p&gt;
  398. &lt;/li&gt;
  399. &lt;li&gt;
  400. &lt;p style="margin-bottom: 0in"&gt;
  401. &lt;font size="2"&gt;read Google service configuration&lt;/font&gt;&lt;/p&gt;
  402. &lt;/li&gt;
  403. &lt;li&gt;
  404. &lt;p style="margin-bottom: 0in"&gt;
  405. &lt;font size="2"&gt;&lt;b&gt;toggle sync on and off&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  406. &lt;/li&gt;
  407. &lt;li&gt;
  408. &lt;p style="margin-bottom: 0in"&gt;
  409. &lt;font size="2"&gt;draw over other apps&lt;/font&gt;&lt;/p&gt;
  410. &lt;/li&gt;
  411. &lt;li&gt;
  412. &lt;p style="margin-bottom: 0in"&gt;
  413. &lt;font size="2"&gt;&lt;b&gt;expand/collapse status bar&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  414. &lt;/li&gt;
  415. &lt;li&gt;
  416. &lt;p style="margin-bottom: 0in"&gt;
  417. &lt;font size="2"&gt;full network access&lt;/font&gt;&lt;/p&gt;
  418. &lt;/li&gt;
  419. &lt;li&gt;
  420. &lt;p style="margin-bottom: 0in"&gt;
  421. &lt;font size="2"&gt;change network connectivity&lt;/font&gt;&lt;/p&gt;
  422. &lt;/li&gt;
  423. &lt;li&gt;
  424. &lt;p style="margin-bottom: 0in"&gt;
  425. &lt;font size="2"&gt;&lt;b&gt;set wallpaper&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  426. &lt;/li&gt;
  427. &lt;li&gt;
  428. &lt;p style="margin-bottom: 0in"&gt;
  429. &lt;font size="2"&gt;&lt;b&gt;send sticky broadcast&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  430. &lt;/li&gt;
  431. &lt;li&gt;
  432. &lt;p style="margin-bottom: 0in"&gt;
  433. &lt;font size="2"&gt;&lt;b&gt;read battery statistics&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  434. &lt;/li&gt;
  435. &lt;li&gt;
  436. &lt;p style="margin-bottom: 0in"&gt;
  437. &lt;font size="2"&gt;&lt;b&gt;reorder running apps&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  438. &lt;/li&gt;
  439. &lt;li&gt;
  440. &lt;p style="margin-bottom: 0in"&gt;
  441. &lt;font size="2"&gt;&lt;b&gt;connect and disconnect from Wi-Fi&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
  442. &lt;/li&gt;
  443. &lt;li&gt;
  444. &lt;p style="margin-bottom: 0in"&gt;
  445. &lt;font size="2"&gt;read sync settings&lt;/font&gt;&lt;/p&gt;
  446. &lt;/li&gt;
  447. &lt;li&gt;
  448. &lt;p&gt;
  449. &lt;font size="2"&gt;control vibration&lt;/font&gt;&lt;/p&gt;
  450. &lt;/li&gt;
  451. &lt;/ul&gt;
  452. &lt;/td&gt;
  453. &lt;td style="width: 342px;"&gt;
  454. &lt;p&gt;
  455. &lt;font size="2"&gt;Other &lt;/font&gt;&lt;/p&gt;
  456. &lt;ul&gt;
  457. &lt;li&gt;
  458. &lt;p style="margin-bottom: 0in"&gt;
  459. &lt;font size="2"&gt;receive data from Internet&lt;/font&gt;&lt;/p&gt;
  460. &lt;/li&gt;
  461. &lt;li&gt;
  462. &lt;p style="margin-bottom: 0in"&gt;
  463. &lt;font size="2"&gt;download files without notification &lt;/font&gt;&lt;/p&gt;
  464. &lt;/li&gt;
  465. &lt;li&gt;
  466. &lt;p style="margin-bottom: 0in"&gt;
  467. &lt;font size="2"&gt;run at startup&lt;/font&gt;&lt;/p&gt;
  468. &lt;/li&gt;
  469. &lt;li&gt;
  470. &lt;p style="margin-bottom: 0in"&gt;
  471. &lt;font size="2"&gt;prevent device from sleeping&lt;/font&gt;&lt;/p&gt;
  472. &lt;/li&gt;
  473. &lt;li&gt;
  474. &lt;p style="margin-bottom: 0in"&gt;
  475. &lt;font size="2"&gt;view network connections&lt;/font&gt;&lt;/p&gt;
  476. &lt;/li&gt;
  477. &lt;li&gt;
  478. &lt;p style="margin-bottom: 0in"&gt;
  479. &lt;font size="2"&gt;install shortcuts&lt;/font&gt;&lt;/p&gt;
  480. &lt;/li&gt;
  481. &lt;li&gt;
  482. &lt;p style="margin-bottom: 0in"&gt;
  483. &lt;font size="2"&gt;change your audio settings&lt;/font&gt;&lt;/p&gt;
  484. &lt;/li&gt;
  485. &lt;li&gt;
  486. &lt;p style="margin-bottom: 0in"&gt;
  487. &lt;font size="2"&gt;read Google service configuration&lt;/font&gt;&lt;/p&gt;
  488. &lt;/li&gt;
  489. &lt;li&gt;
  490. &lt;p style="margin-bottom: 0in"&gt;
  491. &lt;font size="2"&gt;draw over other apps&lt;/font&gt;&lt;/p&gt;
  492. &lt;/li&gt;
  493. &lt;li&gt;
  494. &lt;p style="margin-bottom: 0in"&gt;
  495. &lt;font size="2"&gt;full network access&lt;/font&gt;&lt;/p&gt;
  496. &lt;/li&gt;
  497. &lt;li&gt;
  498. &lt;p style="margin-bottom: 0in"&gt;
  499. &lt;font size="2"&gt;read sync settings&lt;/font&gt;&lt;/p&gt;
  500. &lt;/li&gt;
  501. &lt;li&gt;
  502. &lt;p style="margin-bottom: 0in"&gt;
  503. &lt;font size="2"&gt;control vibration&lt;/font&gt;&lt;/p&gt;
  504. &lt;/li&gt;
  505. &lt;li&gt;
  506. &lt;p&gt;
  507. &lt;font size="2"&gt;change network connectivity&lt;/font&gt;&lt;/p&gt;
  508. &lt;/li&gt;
  509. &lt;/ul&gt;
  510. &lt;/td&gt;
  511. &lt;/tr&gt;
  512. &lt;/tbody&gt;
  513. &lt;/table&gt;
  514. &lt;p dir="ltr"&gt;
  515. &amp;nbsp;&lt;/p&gt;
  516. &lt;p dir="ltr"&gt;
  517. &amp;nbsp;&lt;/p&gt;
  518. &lt;p dir="ltr"&gt;
  519. &amp;nbsp;&lt;/p&gt;</content:encoded>
  520.    </item>
  521.    <item>
  522.      <title>Just what is this Mail.Next thing?</title>
  523.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/mailnext?lang=en_us</link>
  524.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  525.      <guid isPermaLink="false">urn:uuid:3f24f537-6c17-d1f2-1d99-d3fbd1fdc563</guid>
  526.      <pubDate>Wed, 05 Feb 2014 08:41:36 -0500</pubDate>
  527.      <description>Simply put (and as it was put to me at Connect 14), it&amp;#39;s a J2EE application that talks to iNotes. As you may know, today there is a component available in IBM Connections (since 4.0) called Connections Mail. This is a fairly simple interface in Connections...</description>
  528.      <content:encoded>&lt;p dir="ltr"&gt;
  529. Simply put (and as it was put to me at Connect 14), it&amp;#39;s a J2EE application that talks to iNotes.&lt;/p&gt;
  530. &lt;p dir="ltr"&gt;
  531. As you may know, today there is a component available in IBM Connections (since 4.0) called Connections Mail. This is a fairly simple interface in Connections that surfaces your mail and calendar. How is this implemented? It&amp;#39;s a J2EE application that talks to iNotes. Here&amp;#39;s what you get with that today:&lt;/p&gt;
  532. &lt;p dir="ltr"&gt;
  533. &amp;nbsp;&lt;/p&gt;
  534. &lt;p dir="ltr"&gt;
  535. &lt;a href="https://www.socialbizug.org/blogs/lotusnut/resource/BLOGS_UPLOADED_IMAGES/ScreenShot2014-02-05at8.26.08AM.png" style="width: 100%; display: inline-block;" target="_blank"&gt;&lt;img alt="image" src="https://www.socialbizug.org/blogs/lotusnut/resource/BLOGS_UPLOADED_IMAGES/ScreenShot2014-02-05at8.26.08AM.png" style="  display:block; margin: 0 auto;text-align: center;"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;
  536. &lt;p dir="ltr"&gt;
  537. &amp;nbsp;&lt;/p&gt;
  538. &lt;p dir="ltr"&gt;
  539. When IBM releases Mail.Next, it was demoed as looking like this:&lt;/p&gt;
  540. &lt;p dir="ltr"&gt;
  541. &amp;nbsp;&lt;/p&gt;
  542. &lt;p dir="ltr"&gt;
  543. &lt;a href="https://www.socialbizug.org/blogs/lotusnut/resource/BLOGS_UPLOADED_IMAGES/ScreenShot2014-02-05at8.28.25AM.png" style="width: 100%; display: inline-block;" target="_blank"&gt;&lt;img alt="image" src="https://www.socialbizug.org/blogs/lotusnut/resource/BLOGS_UPLOADED_IMAGES/ScreenShot2014-02-05at8.28.25AM.png" style="  display:block; margin: 0 auto;text-align: center;"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;
  544. &lt;p dir="ltr"&gt;
  545. &amp;nbsp;&lt;/p&gt;
  546. &lt;p dir="ltr"&gt;
  547. Obviously, it&amp;#39;s a much more complex application, but it&amp;#39;s still just a Websphere-based frontend to Domino iNotes.&lt;/p&gt;
  548. &lt;p dir="ltr"&gt;
  549. What does this change for existing customers who are not currently planning on an IBM Connections deployment? Again, to be brief, it changes nothing. It&amp;#39;s my understanding that you can still just use Notes and iNotes if you would like. They may receive some type of facelift, but it&amp;#39;s still going to be business as usual if you wish to remain a Notes user.&lt;/p&gt;
  550. &lt;p dir="ltr"&gt;
  551. I hope that clears some things up for everyone. It is arguable that IBM could have provided a little more clarity in the Connect 2014 OGS, but the fact remains that IBM is dedicated to Domino as their strategic mail platform.&lt;/p&gt;
  552. &lt;p dir="ltr"&gt;
  553. If you want to move forward, though, you will want to start learning Websphere. ;)&lt;/p&gt;</content:encoded>
  554.    </item>
  555.    <item>
  556.      <title>Re: Notes 9.0.1 and Mavericks</title>
  557.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/re_notes_9_0_1_and_mavericks?lang=en_us</link>
  558.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  559.      <guid isPermaLink="false">urn:uuid:510ec5a0-9f97-f904-27d2-e68d92b32fad</guid>
  560.      <pubDate>Wed, 18 Dec 2013 13:46:15 -0500</pubDate>
  561.      <description>In response to: Notes 9.0.1 and Mavericks As a response to my previous post on this topic, IBM has release/updated a technote on Notes support for Mac OS X 10.9 (aka Mavericks).
  562. &amp;nbsp; One line that made me laugh was this: &amp;nbsp; "This early testing was...</description>
  563.      <content:encoded>&lt;p&gt;In response to: &lt;a href="https://www.socialbizug.org/blogs/lotusnut/entry/901mavericks"&gt;Notes 9.0.1 and Mavericks&lt;/a&gt;&lt;/p&gt;As a response to my previous post on this topic, IBM has &lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21655004"&gt;release/updated&lt;/a&gt;
  564. a technote on Notes support for Mac OS X 10.9 (aka Mavericks).
  565. &lt;div&gt;&amp;nbsp;&lt;/div&gt;
  566. One line that made me laugh was this: &lt;div&gt;&amp;nbsp;&lt;/div&gt;
  567. "This early testing was &lt;b&gt;fruitful&lt;/b&gt; and Apple was able to make
  568. code changes that benefited compatibility with Notes." &lt;div&gt;&amp;nbsp;&lt;/div&gt;
  569. There are some good fixes noted as being addressed in 9.0.1, but
  570. none of them appear to address the upgrade issue above that I (and
  571. others) have run into.</content:encoded>
  572.    </item>
  573.    <item>
  574.      <title>Speaking At IBM Connect 2014</title>
  575.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/speaking_at_ibm_connect_2014?lang=en_us</link>
  576.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  577.      <guid isPermaLink="false">urn:uuid:61b2b878-0724-8fa4-2778-ae39451cc6ee</guid>
  578.      <pubDate>Thu, 12 Dec 2013 11:10:56 -0500</pubDate>
  579.      <description>I&amp;#39;m extremely excited to be presenting (again) with Mitch&amp;nbsp;Cohen at IBM Connect 2014. We are looking forward to having another fun-filled TV show-themed session this year. In the Show &amp;#39;n Tell track again this year, our session title is How to...</description>
  580.      <content:encoded>&lt;p dir="ltr"&gt;
  581. I&amp;#39;m extremely excited to be presenting (again) with &lt;a href="http://www.curiousmitch.com/" target="_blank"&gt;Mitch&amp;nbsp;Cohen&lt;/a&gt; at IBM Connect 2014. We are looking forward to having another fun-filled TV show-themed session this year.&lt;/p&gt;
  582. &lt;p dir="ltr"&gt;
  583. In the Show &amp;#39;n Tell track again this year, our session title is How to Create a Perfect Profile: A Hitchiker&amp;#39;s Guide to A Smarter Workforce. Here is the abstract:&lt;/p&gt;
  584. &lt;blockquote dir="ltr"&gt;
  585. &lt;p&gt;
  586. Profiles are the centerpiece of IBM Connections and your social business. IBM Connections ships with scripts to connect to your LDAP Directory. However, most organizations also need to integrate HR data to build complete profiles and reporting structure. In this session we&amp;#39;ll teach you step-by-step how to add custom fields to your profiles configuration, and how to populate data from multiple sources including LDAP and HR systems.&lt;/p&gt;
  587. &lt;/blockquote&gt;
  588. &lt;p dir="ltr"&gt;
  589. You can also find more information about all of the sessions at the &lt;a href="https://www-950.ibm.com/events/tools/ibmc/ibmcems/sessionPreview.jsp" target="_blank"&gt;IBM&amp;nbsp;Connect&amp;nbsp;2014&amp;nbsp;Session&amp;nbsp;Preview&amp;nbsp;Tool&lt;/a&gt;.&lt;/p&gt;
  590. &lt;p dir="ltr"&gt;
  591. Bonus poll question: Who thinks Mitch and I should present in bow ties?&lt;/p&gt;</content:encoded>
  592.    </item>
  593.    <item>
  594.      <title>Because Everyone Has 16 cores lying around</title>
  595.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/because_everyone_has_16_cores_lying_around?lang=en_us</link>
  596.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  597.      <guid isPermaLink="false">urn:uuid:6a9cd09a-217c-c739-4754-deae9c90b3e8</guid>
  598.      <pubDate>Tue, 26 Nov 2013 09:07:33 -0500</pubDate>
  599.      <description>As I was checking in on the Sametime forum today, I saw that the new Sametime 9.0 MCU requires&amp;nbsp;quite&amp;nbsp;a&amp;nbsp;load&amp;nbsp;of&amp;nbsp;hardware . If you follow through to the Sametime&amp;nbsp;Wiki&amp;nbsp;Article&amp;nbsp;regarding&amp;nbsp;the&amp;nbsp;A/V&amp;nbsp;Deployment ,...</description>
  600.      <content:encoded>&lt;p dir="ltr"&gt;
  601. As I was checking in on the Sametime forum today, I saw that the new Sametime 9.0 MCU &lt;a href="http://www-10.lotus.com/ldd/stforum.nsf/DateAllFlatweb/ff2f1a69c8ce2ce785257c2e0075c482?OpenDocument" target="_blank"&gt;requires&amp;nbsp;quite&amp;nbsp;a&amp;nbsp;load&amp;nbsp;of&amp;nbsp;hardware&lt;/a&gt;. If you follow through to the &lt;a href="http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?lookupName=Administering+Sametime+9.0+documentation#action=openDocument&amp;amp;res_title=Audio_and_video_deployment_plans_st9&amp;amp;content=pdcontent" target="_blank"&gt;Sametime&amp;nbsp;Wiki&amp;nbsp;Article&amp;nbsp;regarding&amp;nbsp;the&amp;nbsp;A/V&amp;nbsp;Deployment&lt;/a&gt;, you&amp;#39;ll see the following gem:&lt;/p&gt;
  602. &lt;blockquote dir="ltr"&gt;
  603. &lt;p&gt;
  604. The Video Manager and the Video MCU each must be on its own computer. Best practice calls for 16 core, 16 GB for each computer.&lt;/p&gt;
  605. &lt;/blockquote&gt;
  606. &lt;p dir="ltr"&gt;
  607. Yes, that&amp;#39;s 16 cores for each server. Lest we think this is just a recommendation, we may want to reconsider this. As the post at the forum stated, &amp;quot;If the MCU has less then 16 CPUs it complains about insufficient resources.&amp;quot; If you&amp;#39;re wanting to deploy A/V with Sametime 9.0, you may want to call your preferred hardware vendor.&lt;/p&gt;</content:encoded>
  608.    </item>
  609.    <item>
  610.      <title>Notes 9.0.1 and Mavericks</title>
  611.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/901mavericks?lang=en_us</link>
  612.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  613.      <guid isPermaLink="false">urn:uuid:684d2481-60ff-b988-946f-68eb9f56562a</guid>
  614.      <pubDate>Tue, 05 Nov 2013 08:50:12 -0500</pubDate>
  615.      <description>I&amp;#39;ve been running 9.0 for a while on my Macbook Air. My only problem has been that 4 out of 5 days I have to force quit Notes at the end of the day. After upgrading to Mavericks after it was released, I was prompted to upgrade Java and things were OK....</description>
  616.      <content:encoded>&lt;p dir="ltr"&gt;
  617. I&amp;#39;ve been running 9.0 for a while on my Macbook Air. My only problem has been that 4 out of 5 days I have to force quit Notes at the end of the day. After upgrading to Mavericks after it was released, I was prompted to upgrade Java and things were OK.&lt;/p&gt;
  618. &lt;p dir="ltr"&gt;
  619. Then, 9.0.1 was released and I tried upgrading. Nothing happened after launching Notes, and I couldn&amp;#39;t see any errors in logs. I tried deleting the Expeditor folder (like Workspace folder for Windows...), but that didn&amp;#39;t help either. I decided to then just remove the Notes Application and do a reinstall. All was good after that.&lt;/p&gt;
  620. &lt;p dir="ltr"&gt;
  621. Of course, Mavericks isn&amp;#39;t supported (yet) by IBM. I expect that a hotfix may be issued to address this and full support may not come until 9.0.2. I have also seen a &lt;a href="http://www-10.lotus.com/ldd/ndseforum.nsf/xpTopicThread.xsp?documentId=842C2ABFA95FAB8585257C18007E4B99" target="_blank"&gt;similar&amp;nbsp;report&amp;nbsp;here&lt;/a&gt;. Oh, and I do still have to force quit Notes...&lt;/p&gt;</content:encoded>
  622.    </item>
  623.    <item>
  624.      <title>My Next Tablet?</title>
  625.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/my_next_tablet?lang=en_us</link>
  626.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  627.      <guid isPermaLink="false">urn:uuid:1348a250-23b4-1a98-7d32-fb4317341999</guid>
  628.      <pubDate>Fri, 01 Nov 2013 14:30:55 -0400</pubDate>
  629.      <description>Up until hearing recently that Apple now makes the iPad Air, I had talked myself into upgrading my Acer A500 10.1&amp;quot; tablet to either an iPad Mini or something like a Nexus 7. Basically, I had decided that I would be fine with the smaller form factor for my...</description>
  630.      <content:encoded>&lt;p dir="ltr"&gt;
  631. Up until hearing recently that Apple now makes the iPad Air, I had talked myself into upgrading my Acer A500 10.1&amp;quot; tablet to either an iPad Mini or something like a Nexus 7. Basically, I had decided that I would be fine with the smaller form factor for my use cases (Kindle app and news/rss reading, social networking, note taking, not much gaming, etc...). Here was a great review I saw of the &lt;a href="http://www.geek.com/apple/tiny-tablet-titans-nexus-7-2013-vs-ipad-mini-with-retina-display-1574746/" target="_blank"&gt;iPad&amp;nbsp;Mini&amp;nbsp;vs.&amp;nbsp;Nexus&amp;nbsp;7&lt;/a&gt;. I&amp;#39;m a Mac guy, but I do kind of like the Android tablet. I really like SwiftKey as well. C&amp;#39;mon Apple... &lt;img alt="Wink" height="18" src="https://www.socialbizug.org/connections/resources/web/com.ibm.oneui.ckeditor/editor/plugins/sametimeemoticons/images/EmoticonWink.gif" title="Wink" width="18"&gt;&lt;/img&gt; But Words With Friends is atrocious on Android, IMHO! lol&lt;/p&gt;
  632. &lt;p dir="ltr"&gt;
  633. Has that now changed with the iPad Air? The larger screen would be nice - especially in a form factor that isn&amp;#39;t &lt;strong&gt;that&lt;/strong&gt; much bigger.&lt;/p&gt;
  634. &lt;p dir="ltr"&gt;
  635. Thoughts? I think I&amp;#39;m actually leaning towards the new iPad Mini with Retina Display, but I&amp;#39;m kind of open.&lt;/p&gt;</content:encoded>
  636.    </item>
  637.    <item>
  638.      <title>Some Mail and User Migration Tips</title>
  639.      <link>https://www.socialbizug.org/blogs/lotusnut/entry/migrationtips?lang=en_us</link>
  640.      <source url="https://www.socialbizug.org/blogs/lotusnut?lang=en_us">Lotus Nut</source>
  641.      <guid isPermaLink="false">urn:uuid:d79c7f47-3f75-c97e-f3c2-61f0d47ca80e</guid>
  642.      <pubDate>Thu, 29 Aug 2013 09:49:42 -0400</pubDate>
  643.      <description>Over the course of the years, I have been involved with many IBM Domino mail consolidation/migration projects. This could be in the form of an acquisition, data center consolidation, moving users to hosted servers, etc&amp;hellip; I would like to share a few of...</description>
  644.      <content:encoded>&lt;p dir="ltr"&gt;
  645. Over the course of the years, I have been involved with many IBM Domino mail consolidation/migration projects. This could be in the form of an acquisition, data center consolidation, moving users to hosted servers, etc&amp;hellip; I would like to share a few of the &amp;quot;little&amp;quot; things that I&amp;#39;ve learned or implemented that help these projects succeed. These are just some tips and the list is, of course, not an all-inclusive outline of steps.&lt;br&gt;
  646. &lt;br&gt;
  647. It should go without being said that many of these projects will have certain prerequisites. I don&amp;#39;t want to go into details about those things. They would include ensuring general network connectivity, establishing connection documents, cross-certification, storage planning, template versioning, etc&amp;hellip; But let us proceed with some of the gotchas - preparing you for walls into which you may run!&lt;br&gt;
  648. &lt;br&gt;
  649. &lt;strong&gt;A. Getting the data over!&lt;/strong&gt;&lt;br&gt;
  650. &lt;br&gt;
  651. While there are certainly different methods for getting the mail databases moved to other servers, more often than not you may choose to use the Domino Administrator Client&amp;#39;s File tab to create a replica on another server. Even when I&amp;#39;ve used the native options for moving mail users to another system, I would tend to replicate the databases ahead of time. If this is the route you&amp;#39;re going to choose, this means that the AdminP process will be involved and this means you&amp;#39;ll need to keep some things in mind. First of all, the originating servers will need to have create replica rights on the target servers - so make sure that you check this out in the Server Documents first. Secondly, you may need to set up inbound and outbound cross-domain AdminP to allow for these requests. This is really very simple, but make sure that you copy the server documents listed in the cross-domain documents from each domain into the other. If not, you&amp;#39;ll likely get some really strange errors or if you&amp;#39;re lucky Domino will tell you the server can&amp;#39;t be found in the Directory. Oh, and ensure that proper settings are in place so that the new databases are created at the proper ODS level (including making sure DAOS is enabled and as databases are replicated they should transfer faster once DAOS has begun population).&lt;br&gt;
  652. &lt;br&gt;
  653. &lt;strong&gt;B. What about accessing those mail databases?&lt;/strong&gt;&lt;br&gt;
  654. &lt;br&gt;
  655. You&amp;#39;re probably thinking I left out something vital above, right? Yes you will also need to make sure that the servers involved can access the databases for replication. You need to determine what your strategy will be. Do you want LocalDomainServers to have Manager access in the ACL? Sometimes this is OK. Other times it may not be. But just ACL access may not be good enough! Some other things to consider:&lt;br&gt;
  656. &lt;br&gt;
  657. - The servers will need to have deletion rights.&lt;br&gt;
  658. - The target server will likely become the home/administration server for the mail db. You may need to ensure ahead of time that the correct value is already set (so that future name changes/AdminP tasks will work).&lt;br&gt;
  659. - Is replication disabled on any of the databases?&lt;br&gt;
  660. &lt;br&gt;
  661. &lt;strong&gt;C. Why are all of my emails unread on the new server?&lt;/strong&gt;&lt;br&gt;
  662. &lt;br&gt;
  663. Yes, this has historically been a big issue. But there are several things you can to to mitigate problems from this:&lt;br&gt;
  664. &lt;br&gt;
  665. - Ensure that the advanced database property is set to replicate unread marks with all servers (hint, &lt;a href="http://www.bleedyellow.com/blogs/lotusnut/entry/easy_way_to_manage_acl_or_advanced_properties_for_a_folder_sntt11" target="_blank"&gt;you&amp;nbsp;can&amp;nbsp;set&amp;nbsp;this&amp;nbsp;for&amp;nbsp;all&amp;nbsp;databases&amp;nbsp;in&amp;nbsp;a&amp;nbsp;folder&amp;nbsp;in&amp;nbsp;the&amp;nbsp;Administrator&amp;nbsp;Client&lt;/a&gt;)&lt;br&gt;
  666. - If your servers are 6.5.6, 7.0.3, or 8.0 and later, set &lt;a href="http://cwhisonant.blogspot.com/2007/12/domino-8-101-unread-marks-enhancements.html" target="_blank"&gt;ADMINP_EXCHANGE_ALL_UNREAD_MARKS&lt;/a&gt;=1&lt;br&gt;
  667. - Do you know about using &lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21093302" target="_blank"&gt;REPLICATOR_SYNC_UNREAD&lt;/a&gt;=-1 on the Notes Client to sync the unread marks on each replication?&lt;/p&gt;
  668. &lt;p dir="ltr"&gt;
  669. Even if you do ensure the things above, you may still run into unread marks issues.&lt;br&gt;
  670. &lt;br&gt;
  671. &lt;strong&gt;D. What else could go wrong?&lt;/strong&gt;&lt;br&gt;
  672. &lt;br&gt;
  673. One answer to that question is &amp;quot;it depends on how you&amp;#39;ve planned this out ahead of time.&amp;quot; Take the time at the outset of the project to look over all of your settings. Hopefully some of what I&amp;#39;ve mentioned above will spark some other ideas on items you may miss.&lt;br&gt;
  674. &lt;br&gt;
  675. Feel free to comment here or email me if you have any questions!&lt;/p&gt;</content:encoded>
  676.    </item>
  677.  </channel>
  678. </rss>
  679.  

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//feed.informer.com/digests/AYKA2HVQUK/feeder.rss

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