Stories with Tag SMS

• Apple will soon support encrypted RCS messaging with Android users

  permalink

  Posted: 2025-03-14 12:07:06

  Verbose tl;dr

  Apple is reportedly planning to add support for encrypted Rich Communication Services (RCS) messaging between iPhones and Android devices. This means messages, photos, and videos sent between the two platforms will be end-to-end encrypted, providing significantly more privacy and security than the current SMS/MMS system. While no official timeline has been given, the implementation appears to be dependent on Google updating its Messages app to support encryption for group chats. This move would finally bring a modern, secure messaging experience to cross-platform communication, replacing the outdated SMS standard.

  In a significant development for cross-platform communication, Apple appears poised to finally address a long-standing grievance among Android users: the lack of seamless, secure messaging between iPhones and Android devices. The Verge reports that Apple is actively working to incorporate support for Rich Communication Services (RCS) messaging with end-to-end encryption (E2EE), potentially bridging the gap between the iMessage ecosystem and the Android world. This means that messages exchanged between iPhones and Android devices will be protected by robust encryption, preventing third-party interception and ensuring privacy for users on both platforms.

  Currently, messages sent between iPhones and Android phones rely on the antiquated SMS/MMS standard, which lacks modern features such as read receipts, high-quality image and video sharing, and, most importantly, end-to-end encryption. This has led to a fragmented and often frustrating user experience, particularly for Android users who are often subject to the "green bubble" stigma and experience diminished message quality. The implementation of RCS with E2EE by Apple would effectively modernize cross-platform communication, offering a comparable experience to iMessage conversations, complete with enhanced features and the crucial security of encryption. This would represent a substantial improvement over the existing system, alleviating the technical limitations and social implications associated with the current cross-platform messaging disparity.

  While Apple has not officially announced a timeline for this implementation, the reporting suggests it's a matter of "when," not "if." This move, if realized, could dramatically reshape the landscape of mobile messaging, providing a unified and secure communication platform for users regardless of their operating system. It signifies a potential shift in Apple's strategy, which has previously been perceived as leveraging iMessage's exclusivity as a competitive advantage. By embracing RCS with E2EE, Apple could foster a more interoperable messaging ecosystem, benefiting users across the mobile landscape.

  • Apple
  • Android
  • RCS
  • Messaging
  • Encryption
  • iMessage
  • SMS
  • End-to-End Encryption
  • iOS
  • Google
  • Mobile communication
  • Technology
  • privacy
  • Security

  Summary of Comments ( 15 )
  https://news.ycombinator.com/item?id=43361822

  Verbose tl;dr

  Hacker News commenters generally expressed skepticism about Apple's purported move towards supporting encrypted RCS messaging. Several doubted Apple's sincerity, suggesting it's a PR move to deflect criticism about iMessage lock-in, rather than a genuine commitment to interoperability. Some pointed out that Apple benefits from the "green bubble" effect, which pressures users to stay within the Apple ecosystem. Others questioned the technical details of Apple's implementation, highlighting the complexities of key management and potential vulnerabilities. A few commenters welcomed the move, though with reservations, hoping it's a genuine step toward better cross-platform messaging. Overall, the sentiment leaned towards cautious pessimism, with many anticipating further "Apple-style" limitations and caveats in their RCS implementation.

  The Hacker News post titled "Apple will soon support encrypted RCS messaging with Android users" generated a significant number of comments discussing various aspects of the news. Several commenters expressed skepticism about Apple's motivations, suggesting that they might be driven more by regulatory pressure, particularly in the EU, than a genuine desire to improve interoperability. Some pointed to Apple's business model, arguing that iMessage lock-in is a key factor in maintaining their ecosystem and that true interoperability could threaten that.

  A recurring theme in the discussion revolves around the technical details and potential limitations of Apple's implementation. Commenters debated whether Apple would fully embrace the RCS standard or implement a limited version that maintains some advantages for iMessage users. Concerns were raised about features like read receipts and typing indicators, and whether these would function seamlessly across platforms. The potential for Apple to utilize its own servers for relaying messages, rather than relying on Google's Jibe platform, was also discussed, along with the implications for privacy and security.

  Several comments highlighted the complexities of implementing end-to-end encryption (E2EE) in a cross-platform messaging system. Some users expressed concerns about the potential vulnerabilities and challenges of maintaining security across different operating systems and devices.

  Another thread of discussion focused on the broader implications of this change for the messaging landscape. Some commenters speculated on how this might affect other messaging platforms like WhatsApp and Signal, and whether it could lead to greater interoperability across the industry.

  Some users shared personal anecdotes about the frustrations of the current messaging situation between iOS and Android, expressing hope that this change would improve communication and eliminate the "green bubble" stigma. Others, however, remained pessimistic, believing that Apple would find ways to maintain the advantages of iMessage and prevent true parity with Android messaging.

  Finally, several comments delved into the history of messaging standards and the role of various companies in shaping the current landscape. Some blamed carriers for their resistance to adopting open standards, while others criticized Apple for their perceived reluctance to embrace interoperability.

• Show HN: Trolling SMS spammers with Ollama

  permalink

  Posted: 2025-01-22 19:23:48

  Verbose tl;dr

  The author created a system using the open-source large language model, Ollama, to automatically respond to SMS spam messages. Instead of simply blocking the spam, the system engages the spammers in extended, nonsensical, and often humorous conversations generated by the LLM, wasting their time and resources. The goal is to make SMS spam less profitable by increasing the cost of sending messages, ultimately discouraging spammers. The author details the setup process, which involves running Ollama locally, forwarding SMS messages to a server, and using a Python script to interface with the LLM and send replies.

  Evan Widloski has developed a system to automatically engage and playfully frustrate SMS spammers using a large language model (LLM) named Ollama, hosted locally on his machine. He describes his motivation stemming from annoyance with frequent spam text messages and a desire to waste the spammers' time and resources, potentially discouraging their operations.

  His technical implementation involves forwarding incoming spam SMS messages to a Python script. This script utilizes the Twilio API to identify the originating phone number. This number is then checked against a blocklist to prevent responses to legitimate messages. If the number is not blocked, the script formats the received spam message and feeds it into the Ollama LLM. The LLM is prompted to generate a nonsensical or absurd reply, designed to keep the spammer engaged in a pointless conversation.

  Widloski details specific prompting strategies to guide the LLM's responses, such as instructing it to impersonate a confused persona, ask irrelevant questions, or fabricate outlandish scenarios. The generated response is then sent back to the spammer via the Twilio API.

  He highlights the cost-effectiveness of running the LLM locally, minimizing expenses associated with cloud-based LLM services. Furthermore, he showcases examples of successful interactions with spammers, illustrating how the LLM-generated responses effectively lead the spammers on, often through multiple exchanges. Widloski also acknowledges potential drawbacks and ethical considerations, such as the possibility of the LLM inadvertently revealing personal information or generating offensive content. He emphasizes that his project is a personal experiment and stresses the importance of responsible use of LLMs. The post concludes with a reflection on the effectiveness of the approach and future possibilities, including refining the prompting strategy and incorporating more advanced language models.

  • SMS
  • Spam
  • Trolling
  • Ollama
  • LLM
  • Large Language Model
  • AI
  • artificial intelligence
  • Chatbot
  • Humor
  • Software
  • Project
  • HN
  • Hacker News
  • Show HN

  Summary of Comments ( 21 )
  https://news.ycombinator.com/item?id=42796496

  Verbose tl;dr

  HN users generally praised the project for its creativity and humor. Several commenters shared their own experiences with SMS spam, expressing frustration and a desire for effective countermeasures. Some discussed the ethical implications of engaging with spammers, even with an LLM, and the potential for abuse or unintended consequences. Technical discussion centered around the cost-effectiveness of running such a system, with some suggesting optimizations or alternative approaches like using a less resource-intensive LLM. Others expressed interest in expanding the project to handle different types of spam or integrating it with existing spam-filtering tools. A few users also pointed out potential legal issues, like violating telephone consumer protection laws, depending on the nature of the responses generated by the LLM.

  The Hacker News post titled "Show HN: Trolling SMS spammers with Ollama" generated a moderate amount of discussion, with a handful of commenters engaging with the original poster's project of using a local large language model (LLM) to engage with and frustrate SMS spammers.

  Several commenters expressed amusement and appreciation for the project's concept. One user praised the creative use of an LLM for this purpose, finding the idea of tying up spammers' resources with a bot entertaining and potentially helpful in reducing their effectiveness. Another commenter expressed a similar sentiment, enjoying the "trolling" aspect and appreciating the potential for wasting spammers' time and money.

  A couple of users raised practical questions and concerns. One individual inquired about the cost-effectiveness of running the LLM locally for this purpose, wondering if the expense of compute resources would outweigh the benefits. Another commenter raised a point about potential legal implications or risks associated with engaging with spammers, though no specific legal issues were identified.

  The original poster actively engaged with the comments, responding to questions and clarifying certain aspects of the project. They addressed the cost concern by explaining their utilization of a relatively small and efficient LLM, and also noted that the compute costs were currently negligible for their usage pattern.

  While there wasn't extensive debate or deeply analytical discussion, the comments generally reflected positive interest in the project, with users finding the idea clever and potentially useful. The main points of conversation revolved around the amusement factor, the practicality and cost of the approach, and potential risks involved. The lack of a large number of comments suggests that while the project intrigued some users, it didn't spark widespread or highly controversial discussion.