Talk:Multimedia Messaging Service

message: Correct me if I'm wrong but the pic being used in this entry seems completely pointless. As far as I can tell it adds nothing to the quality of the article. Might I suggest it be removed? TheNad 21:14, 14 September 2009 (UTC)
thread_title:  Pic Unnecessary 

message: I am not sure these links brings anything to the article so I removed them
* www.eigroup.com/ Empower Interactive
* www.mobispine.com/ Mobispine - A low-cost alternative to MMS
* www.shootsend.com/ Shoot&Send - A low-cost alternative to MMS
* www.celtius.com/s.asp?id=393 MMS/SMS Gateway can be used for sending and receiving MMS/SMS messages with your application through GPRS modem or direct MMSC/SMSC connection.
* www.mplix.com/ Mplix - Create and send free animated MMS messages
* www.mozat.com/en/m2u-enterprise/m2u-enterprise-overview.htm MMS Gateway Product in Singapore
* www.winwap.com/products_1_3.php MMS Stack SDK is a library for adding MMS capabilities to other software applications, for creating your own MMS solutions (testing/measuring or end-user solutions)
* www.infosoftin.com/wap - MMSC Simulator mimics the behavior of real MMSC
* www.businesms.com/ MercuryXMS is a suite of SDKs for creating, optimizing and delivering MMS via direct connections, GPRS/CDMA modems and binary connections, together with video/audio transcoding and handset detection.
Riadlem 18:12, 23 June 2006 (UTC)
replies: text: Also removed TriPlay link since it's just an ad for a site and does clearly not belong here~. Tauntz (talk) 16:24, 10 December 2008 (UTC)
replies: text: Agree with the above removals and "unlinked" them in this discussion Calltech (talk) 15:32, 19 March 2009 (UTC)
thread_title:  Commercial links 

message: This article has too little (no) technical information or specs about standards and limitations.. let's get some! 84.234.176.26 22:53, 30 March 2007 (UTC)
replies: text: Yes I think this article can be better than this, please insert some technical information, thanks --Snake co1 (talk) 10:57, 17 January 2012 (UTC)
thread_title:  Specs... 

message: could anybody please add MMS call flow from sombody who sent the MMS until MMS received by the receiver.
best regards.  —Preceding unsigned comment added by 124.81.68.100 (talk) 02:34, 24 October 2007 (UTC)
thread_title:  MMS call flow 

message: the article probably contains no more than three encyclopedic facts, is long winded, and appears to be entirely lifted off of the back of the packaging this MMS thing came in.  does really nobody who cared enough to write/copy and paste this know enough about it to write an even halfway encyclopedic entry about it?  —Preceding unsigned comment added by 208.120.85.210 (talk) 00:18, 20 May 2008 (UTC)
replies: text: I agree, the "Facts" section read like a "Did you know?" website from the 20th century, and the rest was low quality as well. 90.230.54.138 (talk) 17:51, 3 August 2008 (UTC)
thread_title:  this requires major cleanup 

message: I removed the material regarding the iPhone; it was tacked on to the end of a section and lacked relevance. It was also the only handset whose MMS capabilities were mentioned, and was overly POV ("For two years Apple refused...").  It was also simply incorrect and US-centric, since the lack of MMS was limited to AT&T, and in any case will be moot as of later this month.  --MCB (talk) 03:42, 4 September 2009 (UTC)
thread_title:  iPhone reference 

message: On my old phone MMS worked very nicely. I could view received messages perfectly and compose them easily. Now, on my admittedly older Android (version 1.6 I believe), it's a complete mess. Composing them to be displayed like I want can not be done – not in the default messaging app and not in the very popular app Go SMS Pro. My mobile phone operator company does however offer a website that I can log in to and compose an MMS like I want it to display and then send it from the website, which is of course rather inconvenient compared to sending an sms from your phone.
Receiving an MMS is equally messy. They kind of just throw the parts – text, picture and sound – at me to be viewed in "some way" I have to basically figure out myself and do manually. Not at all elegant like on my old phone (old school non-smart phone). So is this generally how it is on smart phones, that MMS is a mess? Does that, if so, mean that phone makers are not aiming at maintaining this form of communication? Maybe the article could present something about the future (or lack thereof) of MMS. --95.34.4.130 (talk) 18:39, 29 July 2012 (UTC)
thread_title:  Is MMS "dying"? 

message: PXT redirects here.  What is PXT ?  I don't know,   thats why I was looking for it in Wikipedia.   Is PXT an alternative name for MMS ?   Is PXT some sort of variant of MMS ?   Is PXT a forgotten, failed, alternative to MMS ?    I have no idea.
But it redirects here,  there must be some reason,  someone must know,   then it perhaps should be mentioned in the text of this article, somewhere.Eregli bob (talk) 23:07, 9 March 2014 (UTC)
replies: text: See http://help.vodafone.co.nz/app/answers/detail/a_id/2654/~/what-is-pxt%3F (if it still exists). It sounds like PXT and MMS are synonymous.—140.153.24.155 (talk) 12:47, 2 May 2014 (UTC)
thread_title:  PXT redirects here - why ? 

message: I do not know what the phrase "captive technology" means.
A Google search does not return any relevant results (on the first page)
The citation for the sentence mentioning "captive technology" never uses the phrase. My assumption is that an editor inferred this phrase (not realizing its ambiguity.)
Amid the other problems this article has, I propose the removal of this phrase, as it does not help convey an understanding of the topic.
Anyone disagreeing, please explain why this phrase is helpful. I will gladly do what I can to make the article more clear if I am enlightened as to the meaning of the phrase
Chasevasic (talk) 23:23, 30 January 2015 (UTC)
thread_title:  What is captive technology? 

message: Is it really HTTP or is it WSP the protocol which is used to retrieve the message? See here.  — Preceding unsigned comment added by Mitar (talk • contribs) 18:49, 22 August 2015 (UTC)
thread_title:  HTTP or WSP 

message: I notice that many of the changes I made in  are concerns that were raised months or even years ago on this talkpage. This is your friendly reminder that if you see obvious issues, or paragraphs that are confusing or unclear, please do not be afraid to be bold and make the changes yourself.   Adrian[232] 04:01, 2 February 2016 (UTC)
thread_title:  Please, [[WP:BOLD|Be Bold]] 

message: The article currently states:
* MMS does not utilize operator-maintained "data" plans to distribute multimedia content, which is only used if the operator clicks links inside the message.
This unsupported claim is both confusing and dubious.
This article should say more about SMS/MMS mode/coding issues. It seems common that use of non-text features such as Emojis automatically converts a text msg into MMS -- which can be hard for some phones to receive. A particular issue is when fancy text messages cross over the line into requiring "data" mode to send or receive.-73.61.15.80 (talk) 17:13, 13 December 2017 (UTC)
thread_title:  "data" mode