Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.beaware.live/users/BeAware/statuses/112321761311000997">BeAware (beaware@social.beaware.live)'s status on Wednesday, 24-Apr-2024 02:41:31 JST</a><a href="https://social.beaware.live/@BeAware" title="beaware@social.beaware.live"><img src="https://gnusocial.jp/avatar/142396-48-20240112152236.webp" width="48" height="48" alt="BeAware" style="position: absolute; left: 0; top: 0;">BeAware</a><div><a href="https://noc.social/@AAKL/112321679252414916" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/87123" title="david@boles.xyz">David Boles</a></li></ul></div></section><article><p><a href="https://noc.social/@AAKL">@AAKL</a> <a href="https://boles.xyz/@david">@david</a> either that, or SERIOUSLY bad PR....however. I did have some of these concerns quelled by the CEO of a completely different company. 🤦♂️ </p><p>Mike McCue, CEO of Flipboard, had a talk with me yesterday about how it might be a data law issue. Like GDPR, there are a few different data laws around the world that companies have to deal with that are a legal nightmare.</p><p>Meta isn't operating Threads in the EU right now for this very reason, however, they are still operating in California which has CCPA. here's a link to that discussion. <a href="https://flipboard.social/@mike/112317517766956422" rel="nofollow noreferrer">https://flipboard.social/@mike/112317517766956422</a></p><p>I'm still not dealing with Meta after their interaction because why didn't they just answer like Mike? Seems like a pretty simple, straight forward answer that I can understand completely.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2971953#notice-5924634">In conversation</a><time datetime="2024-04-24T02:41:31+09:00" title="Wednesday, 24-Apr-2024 02:41:31 JST">Wednesday, 24-Apr-2024 02:41:31 JST</time> <span>from <span><a href="https://social.beaware.live/@BeAware/112321761311000997" rel="external" title="Sent from social.beaware.live via ActivityPub">social.beaware.live</a></span></span><a href="https://social.beaware.live/@BeAware/112321761311000997">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://flipboard.social/@mike/112317517766956422I">Mike McCue (@mike@flipboard.social)</a></h5><div> from <span>Mike McCue</span></div></header><div>@BeAware@social.beaware.live  You're right about the EU. But there's a maze of other privacy regulations to navigate. For example in California there's CCPA. Plus there's still a lot of legal ground to map out with posts being propagated and copied across a decentralized set of servers around the world. It's the kind of thing that drives legal departments crazy. It takes a certain amount of courage/commitment to ship a product in this environment given the potential for liability. I need to learn more about Authorized Fetch to say how much of a solution this is or isn't.Side thread: as far as I can tell regulations like GDPR and CCPA have had limited value to consumers while being incredibly costly to implement for smaller publishers and making the whole web experience painful with yet more popups. These well intentioned regulations are making the big guys who can afford to do all this stuff stronger while making the small guys weaker and at greater risk. Ugh.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
BeAware (beaware@social.beaware.live)'s status on Wednesday, 24-Apr-2024 02:41:31 JSTBeAware
in reply to
- Aida Akl
- David Boles
@AAKL @david either that, or SERIOUSLY bad PR....however. I did have some of these concerns quelled by the CEO of a completely different company. 🤦♂️
Mike McCue, CEO of Flipboard, had a talk with me yesterday about how it might be a data law issue. Like GDPR, there are a few different data laws around the world that companies have to deal with that are a legal nightmare.
Meta isn't operating Threads in the EU right now for this very reason, however, they are still operating in California which has CCPA. here's a link to that discussion. https://flipboard.social/@mike/112317517766956422
I'm still not dealing with Meta after their interaction because why didn't they just answer like Mike? Seems like a pretty simple, straight forward answer that I can understand completely.
In conversationWednesday, 24-Apr-2024 02:41:31 JST from social.beaware.livepermalink
Attachments
1. No result found on File_thumbnail lookup.
  Mike McCue (@mike@flipboard.social)
  from Mike McCue
  @BeAware@social.beaware.live You're right about the EU. But there's a maze of other privacy regulations to navigate. For example in California there's CCPA. Plus there's still a lot of legal ground to map out with posts being propagated and copied across a decentralized set of servers around the world. It's the kind of thing that drives legal departments crazy. It takes a certain amount of courage/commitment to ship a product in this environment given the potential for liability. I need to learn more about Authorized Fetch to say how much of a solution this is or isn't. Side thread: as far as I can tell regulations like GDPR and CCPA have had limited value to consumers while being incredibly costly to implement for smaller publishers and making the whole web experience painful with yet more popups. These well intentioned regulations are making the big guys who can afford to do all this stuff stronger while making the small guys weaker and at greater risk. Ugh.

Public

Embed Notice

HTML Code

Corresponding Notice