zlacker

[parent] [thread] 9 comments
1. singlu+(OP)[view] [source] 2023-11-18 05:36:43
Greg Brockman sharing the timeline on Twitter: https://twitter.com/gdb/status/1725736242137182594?s=46&t=Nn...
replies(4): >>zer0c0+rd >>theyin+wf >>nullan+Rm >>hu3+PT
2. zer0c0+rd[view] [source] 2023-11-18 07:38:52
>>singlu+(OP)
His timeline.
3. theyin+wf[view] [source] 2023-11-18 07:58:29
>>singlu+(OP)
As both hint to "greater things" already on the horizon: maybe they were working on/for competitor on the sidelines and the board found out?
replies(1): >>ktta+2i
◧◩
4. ktta+2i[view] [source] [discussion] 2023-11-18 08:21:40
>>theyin+wf
That's standard "You were too good for them anyways" post break-up speech
5. nullan+Rm[view] [source] 2023-11-18 09:03:57
>>singlu+(OP)
Reading that thread made me realise how low the signal to noise ratio is over on twitter.

90% of the replies scrolling down were rehashed versions of "can't believe they used Google meet"

replies(3): >>Raston+Zo >>komali+Qp >>layer8+UT
◧◩
6. Raston+Zo[view] [source] [discussion] 2023-11-18 09:22:11
>>nullan+Rm
Monetization of "hot takes" and baiting, true example of enshittification
◧◩
7. komali+Qp[view] [source] [discussion] 2023-11-18 09:30:25
>>nullan+Rm
Try blocking all bluechecks. After doing so is the first time in like a decade that Twitter has had good content for me.

Before, braindead or cloutchasing bluechecks were mixed in with the rest of us rabble. Hard to pick them out of the pack, you had to read their detritus with the rest of the comments.

Now they voluntarily self identify, and even better, their comments are lumped at the top. So block them all with a bot or just scroll down until there's no more blue checks and the comment quality jumps exponentially.

8. hu3+PT[view] [source] 2023-11-18 13:20:36
>>singlu+(OP)
Copy-pasted here for posterity:

Greg Brockman @gdb

Sam and I are shocked and saddened by what the board did today.

Let us first say thank you to all the incredible people who we have worked with at OpenAI, our customers, our investors, and all of those who have been reaching out.

We too are still trying to figure out exactly what happened. Here is what we know:

- Last night, Sam got a text from Ilya asking to talk at noon Friday. Sam joined a Google Meet and the whole board, except Greg, was there. Ilya told Sam he was being fired and that the news was going out very soon.

- At 12:19pm, Greg got a text from Ilya asking for a quick call. At 12:23pm, Ilya sent a Google Meet link. Greg was told that he was being removed from the board (but was vital to the company and would retain his role) and that Sam had been fired. Around the same time, OpenAI published a blog post.

- As far as we know, the management team was made aware of this shortly after, other than Mira who found out the night prior.

The outpouring of support has been really nice; thank you, but please don’t spend any time being concerned. We will be fine. Greater things coming soon.

10:42 PM · Nov 18, 2023

8.1M Views

◧◩
9. layer8+UT[view] [source] [discussion] 2023-11-18 13:21:17
>>nullan+Rm
And “can’t believe how shitty the Twitter replies are” is any better?
replies(1): >>nullan+yWj
◧◩◪
10. nullan+yWj[view] [source] [discussion] 2023-11-23 13:19:46
>>layer8+UT
Seemed like a pretty productive conversation to me. As a non-twitter regular I now know how to make things more bearable in the future thanks to this discussion.
[go to top]