Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Goodbye, Fleets

blog.twitter.com

Post reply on HN
Print view View original

191–200 of 306 posts

Re: Goodbye, Fleets

#191

Post by dfabulich »

Gaelan wrote: post #171
jasonwatkinspdx wrote: post #147

Earlier quoted context omitted.

The glaring omission is a time limited typo edit window. Just ducking ship it already.

I wonder if there are technical issues here? It wouldn't be too surprising if "tweets are immutable" (and therefore safe to aggressively cache) is an assumption baked into a lot of their code.

It's not just technical. Jack doesn't want it. https://www.wired.com/story/jack-dorsey-wont-get-edit-tweet-...

> Dorsey was unusually direct: “The answer is no,” he says.

> “The reason there's no edit button [and] there hasn't been an edit button traditionally is we started as an SMS text messaging service," explains Dorsey. "So as you all know, when you send a text, you can’t really take it back. We wanted to preserve that vibe and that feeling in the early days.”

Re: Goodbye, Fleets

#192

Post by afavour »

kyrofa wrote: post #169
chmod775 wrote: post #164

Earlier quoted context omitted.

I would think that a big problem here is to only allow correcting typos, not changing meaning of a tweet - which would suck for a public, fast-paced platform like twitter. This isn't as simple as counting the number of changed characters, especially when you have to consider at least dozens, better hundreds, of languages. But then again you can already cram about ten times as much meaning into a single tweet if you w…

> I would think that a big problem here is to only allow correcting typos, not changing meaning of a tweet - which would suck for a public, fast-paced platform like twitter. I feel like GitHub already solved that problem by showing an edit history on comments. Twitter could do the same thing. Even easier: don't actually publish tweets for 60 seconds, during which time they can be edited.

Facebook already has similar edit functionality and I’m curious how many users click through to see the edits. I’ll be the number is not high.

The speed Twitter moves I think a lot more people are going to mash the retweet button than the “see edits” button.

Re: Goodbye, Fleets

#193

Post by sg47 »

jasonwatkinspdx wrote: post #147
ChrisArchitect wrote: post #65

Earlier quoted context omitted.

Yeah I actually really respect that they axed something within a timely span, posted about their thoughts, and well, lately the Twitter team has been killing it as far as deploying features and long talked about stuff, so it's all good. The idea of Fleets, whether it was inspired by Stories etc, was another way to engage users and it did have some usefulness. I love the 24hr disappearing thing on IG and I liked it si…

The glaring omission is a time limited typo edit window. Just ducking ship it already.

Wondering if you can implement it as a redirect. Instead of editing the original, the tweet redirects to the modified version but the original still shows up as a quote tweet or as a reply (with all replies to the original tweet under that reply)

Re: Goodbye, Fleets

#194

Post by px43 »

mdoms wrote: post #56
thallavajhula wrote: post #5

Twitter is great when it comes to transparency. I love how they included this >Although we built Fleets to address some of the anxieties that hold people back from Tweeting, Fleets are mostly used by people who are already Tweeting to amplify their own Tweets and talk directly with others. We’ll explore more ways to address what holds people back from participating on Twitter. And for the people who already are Tweet…

Perhaps people are anxious about tweeting because a single tweet can ruin your life?

Please point to one person whose life was ruined from a single tweet, and who didn't deserve it.

Yes, it exposes unapologetic racists and misogynists. That's a good thing. People who genuinely learn from their fuckups are generally called out, but their lives are hardly "ruined".

Re: Goodbye, Fleets

#195

Post by xeromal »

kyrofa wrote: post #169
chmod775 wrote: post #164

Earlier quoted context omitted.

I would think that a big problem here is to only allow correcting typos, not changing meaning of a tweet - which would suck for a public, fast-paced platform like twitter. This isn't as simple as counting the number of changed characters, especially when you have to consider at least dozens, better hundreds, of languages. But then again you can already cram about ten times as much meaning into a single tweet if you w…

> I would think that a big problem here is to only allow correcting typos, not changing meaning of a tweet - which would suck for a public, fast-paced platform like twitter. I feel like GitHub already solved that problem by showing an edit history on comments. Twitter could do the same thing. Even easier: don't actually publish tweets for 60 seconds, during which time they can be edited.

No one would actually look at that though. You need to cater to the masses or make it exceedingly obvious

Re: Goodbye, Fleets

#196

Post by pjc50 »

whywhywhywhy wrote: post #31

The lack of innovation at Twitter, Instagram and Facebook is utterly baffling and points to a serious culture problem. Feels there are rooms of people now just being paid to clone successful features from other apps and only after those apps have carved their place in the market, literally become followers rather than trailblazers. In just a few years Instagram is going to seem completely old hat to anyone who didn't…

Someone had a "history of MUD sites" in which they describe a two year lifecycle of popularity. I think the same applies to social media on about ten years; there's a cohort of people who join in the first few years, because the site creates a different community that isn't served elsewhere. Then it reaches saturation, slow decay, drama, and gradually exodus to the hotter new things.

Hence all the desperate cloning of new platform features.

Re: Goodbye, Fleets

#197

Post by notatoad »

jasonwatkinspdx wrote: post #147
ChrisArchitect wrote: post #65

Earlier quoted context omitted.

Yeah I actually really respect that they axed something within a timely span, posted about their thoughts, and well, lately the Twitter team has been killing it as far as deploying features and long talked about stuff, so it's all good. The idea of Fleets, whether it was inspired by Stories etc, was another way to engage users and it did have some usefulness. I love the 24hr disappearing thing on IG and I liked it si…

The glaring omission is a time limited typo edit window. Just ducking ship it already.

They did, like a month ago. You gotta pay for it though...

https://ibb.co/S6WNLvt

Re: Goodbye, Fleets

#198

Post by user-the-name »

dfabulich wrote: post #191
Gaelan wrote: post #171

Earlier quoted context omitted.

I wonder if there are technical issues here? It wouldn't be too surprising if "tweets are immutable" (and therefore safe to aggressively cache) is an assumption baked into a lot of their code.

It's not just technical. Jack doesn't want it. https://www.wired.com/story/jack-dorsey-wont-get-edit-tweet-... > Dorsey was unusually direct: “The answer is no,” he says. > “The reason there's no edit button [and] there hasn't been an edit button traditionally is we started as an SMS text messaging service," explains Dorsey. "So as you all know, when you send a text, you can’t really take it back. We wanted to preser…

Jack really is just a blithering idiot. There are plenty of reasons you could give for not adding this feature, but that one, that's probably the worst.

Re: Goodbye, Fleets

#199

Post by isiahl »

afavour wrote: post #192
kyrofa wrote: post #169

Earlier quoted context omitted.

> I would think that a big problem here is to only allow correcting typos, not changing meaning of a tweet - which would suck for a public, fast-paced platform like twitter. I feel like GitHub already solved that problem by showing an edit history on comments. Twitter could do the same thing. Even easier: don't actually publish tweets for 60 seconds, during which time they can be edited.

Facebook already has similar edit functionality and I’m curious how many users click through to see the edits. I’ll be the number is not high. The speed Twitter moves I think a lot more people are going to mash the retweet button than the “see edits” button.

Facebooks edit history is also hidden in grey text next to the timestamp. I bet putting a "This tweet has been edited" notice actually inline with the content would be effective.

Re: Goodbye, Fleets

#200

Post by kyrofa »

zerocrates wrote: post #173
kyrofa wrote: post #169

Earlier quoted context omitted.

> I would think that a big problem here is to only allow correcting typos, not changing meaning of a tweet - which would suck for a public, fast-paced platform like twitter. I feel like GitHub already solved that problem by showing an edit history on comments. Twitter could do the same thing. Even easier: don't actually publish tweets for 60 seconds, during which time they can be edited.

Having a time where it's not actually posted would work fine but probably not be super effective: after all, you already have an unlimited amount of time to look at the message sitting on your screen before you actually send it. It's just often very hard to read your own writing for typos. Still it would be a step forward. You could even make it opt-in.

Haha, I swear every time I wish I could edit a tweet it's within 5 minutes after I post it. To be fair, at least with my incredibly limited followers, that's soon enough I can just delete it and post it again without losing too much engagement, but still. I'm just not patient enough to proof-read properly, apparently.
Post reply on HN