• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • Lol, the audacity to post objectively and verifiably false information, then when you’re informed that it’s false not acknowledge that fact and deflect to some completely meaningless point about the holocaust, then when you’re informed that that point makes no sense you deflect to a random meme and attach the opinion of some other guy.

    You don’t actually care about ‘reality’ like your meme implies. If you did you’d care to actually look at the judgement (like I did before commenting, took me five seconds to find and two minutes to speed parse) before deciding what you wanted the judgement to say to selectively suit your own emotional reality.




  • Creating a paid or ad-supported client app for a website isn’t profiting off of content, it’s profiting off of the user’s desire for a better mobile experience. There’s no ‘stealing’, the developer never has access to nor purports to own any of the content themselves- it’s simply a voluntary intermediary for a user to access their own account with their own content feed.

    That said, any client apps that run ads are dumb and will fail miserably. It’s awful for UX. Just so long as client apps can be monetized in other ways I think it’s fine to adopt a license that prohibits specifically ads.


  • Because as it’s currently designed Apple is not handling any of the actual transactions- those are handled by the Payment Service Provider that the merchant is required to provide to be granted Apple’s permission to use the API.

    If Apple opened it up to non-Merchants (who don’t come with their own PSP), then Apple would have to act as the PSP which is a much larger headache that they don’t want to deal with.



  • I think you’re fundamentally misunderstanding how data is handled in federated systems. When an account from Threads interacts with your post or you interact with a Threads post, information is exchanged exclusively through Actions sent between the servers- never to or from your or their client and another server. It looks like this:

    Client <=API=> Instance <=Action=> Instance <=API=> Client

    They don’t get any information that isn’t already available publicly to any random user on your instance- no IP address or anything otherwise. Threads’ mobile app data collection has no bearing on their ability to collect information on you.

    Edit: To be clear- there is theoretically a set of protocols in the ActivityPub spec that allows for direct client to server communication (unimaginatively called ActivityPub Client-to-Server), but it hasn’t been adopted by any current Fediverse software implementation that I’m aware of.






  • They could already get all of your profile and post info… I could get that right now through the free api for every account on this and every other thread with a couple dozen lines of code.

    Edit: I’m also unclear on how they would ever get your IP- if you never use their frontends the only IP they’d have access to is that of the server your account is hosted on… Which would only be your own IP for the extreme minority who host their own instance from their personal internet connection, and Meta wouldn’t be able to tell that that’s the case anyway.