• 0 Posts
  • 58 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle








  • Their CEO is the biggest symptom of their problem. She demands a sky high compensation despite her poor leadership. The company has been in a spiraling decline for the past decade now. Instead of focusing on bringing a great user experience, they alienated their most staunch users with things like Pocket and allowed PWAs and Electron to eat their lunch.








  • At my company we have already used it to great length. We had a backlog on several thousand support tickets we wanted categorized. GPT-4 did it in about 8 hours and with over 80% accuracy, at a fraction of the cost (and higher quality) it would have taken to get humans to do it.

    We’re rolling out a chat bot too using it, with a local model as backup, to reply to leads when our clients are busy. So far they love it.

    We’re making our money back despite the costs, and we’re able to spend that money paying people to not do busy work.




  • No. The e2ee is a proprietary extension developed by Google. To use it and the full set of extensions, you must either use the closed Google RCS API, which at the moment only Samsung is allowed to access. Alternatively you can use Google’s current flavor of the month chat app, Messages.

    I have been very vocal that while this is a good thing, Apple for all their faults, should not be chastised for not implementing anything beyond the core of RCS. Google has been attempted to leverage RCS as a market force, and their widely publicized shaming of Apple not adopting it is at least partly in bad faith. If a telcom wants to implement RCS as Google touts it, you must also purchase and install the RCS gateways that Google can conveniently sell you for very large sums.

    https://www.xda-developers.com/google-messages-rcs-api-third-party-apps/