@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!
@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
@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
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)
That being said, ML-generated alt text should be available in the API now! Just verified on my end. Your feedback is heard :) We've always exposed user-provided alt text but that's not always provided.
Let me know if you have any theories on why this URL can't be rendered.
@BeAware@atomicpoet@fediversenews Sorry I meant "other mastodon clients" as in the "other clients that I have access to that are Mastodon." Totally get that there are a variety of popular platforms and we actually use `_misskey_quote` as our quote post URI field :)
"Photo by Jo on April 05, 2024. May be a Twitter screenshot of 2 people and text that says 'Jo @JoJoFromJerz … Donald Trump was the president when the entire planet was hit with a once in a lifetime historic pandemic. But, ok. Marjorie Taylor Greene... @mtgreenee Follow God is sending America strong signs to tell us to repent. Earthquakes and eclipses and many more things to come. pray that our country listens.'."
This might be a problem with the local client? We're certainly sending down a valid CDN url as the attachment, and it renders just fine in other Mastodon clients (screenshot here is from my local server).
The CDN url is hosted on cdninstagram.com so I would check if you have any local blocklists in your browser that might affect that.