Notices by Pcottle (pcottle@cyberplace.social)

@thisismissem woah didnt know this was being tested. Hope its not something we ship globally :O

@brooks Great pics!! I can only seem so see one photo on that link but appreciate the great snapshots either way :P

@brooks great pics! And great job white balancing out all those blue lights 😅

@Gargron there was a cocktail that was blue and named after Bluesky 😅

@nunesdennis @davidimel @mmasnick @evan I think it’ll be posted later! Was recorded I believe

Hello Fediverse!

@thisismissem @theverge @the-verge-theverge @manlycoffee I don't work on Edits so can't speak for the team, but I get why sometimes companies will build power-user features into a separate space while keeping the main consumer app simple. Curious to try it when its released!

@cdevroe definitely something we want once we have bidirectional replies!

@j12t @Gargron well it's just formatted like a normal fediverse username mention right? That's how it appears to me

On mastodon sure it doesn't get 'shortened' to @gargron but I think the correct plaintext export of the post is shown below?

@troed @renchap @GossiTheDog @Gargron I'd just ask for understanding that sometimes an incremental approach is easier to work through at a large company with regulatory oversight versus doing everything at once.

Being able to go to market with our MVP and not having to worry about:
- edits being respected by a wide variety of disparate fediverse software
- users not having a chance to abort a fediverse publish

Helped significantly :)

@Gargron we're aligned on that! Really excited for bi-directional replies

@Gargron we launched our public beta on March 21st, 30 weeks ago -- not over a year :)

Since then we have:
- expanded to 100+ countries
- gone from outbound publishing + likes to having fediverse replies, media ingestion, integrity screening, profile display
- implemented transparent blocklists with appeal forms

And most important of all... haven't ruined the fediverse! Before we launched that was everyone's top worry, and I'd rather be slow and cautious (with our size) vs brazen and careless

@renchap @troed @GossiTheDog @Gargron

yep as Renaud mentioned, we made a promise to users that:
- they had five minutes to change their mind and not publish to the fediverse, via deleting their post
- no Fediverse server was capable of *not* respecting their edits, since we simply didn't federate posts until editing was done

Switching to instant publishing + edit syncs is a very different mental mode of how it works, and we'd need to disclose that (to both users and regulators)

@0xjessel whatuppppp jesseeeeeeee (lol)

@mho @pcottle@threads.net I'd jump on a call with the Irish Data Protection Commission any day to help advocate there!

@pcottle@threads.net Great work!!

@wuchyi @aulia Threads operates in a blocklist mode (aka we interop by default) except for the following cases here:
https://help.instagram.com/914046486923176/

We require signed HTTP requests though

@zak ah we require everything beyond webfinger to use HTTP signatures for signed fetches:

https://help.instagram.com/914046486923176

There are a few libraries that provide support for this 😇

@vitriolix @tchambers @snarfed.org @mike @matthias @dave @jessel We're working on it!!

@nunesdennis we're working closely with stakeholders outside of the company and hopefully will have something to share soon!