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

271–280 of 306 posts

Re: Goodbye, Fleets

#271

Post by renewiltord »

andy_ppp wrote: post #269
renewiltord wrote: post #219

Earlier quoted context omitted.

I mean, I could just as well say "Log out of your account then". That will negate the effect of the block.

Yes, it’s inconvenient though, I’m trying to be informed about what everyone thinks, even very thin skinned people who hit the block button at a tiny difference in opinion, some of their opinions are informative and helpful to me so yes as the information is in the public domain it should still be easy to access. The difference here is that my change to blocking doesn’t affect the things you’ve said one bit, how will…

My audience knows that when I tell it to kill all the Apaches, that it’s advice to kill each forked process of Apache2. The consuming madness that causes others who do not speak the language to conclude that I am calling for genocide is not something I choose to engage with.

I have a tool. It is effective. Cope with it or don’t. It’s not my problem. Having just realized this tool isn’t going away, I no longer feel the need to continue this conversation.

Re: Goodbye, Fleets

#272

Post by shruubi »

I don't use twitter, in fact, I deleted my account and created a new, blank account in case I got sent anything on Twitter. Twitter is, to me an ugly place dominated by cliques with everyone else trying to shout the loudest in the hopes of being noticed by said cliques.

I in no way feel safe or comfortable contributing to a platform that is that toxic and has a long track record of people trawling through every little thing you have ever said in the hopes of destroying your career and life.

And people who say the solution is to follow specific people or use certain ways of viewing your timeline underline the other problem which is if the platform requires me to make a significant time investment to get a non-toxic, non-awful experience, then I'd rather go without and be blissfully ignorant to anything happening on that platform.

Re: Goodbye, Fleets

#274

Post by mathw »

kyle-rb wrote: post #246
user-the-name wrote: post #224

Earlier quoted context omitted.

I mean, yes, that is one good argument for not having an edit button. But it is not the reason Jack gave.

If you read the next paragraph in the article, he does say basically that. > Though Twitter has evolved since its SMS days, Dorsey says the static, uneditable nature of posts remains an integral aspect of the platform, as it allows users to retweet and quote tweet others freely without fear that the message they amplified or critiqued could later be altered.

And that is vital. Retweets and quote tweets and replies just fall apart if the parent tweet can be freely edited. Time-limited typo fixing capability is one thing, arbitrary editing is quite another.

Re: Goodbye, Fleets

#275

Post by kuu »

andrewmcwatters wrote: post #180

Maybe someone can correct me, but I don’t recall ever seeing a website fundamentally change itself or evolve and grow whereas I have seen time and time again something entirely new coming out and being the thing people use instead. If you compared Twitter today to Twitter’s first tweet, it’s the same thing. Nothing’s changed with the site itself; I can see people talk about how they ate a sandwich then and still toda…

Threads is a successful feature they added and it's not the same as at the beginning.

Re: Goodbye, Fleets

#276

Post by andy_ppp »

renewiltord wrote: post #271
andy_ppp wrote: post #269

Earlier quoted context omitted.

Yes, it’s inconvenient though, I’m trying to be informed about what everyone thinks, even very thin skinned people who hit the block button at a tiny difference in opinion, some of their opinions are informative and helpful to me so yes as the information is in the public domain it should still be easy to access. The difference here is that my change to blocking doesn’t affect the things you’ve said one bit, how will…

My audience knows that when I tell it to kill all the Apaches, that it’s advice to kill each forked process of Apache2. The consuming madness that causes others who do not speak the language to conclude that I am calling for genocide is not something I choose to engage with. I have a tool. It is effective. Cope with it or don’t. It’s not my problem. Having just realized this tool isn’t going away, I no longer feel th…

I find your arguments quite disingenuous to be honest. It’s a complete straw man example you’ve made up that doesn’t support your argument (nonsense about people being so stupid as to misunderstanding technical and genocidal tweets is absurd). If the information is public you can still be confusing no matter how many people you block. How will you know that people are confused by you if they can’t interact with you? You are right though, Twitter are not getting better at product any time soon.

Re: Goodbye, Fleets

#277

Post by Abishek_Muthian »

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…

> It's always nice to know why an experiment/project failed.

Every failure we can learn from is one which we can avoid for our self. Hence in the startup ecosystem, 'What not to do' is more valuable than 'What to do' but those who are new to the game flock to those selling the latter because 'they tell what one wants to hear'.

The recent #buildinpublic trend is showing some promise. I started my first buildinpublic project recently, A platform to validate minimum viable product but it failed the meta validation and I've detailed the reasons in the twitter thread[1].

But I've noticed that much of the building in public ecosystem is focused upon nocode, Especially flooded with notion related projects. I haven't used it, But I presume the reason is because majority of the people who are watching the #buildinpublic threads are non-coders and are looking to learn how a project is built.

[1] https://twitter.com/Abishek_Muthian/status/13994004552858542...

Re: Goodbye, Fleets

#278

Post by theshrike79 »

berniemadoff69 wrote: post #129
theshrike79 wrote: post #77

Earlier quoted context omitted.

This is why I purge my old tweets automatically. Nothing good has ever come from someone digging up old edgy tweets.

archive.org scoops up all kinds of tweets - deleting them isn't really a safe way to get rid of it, just fyi

Deleting edgy stuff at least gives plausible deniability.

"I don't think like that any more, that's why I deleted the tweet" is a good defence IMO.

Re: Goodbye, Fleets

#279

Post by zimpenfish »

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.

One place I used to frequent solved this by disallowing editing of the original content but allowing the author to add a small annotation after the fact. Doesn't really fix the "correcting typos directly" issue but does allow for clarifications, etc., without the possibility of changing the original meaning that people may have RT/QT/etc.

(You could also extend this to allowing the annotation to be added to a run of text and shove it in the entities object for extra clarity / highlighting.)

Post reply on HN