Google's Double Standard for Youtube

If you own a Windows Phone device, you are probably well aware of the drama between Google and Microsoft regarding a native Youtube app for Windows Phone.

To recap, first, everything started when Microsoft (due to Google's lack of love and support for Windows Phone) came out with its own native Youtube app which was much better than what was available via the web interface for Youtube. It had the ability to play video from Youtube in portrait mode or landscape mode (you could watch the video and view the list of comments or the list of related videos while you were in portrait mode). It also integrated with your Youtube account (so you could still access your playlists and the like) and had some extra goodies such as no ads and being able to download video to play while offline as well.

Google got word of this and claimed that some of the extra features such as the no ads and the video downloading were against its terms of service. It claimed that circumventing the ads were robbing content creators of revenue. It then asked Microsoft to make some changes to the app such as removing the video download feature and add support for Youtube's ads. Microsoft released an updated version of the Youtube app which was more in-line with Google's terms of service, but that wasn't good enough for Google.

Some time after the updated Youtube app was released, Google revoked the api key that the Youtube app was using. This broke the native app and made it useless since it could not download data from Youtube. Google then put up an a new list of requirements that Microsoft's app had to meet such as being totally in HTML5. Google makes no such requirement for the Youtube app for it's own Android operating system or for Apple's iOS operating system.

There was backlash against Google on the internet for these decisions (mostly for revoking the api key) and there still is. Microsoft was willing to make further changes to its Youtube app to meet Google's list of requirements, but one sticking point still keeps Microsoft from meeting Google's demands. Microsoft claims that it cannot (properly) implement Youtube's ads because Google has not made the api for accessing the ads available. Even now, Google still has not given Microsoft access to the Youtube ad api.

Now today, I found an article on Ars Technica saying that with the latest release of the Youtube app for Google, it is implementing features that Microsoft tried to implement and was told were against Google's terms of service. With these moves, Google has created a double standard. Anything goes for it's own Android app, but it refuses to make a proper Youtube app for Windows Phone (or let Microsoft attempt to make one itself). Google cannot continue to disregard Windows Phone users for much longer. If someone wants to make the argument of "just use the website", I will reply back that not all videos are available for playback on the mobile site. I think Google fears the potential of Windows Phone for the future, and that is why it has created a double standard.

As of now, there is a Youtube "app" in the windows phone store right now, but it is mostly a link to the mobile Youtube site. What do you think of this? Please let me know in the comment box below.

Why not try some delicious Mystic Monk Coffee while watching your favorite Youtube videos? Mystic Monk Coffee (use this link or click on the picture below to access the store and purchase) is what you really need when it comes to coffee. Trust me, it's good coffee (in most instances, much better than Starbucks coffee) and you won't regret buying some (just keep it away from your computer keyboard or laptop/tablet). If you like tea more than coffee, they also offer tea. If you have a Keurig machine, the monks also have k-cups for purchase as well (known as "monk shots") Using the link (or picture below) to buy the coffee (or tea) helps the monks out and helps me with my endeavors as well. The coffee (or tea) also makes for great gifts for friends and family as well.

Rig

GDDR2 Amber Update for Nokia Phones on AT&T Network is Finally Out

Well folks, after 15:00 e.s.t., AT&T has finally put out the GDDR2 Amber update from Nokia for the Lumia 820 and 920. All of those weeks of constantly bickering at AT&T paid off.

You can get the Update by going into the Settings and choosing "Check for Update". Nokia's update check page reflects this.

Since my Lumia 820 only has 8gb of onboard storage space, I will think I will be one of the more adventurous ones and download the new rom image (with the updates in it) and flash it for a clean install. Now if only Microsoft allowed for apps to be able to backup their program data to skydrive. It's a shame that I am going to loose all of my progress on my games if I flash the new rom image instead of getting it through "check for update" (but I guess that is the price I have to pay).

A Better Way for AT&T to handle Windows Phone Updates

Update (10-21-2013): Thanks to Microsoft,  one of the issues that I brought up has been remedied. If you are a Windows Phone developer, either through the app store or through Microsoft's online App Studio, you can download a utility from Microsoft (it's actually in the Windows Phone store) which will change the update settings in the registry (of the phone) so that the update source for os update packages is now Microsoft instead of your carrier. If you use the utility to change the update source, you can undo the change so that the update source is the carrier again, but you cannot revert to an earlier os update unless you reflash the rom for your phone (rom flashing should be done by advanced users only due to risk of bricking your phone). An important thing to note that the Microsoft utility only covers operating system updates. Any device firmware updates (this is separate from os updates) will still come through the carrier either way. An example of a device firmware update would be Nokia's amber update for its lumia phones running Windows Phone 8.

It's been 1 month and (about) 4 weeks since Microsoft put out the GDDR2 update for Windows Phone 8. Around that time, the update was pushed out to all phones running Windows Phone 8 (depending on the carrier's time) except for Nokia phones. Nokia took some extra time and added some device-specific stuff to the GDDR2 update for its phones and packaged it up as the "Amber" update. Back in September, Nokia deemed the amber update stable and delivered it out to the carriers for them to push the update to devices.

Here in the US, reception of the update by the cell carriers has varied. T-Mobile and Verizon tested and pushed out the update in a timely manner. I am not including Sprint in this since it doesn't have any phones running Windows Phone 8 (the HTC 8XT and the Samsung ATIVS Neo are listed for preorder on Sprint's web site). However, AT&T has taken quite awhile to test and push out this amber update for its Nokia phones running Windows Phone 8. As of the publishing of this blog post, AT&T has still not pushed out the update for Nokia phones. Furthermore, AT&T has been very secretive in the status of its testing of the update. Unfortunately, this is not the first time AT&T has dragged its feet and messed up the Windows Phone update progress. The time taken to test the update, along with the secrecy on progress, is making many customers with Nokia phones running Windows Phone 8 frustrated. A thread on AT&T's community message board titled "Where's The GDR2/Amber Update... Any Schedule?" certainly shows evidence of this.

As a software developer, I know that time is money. I know it's important to thoroughly test software before pushing it out to customers and that it takes some time to test. However, it's also important to be as transparent as possible to your customers regarding progress on testing. If something went wrong during testing and this means that the new software is not stable enough to push out to customers, that is understandable. If this happens, you need to be as clear as possible with your customers so that they are not kept waiting and the tempers of those customers don't flare up to where you lose a customer. I know that I am not the best at being transparent with update progress myself, but I try my best to do it.

So far, any indication of progress on the update testing has come from customers phoning AT&T customer care and asking (in some cases, almost to the point of harassing) the customer care representative they speak to where AT&T is with the update. 99% of the time, customer care either replies with something along the lines of "I don't know" or "AT&T is currently testing the update and will release the update when it is ready". However, there are a few cases where customer care reps have actually given some kind of indication of progress. The last one I know of is that AT&T found a problem with the update back in September and asked Nokia to fix it, pushing back the release date to some time in October of this year.

If AT&T wishes to keep faith in its customers, I have some suggestions for it. The first is if the obligation to push out an update for a device falls on the carrier's shoulders, that there be some kind of "progress page", accessible to AT&T customers (if not the general public), which details the roadmap for testing the update and the estimated release date and where we are on the roadmap. This page would also be updated with messages about (critical) problems which impact the release date update and would include a new estimated release date.

The second suggestion I have is for AT&T to start a kind-of "beta program", where customers can opt-in to get the update (from AT&T, once it gets the update from the OEM, not direct from the OEM) earlier than the offical (stable) release. Those customers that opt-in must accept a (legal) disclaimer that says that as part of this program, you will get the update earlier than everyone else, but there might still be bugs. This would enlist some extra help with testing that would allow AT&T to push out the updates in a more timely manner. This would also benefit those customers who are software developers since we would then be able have the latest update to test our own software programs with. On Windows Phone 8, the emulator suffices for most of the testing, but some things you just have to test with a real device.

Lastly, I would like to end with a call to charity in our speech. From that forum thread I referenced earlier, I see many references to others not using charity in the messages they post in the thread. Lack of charity can cause things to get out of hand. I realize that patience is wearing thin for many customers regarding the update, but when we post on the forum or call customer care, we should always speak charitable even if we are frustrated.

If you agree with me or have something else to say about AT&T's handling of the updates, please post in the comment box below. If you have a suggestion of your own that I should add to this list, please post it in the comment box below as well. Once I get enough support from you readers, I will pass this page (and comments) on to AT&T (support?) so that someone high up in the company can take notice.

While you're waiting for AT&T to finally release the amber update for Nokia phones, I would suggest that you try some delicious Mystic Monk Coffee. Mystic Monk Coffee (use this link or click on the picture below to access the store and purchase) is what you really need when it comes to coffee. Trust me, it's good coffee (in most instances, much better than Starbucks coffee) and you won't regret buying some (just keep it away from your computer keyboard or laptop/tablet). If you like tea more than coffee, they also offer tea. If you have a Keurig machine, the monks also have k-cups for purchase as well (known as "monk shots") Using the link (or picture below) to buy the coffee (or tea) helps the monks out and helps me with my endeavors as well. The coffee (or tea) also makes for great gifts for friends and family as well.

Right now, I don't have any updates for you in the way of app updates for my windows phone apps. Yes, I am working on app updates. The reason for me taking a long time between updates is that I want to do some extra testing so I can be sure that I can squash as many bugs as I can before starting a new major version of my media player app and my boy scout app and things have have been somewhat hectic for me around home. I am just about finished with a prayer app designed for (primarily) Catholics (but other Christians can use it too). If you want to go ahead and get my existing apps now (while I'm working on the updates), please use the following links:

BSA Eagle Tracker download: http://bit.ly/Mm1Upo
Mobile Media Manager (paid version) download: http://bit.ly/y3rf6V
Mobile Media Manager (free version) download: http://bit.ly/xGCsWE

Remarks on the Possiblity of the Revival of the Subdeacon within the Roman Rite

About a week ago, I read a blog post on Father Z's WDTPRS blog about subdeacons from the Eastern Rites being used for a Solemn High Mass (in the Extraordinary Form of the Roman Rite). In it, he advocates for the order of subdeacon to be brought back in the Roman Rite. I agree with him to a point, but I realize that much catechesis is needed first to accurately inform the laity.

In case you have never heard of a subdeacon before, it is one who is (literally) "under a deacon". The job of the subdeacon within the Mass is to assist the deacon and do a few other things as well such as reading the epistle. Within the course of holy orders, the subdeacon is below the order of deacon, but higher than all of the minor orders.

In 1972, Pope Paul VI released the motu proprio Ministeria Quaedam. In it, the definition of a cleric within the church was redefined (to be deacon and higher) and the minor orders (as back before Vatican II) and the subdeacon were eliminated and in their place, the minor orders of lector and acolyte were kept, but they were rebranded as "ministries" and thus open to selected laymen (and seminarians on their way to the diaconate and priesthood) to receive them. The exception to this motu proprio is certain groups out there which celebrate the Extraordinary Form exclusively, such as the Priestly Fraternity of Saint Peter (FSSP), which have been allowed to retain the subdiaconate and the minor orders. This worked out until Pope Benedict XVI put out Summorum Pontificum back in 2007, allowing universal permission for any priest within the Roman Rite to celebrate the pre-conciliar form of the Roman Rite without any special permission from his bishop first.

With Summorum Pontificum, there was a renewed interest in the different forms of Mass, including the Solemn High Mass. Unfortunately, things caught a snag in regards to the Solemn High Mass. In order to have one, you need 3 ministers: the priest (obviously), the deacon, and the subdeacon. Due to the big time difference between 1965 and 2007 any proper (ordained) subdeacon, aside from the handful of approved groups devoted to the older form of the Mass which got permission to retain all four minor orders and the subdeacon,  had moved on and received his ordination to the diaconate and priesthood. According to the liturgical guidelines, priests and deacons can dress down to the subdeacon and there is also a provision allowing someone who has received the minor order of acolyte to vest and act as a subdeacon during the Mass if a real subdeacon could not be found (with some exceptions such as not wearing the maniple and not being able to purify the sacred vessels).

Some have suggested that the order of subdeacon be revived in the Roman Rite. There are two concerns that I see that would have to be addressed. First, would the subdeacon be considered a major order as it has traditionally been or would it now be recognized as a minor order as it is with the Eastern rites? I think if the order of subdeacon were brought back in the Roman Rite, it would have to be considered a minor order since the definition of cleric was changed to start with the diaconate. However, if the order of subdeacon were changed to that of a minor order, this would affect those groups which exclusively celebrate the older form of the Mass such as the Priestly Fraternity of Saint Peter (FSSP), but I don't think things for those groups would really change.

Second, what kind of guidelines would subdeacons have to follow? In years past, once a man was ordained a subdeacon, he had to live out the promise of celibacy (if a man received the minor orders, but stopped before he was ordained a subdeacon, he could still get married with no problems). In the Roman Rite, the subdeacon was not allowed to be married. This is before Pope Paul VI brought back the permanent diaconate. For the good of the church, if the subdiaconate were to be brought back, they would follow similar guidelines to what is already established for deacons (transitory and permanent). These days, there would have to be the option of admitting married men to the subdiaconate just as married men can be admitted to the diaconate. The subdeacon who is married would still have do as a married deacon does and take a vow of celibacy.

Third, if the subdiaconate were brought back, what functions would the subdeacon have at Mass in the ordinary form? In the extraordinary form, the functions of the subdeacon are clearly documented. In the ordinary form, we only have reference to the functions of the subdeacon in as far as he was to serve the priest and deacon, read the first and second readings before the gospel, assist the priest in giving communion if needed, and then helping to purify the vessels after communion. If the subdiaconate were to be brought back, I would guess that he would be the first candidate to assume those duties before any man holding the ministries of acolyte or lector (depending on the given task).

These are just some of the issues that would have to be addressed for the subdiaconate to (officially) come back in the Roman Rite. Right now, the Eastern churches sur iuris in communion with Rome still do ordain men to the subdiaconate. At a Solemn High Mass in the Extraordinary Form, an Eastern subdeacon is allowed to fulfill the role of subdeacon within the Mass (and do everything that a real subdeacon does). Before that though, the Eastern subdeacon needs to get permission from his own bishop first, and he uses the vestments that he normally uses in his rite. If the Eastern subdeacon (upon getting his bishop's permission first) does not have his own eastern vestments available with him at the Roman Rite church that the Solemn High Mass is being celebrated at, he can wear the vestments that a Roman Rite subdeacon wears.

Lastly, the subdiaconate and the minor orders are considered sacramentals instead of sacraments. This is mostly because the subdiaconate and the minor orders were something instituted by the Church and do not have divine origins (as in the institution of the priesthood) or apostolic origins (as in the institution of the diaconate). Since the subdiaconate (and the minor orders as well) do not leave an  indelible mark on the soul, there is no need for the subdeacon to be laicised if a situation warrants a man to leave the subdiaconate.

So what do you think of this issue? Should the order of subdeacon be brought back in the Roman Rite or not? I think that it's possible, but much catechesis is needed first to accurately inform the laity. Tell me what you think in the comment box below. If I am missing some information or if I have some wrong information in this post, please let me know via the comment box below as well.

Now that you know a little more about church history, why not try some delicious Mystic Monk Coffee? Mystic Monk Coffee (use this link or click on the picture below to access the store and purchase) is what you really need when it comes to coffee. Trust me, it's good coffee (in most instances, much better than Starbucks coffee) and you won't regret buying some (just keep it away from your computer keyboard or laptop/tablet). If you like tea more than coffee, they also offer tea. If you have a Keurig machine, the monks also have k-cups for purchase as well (known as "monk shots") Using the link (or picture below) to buy the coffee (or tea) helps the monks out and helps me with my endeavors as well. The coffee (or tea) also makes for great gifts for friends and family as well.

Right now, I don't have any updates for you in the way of app updates for my windows phone apps. Yes, I am working on app updates. The reason for me taking a long time between updates is that I want to do some extra testing so I can be sure that I can squash as many bugs as I can before starting a new major version of my media player app and my boy scout app and things have have been somewhat hectic for me around home. I am just about finished with a prayer app designed for (primarily) Catholics (and other Christians can use it too).

While you're learning about recursion, why not try some delicious Mystic Monk Coffee? Mystic Monk Coffee (use this link or click on the picture below to access the store and purchase) is what you really need when it comes to coffee. Trust me, it's good coffee (in most instances, much better than Starbucks coffee) and you won't regret buying some (just keep it away from your computer keyboard or laptop/tablet). If you like tea more than coffee, they also offer tea. If you have a Keurig machine, the monks also have k-cups for purchase as well (known as "monk shots") Using the link (or picture below) to buy the coffee (or tea) helps the monks out and helps me with my endeavors as well. The coffee (or tea) also makes for great gifts for friends and family as well.

While we are waiting for updates to my windows phone apps (trust me, I'm working on them), if you want to go ahead and get my apps now, - See more at: http://www.catholictechgeek.com/2013/06/a-simplified-guide-to-recursion.html#sthash.lQ2Wq09N.dpuf