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

Threads.net Can Go to Hell

lapcatsoftware.com

Post reply on HN
Print view View original

61–70 of 70 posts

Re: Threads.net Can Go to Hell

#61

Post by qingcharles »

lapcat wrote: post #45
input_sh wrote: post #15

Just a phone number!? Lucky you, Instagram wants me to take a selfie with some random code written on a piece of paper. I had this account for years, but I only used it to get away from "log in to see more posts" whenever I randomly stumbled upon some Instagram link, so yeah, I'm not doing that.

> Instagram wants me to take a selfie with some random code written on a piece of paper. It's possible they may have wanted that too, eventually. The phone # request came at the beginning of the appeal process.

It's the next step after the phone number. I went through the same process this morning. After you upload the selfie they perma-ban your account so you can no longer get any support whatsoever.

https://news.ycombinator.com/item?id=37254898

Re: Threads.net Can Go to Hell

#62

Post by qingcharles »

input_sh wrote: post #15

Just a phone number!? Lucky you, Instagram wants me to take a selfie with some random code written on a piece of paper. I had this account for years, but I only used it to get away from "log in to see more posts" whenever I randomly stumbled upon some Instagram link, so yeah, I'm not doing that.

Do not upload that selfie. If you read online you will find it is a trap that perma-bans your account.

https://news.ycombinator.com/item?id=37254898

Re: Threads.net Can Go to Hell

#63

Post by lapcat »

qingcharles wrote: post #61
lapcat wrote: post #45

Earlier quoted context omitted.

> Instagram wants me to take a selfie with some random code written on a piece of paper. It's possible they may have wanted that too, eventually. The phone # request came at the beginning of the appeal process.

It's the next step after the phone number. I went through the same process this morning. After you upload the selfie they perma-ban your account so you can no longer get any support whatsoever. https://news.ycombinator.com/item?id=37254898

The forms don't work for me. One form requires "Your mobile number", and the other form say "Go to Instagram and confirm it's you before requesting a review", which I can't do.

Re: Threads.net Can Go to Hell

#64

Post by qingcharles »

lapcat wrote: post #63
qingcharles wrote: post #61

Earlier quoted context omitted.

It's the next step after the phone number. I went through the same process this morning. After you upload the selfie they perma-ban your account so you can no longer get any support whatsoever. https://news.ycombinator.com/item?id=37254898

The forms don't work for me. One form requires "Your mobile number", and the other form say "Go to Instagram and confirm it's you before requesting a review", which I can't do.

Yeah, their code is a Dumpster fire. I'm not surprised you ended up in some circle of hell like that. I just tried to log into Threads with my banned Instagram account and now both sites just report HTTP Error 429, which I had to look up. (It's client rate limit reached)

Re: Threads.net Can Go to Hell

#66

Post by allarm »

jasonlotito wrote: post #24

> I would urge everyone to reconsider your reliance on Twitter, and reinvest in decentralized options such as blogs, RSS, and email. None of these suggestions replace what Twitter offers as a whole. Suggesting blogs, RSS, and email as a replacement really is just another way of saying you don't know understand the domain. Which is fair, considering who the person is. This is not to say that blogs, RSS, and email can'…

> None of these suggestions replace what Twitter offers as a whole

So? I think it’s clear that the accent here was not on twitter replacement as a whole, but on the decentralized options. And it’s fine to give up some functionality of a service when choosing an alternative. Especially when the reason for the switch is the unbearable user experience.

Sometimes there might not be any alternative, and that’s also fine. I stopped using social networks and youtube years ago and I feel much better than before. It felt like I was missing out something, but this feeling didn’t last long.

> considering who the person is.

What do you mean?

Re: Threads.net Can Go to Hell

#67

Post by [deleted] »

PaulHoule wrote: post #4
CharlesW wrote: post #3

Earlier quoted context omitted.

Where does the author do this? All I see is, "you can find me on the decentralized Mastodon".

I post a lot of photos, particularly of flowers, to mastodon.social because I get very good engagement on them. I know a lot of people using Pixelfed find them, favorite them, and boost them.

[deleted]

Re: Threads.net Can Go to Hell

#68

Post by newscracker »

Instagram bans accounts for no reason at all. It’s had some rogue and buggy bots or algorithms banning or deactivating accounts for years. Appeals don’t work.

Unfortunately, this situation doesn’t get a lot better with the fediverse, where one or two admins would decide what they like or dislike and use the ban hammer without any warnings. No appeals process or no responses over other channels. Maybe everybody is better off having their own blogs and websites rather than having (unpaid) accounts on others’ systems (centralized or not).

Re: Threads.net Can Go to Hell

#69

Post by bakugo »

talldatethrow wrote: post #57
bakugo wrote: post #21

I just remembered that I read a bunch of comments here back when Threads launched about how Twitter was dead and Threads would replace it. A few months later and Threads is effectively dead. Pretty funny in retrospect.

Hijacking a thread here trying to ask you a php question. Linked below, you said something reminds you to a old times when you were using arrays to work through database results. I still do this, building multidimensional arrays of results to later use. How should/could I be doing it? I'm self taught but built a decent sized webapp CRM/project management saas and am trying to learn a few new things before starting a…

I already explained how I personally do it in that comment chain: Doctrine ORM and Symfony. Instead of working directly with raw database data as arrays, you work with classes where all the database columns are defined as typed class properties and let the ORM handle the conversion between the two for you.

If you're starting a new project in PHP, I recommend giving it a try. The SymfonyCasts tutorials are a great way to start (though sadly they're not free).

Re: Threads.net Can Go to Hell

#70

Post by paulddraper »

edgyquant wrote: post #65
paulddraper wrote: post #60

Earlier quoted context omitted.

Oof dead for sure

Maybe not dead, but the opposite of what you suggested

I suggested it increased in popularity over three months and provided the evidence.

There was a separate link provided which said nothing about whether it increased or decreased in popularity over any timeframe.

Post reply on HN