From Newsgroup: uk.rec.waterways

<div>So I use bold text in certain parts of my messages like *bold text* (which translates to bold text) and it works perfectly fine in desktop version of Facebook and also on messenger.com but strangely the android messenger app can't display the text between the asterisks in bold, instead, it just prints out *bold text*</div><div></div><div></div><div>If you don't want to install another app, there's a way around it. Although not elegant, you can tell Chrome to "Request desktop site" from the device's menu button. Have to manually change the URL from m.facebook.com to www.facebook.com afterwards, and the site is, as expected, large and unwieldy. But it works.</div><div></div><div></div><div></div><div></div><div></div><div>facebook messenger apk for android 4.4.2 free download</div><div></div><div>Download Zip: https://t.co/XUivaLnxoB </div><div></div><div></div><div>Just realized I was responding to the duplicate question, but here's another solution: Use Adblock Browser. It's a free browser that disables a lot of ads, and even though some mobile sites might act strange (which is why I still use Chrome), it stops facebook from opening up the Play Store. Hope that helps.</div><div></div><div></div><div>To achieve this level of granular control you want you will struggle on the Meraki for the reasons previously outlined. You would need a firewall that supports HTTPS inspection, which basically decrypts the traffic to be able to differentiate between facebook messenger and regular Facebook.</div><div></div><div></div><div>I have an interesting scenario which I cant seem to find a solution to. I am hoping the community will be able to point me in the right direction. I need to block facebook messenger on a wifi network. To be more specific I need to block the facebook messenger (android & apple) application while mobile devices are on our wireless network. I have successfully blocked facebook web chat in the browser, but mobile devices on our wifi are still able access messenger. I dont want to block HTTPS completely, as many services utilize HTTPS. I dont want to block the entire facebook.com either since there is a need to use facebook. </div><div></div><div></div><div></div><div></div><div>Does anyone know what port the facebook messenger (android & apple) app uses to communicate? I read facebook implemented MQTT which uses 1883 and 8883 for SSL communications. However blocking these ports has had no impact. Maybe the app has hard coded IP addresses which it uses to avoid using DNS. If so, using DNS filters (i.e. OpenDNS) would not work. I would appreciate any insight anybody has regarding this matter. Thank you.</div><div></div><div></div><div></div><div></div><div>They might be using MQTT without using the standard ports. I found a post that mentions FB Messenger for Windows using ports 62656, 62859 and 63965, but it's a couple of years old, and might not apply to ios or android either. </div><div></div><div></div><div></div><div></div><div>To be honest I dont know which one of these blocks accomplished my goal, but as of now when you log into facebook the chat window at the bottom shows "disconnected". This is a win in my book. Navigating the site has not presented any problems thus far. </div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div><div>The facebook messenger app however has not been effected. I would like to thank Chris75 for his recommendation. I have enabled Instant Messaging on my OpenDNS and I will test to see if this resolves my problem. I have to admit there is VERY little information regarding how the facebook apps operate. Short of utilizing a major UTM appliance (i.e. Watchguard) I was stumped. Blocking HTTPS works, but in this scenario I need to excise the disease not cut off the limb.</div><div></div><div></div><div>For those of you whom are curious I have some additional information regarding this topic. First let me address the last question. By blocking the domains I mentioned the apps were unaffected. Blocking the domains I mentioned only prevented users from using facebook chat in their browsers. Upon initial login to facebook it looks like you are connected to chat, but then a few seconds later it shows you disconnected. Works great.</div><div></div><div></div><div>I blocked both immediately. As I mentioned in my first post, Facebook is using the MQTT protocol for messenger. In addition I have found that blocking these two domains works as well to block the messenger app:</div><div></div><div></div><div></div><div></div><div>The trade off is that apps that need to connect to Facebook will be unable to connect as well. Now let me be clear, by blocking these two domains you will not effect the Facebook app. This will block the facebook messenger app. If you want to make sure the facebook app has no problems you can whitelist graph.facebook.com.</div><div></div><div></div><div>With all the media attention on Facebook's messenger app and the suggestions that it can access the data and camera functions on the Android and iPhone smartphones, it is time to consider the wisdom of apps having unrestricted access to our lives.</div><div></div><div> df19127ead</div>
--- Synchronet 3.21d-Linux NewsLink 1.2