He also pointed out the language used when one clicks on the blue check, which says the user is subscribed to Twitter Blue and not that they paid for Twitter Blue. "Despite the implication when you click the blue badge that has mysteriously re-appeared beside my name, I am not paying for the 'honour,'" actor Ian McKellen tweeted.Īttorney Todd Friedman, however, said it might not necessarily be a surefire case from a consumer protection angle.įriedman, whose firm focuses on consumer rights, compared Musk's actions to those of a manager at a store giving freebies to his friends. Many celebs are disgruntled at the appearance that they would pay for the formerly coveted verification mark that now has become a lightning rod for Musk politics. In an email, Twitter responded to a request for comment with an autoreply of a poop emoji. The FTC did not respond to a request for comment. Section 5 of the Federal Trade Commission Act prohibits "unfair or deceptive acts or practices in or affecting commerce," and the Lanham Act, which establishes trademark law, also include a false advertising clause that could apply in this scenario, Davisson said. "It's pretty clear that they understand the value of star power and they have chosen to re-institute Twitter Blue for those users because they think it will sort of lend additional legitimacy to the product," Davisson said. "If you are trying to attain revenue by marketing a premium service on your social media platform, and you indicate that lots of famous celebrities and influencers with large follower accounts have paid for that product," Davisson said, "that would be a misrepresentation about the product or service."īy giving out free subscriptions, Musk is essentially trying to induce people to sign up using celebrity endorsements. This could violate federal law, said John Davisson, director of litigation and senior counsel at the Electronic Privacy Information Center. Musk confirmed in a tweet that he was personally paying for the blue checks of William Shatner, LeBron James and King. Many of those users did not pay for Twitter Blue, however, and were gifted the blue check by Musk. Musk allowed users to keep their legacy verified check marks until a mass purge April 20.Īccounts that remained had a blue check mark which, when clicked, said the following: "This account is verified because they are subscribed to Twitter Blue and verified their phone number." Twitter's previous verification system, launched in 2009, was intended to prevent impersonations of high-profile accounts such as those of celebrities and politicians. When Tesla founder and billionaire Musk bought the social media giant for $44 billion last year, he quickly launched the Twitter Blue subscription service that would grant users a blue check mark among other features such as editing tweets, fewer ads and longer tweets. Reich's check mark has since been removed. "If I don't want a blue check but Elon gives me one anyway, indicating I've paid and endorsed his gonzo system when I haven't, isn't this fraud under the FTC Act?" tweeted former Labor Secretary Robert Reich on Sunday. Federal Trade Commission regulations surrounding consumer protection and false advertising. (which is written in python, btw)Īnyway, the Tribler sourcecode comes from <=2012, when it was probably less than a proof of concept focusing on the primary goal of the project.Public figures including author Stephen King and Lakers star LeBron James have tweeted about not being willing to pay the $8-a-month subscription Musk implemented for the blue check mark, yet it remains on their profiles.īeyond angering celebs, however, Musk's move could be flouting U.S. In fact, they could probably benefit from looking at Transmission as example of a workable rpc/api. Tribler should make a better api and ditch the current one entirely. To name something, it uses an array with values instead of a object with key-value pairs.īasically it isn’t a full api but rather a backend for the webui and generally ‘not-fun’ to program an api client against. In addition, uTorrent has an api that goes against json best practices. We didn’t implement support for those older versions because those version do not easily expose the fields we require. Sonarr rejects the api based on advertised version, not even sure if it’s actually reporting that old uTorrent version… Definitely used an old version as template. I briefly looked in the Tribler git repository, yes it looks like they modeled the api after uTorrent, but the source code on github goes back to 2012 before which it was svn.
0 Comments
Leave a Reply. |