SeibertLab

37 posts

SeibertLab banner
SeibertLab

SeibertLab

@SeibertLab

Translational + clinical research group @UCSanDiego. Quantitative imaging. Genomic risk. Image-guided #cancer treatment. #ProstateMRI #PolygenicRisk #radonc

เข้าร่วม Temmuz 2021
1 กำลังติดตาม19 ผู้ติดตาม
SeibertLab
SeibertLab@SeibertLab·
@jryckman3 Glad you got your WhatsApp back. Sorry it was so painful
English
0
0
1
17
SeibertLab
SeibertLab@SeibertLab·
@jryckman3 💯 A human would see this for what it is in 10 seconds. Sobering reminder of the limitations of sloppy AI and the (lack of) interest companies using it have in their customers
English
1
0
1
15
SeibertLab
SeibertLab@SeibertLab·
Would appreciate some amplifying so @X will bring me back. They know my email address was on the account for 7 years until 3 days ago...🙄 @dr_coops @OncoAlert @LoebStacy @DrewMoghanaki @sophia_kamran @HenningWillers @mharisinghani @Xristodouleas @subatomicdoc @APCCC_Lugano
SeibertLab@SeibertLab

🚨 My usual account has been hacked. I'm sure that is completely obvious to anyone looking at it. @X refuses to fix it, saying they cannot verify that I am the owner. So much for the power of AI @grok

English
4
13
22
7.1K
SeibertLab
SeibertLab@SeibertLab·
@jryckman3 Thank you, Jeff! It honestly seems kind of hopeless… Wild that there is no grace period when the hack/fraud is so obvious
English
1
0
0
11
Jeff Ryckman
Jeff Ryckman@jryckman3·
@seibertlab since I could not DM this account I will post here- here is what grok said when i asked in a separate query: I don't respond to posts or queries involving account hacks or recovery processes because they often attract scams (like those sketchy replies offering "help" in the thread), and my guidelines strictly prohibit any assistance that could relate to hacking, social engineering, or unauthorized access—even if it's about fixing a legitimate issue. It's to keep things safe and avoid any risk of misleading info. If it's your friend's account (or whoever's), the best bet is sticking to official X support channels directly. That's a tough spot—when the hacker changes the email associated with the account, it blocks the standard password reset flow (since X sends reset links/codes to whatever email is currently linked), and automated recovery becomes much harder. X's official process isn't designed for instant fixes in these cases, but there is still a path forward through their support forms. Here's the realistic breakdown and what to do: Key Challenges in This Scenario Password reset won't work reliably because it routes to the hacker's new email. If there's no verified phone number still linked (or if that was also changed/removed), options narrow further. X prioritizes security, so they require strong proof of ownership before restoring access—especially when contact info has been altered. Responses are often slow (days to weeks, sometimes longer), and initial replies can be automated/generic. Recommended Steps (Stick Strictly to Official Channels) 1. Try the Password Reset Anyway (Quick Check) Go to x.com/account/begin_… (or via the login page > Forgot password?). Enter the username (@handle) or the original email your friend remembers. If X still has the old email on record internally (rare, but sometimes changes don't fully propagate immediately), you might get a reset option or notification. More likely: It'll say to use the current (hacker's) email, or fail. If so, move on. 2. Submit the Hacked/Compromised Account Recovery Form This is the main (and only realistic) official route when email is changed and self-reset fails. Go here: help.x.com/en/forms/accou… Select: "I need to regain access to my X account" > "I believe my account is hacked or compromised" > "No" (can't log in). In the form fields, provide as much verifiable detail as possible to prove ownership: The @username (critical). The original email address tied to the account before the hack. Approximate account creation date (month/year if known). Date you last had access (important for X to check logs). Any previous passwords you remember (even old ones). If there was a phone number linked before (even if removed now), mention it and any associated carrier/details. Describe the hack: When noticed, suspicious posts/tweets/DMs sent, rapid email change, etc. Any other proof: Screenshots of old login confirmations, device info used before, linked apps, or unique content your friend created/posted. Submit from any email you control (it doesn't have to be the original one). X may reply to the submission email with follow-ups or additional verification steps. 3. If There's a Linked Phone Number (Even If Not Current) Mention it prominently in the form—X sometimes uses phone-based verification as an alternative proof if email is inaccessible. 4. Premium Perks (Since Your Friend Has Premium) As a Premium subscriber, the ticket may get prioritized or escalated faster than free accounts (some users report quicker responses with verified/ID-linked Premium accounts). Include the Premium status in the description if relevant. No guaranteed live chat/phone support, but it can help bump the queue. 5. After Submission Monitor the email you used to submit for replies from X (check spam/junk too). They might ask for more info via email back-and-forth (this is where human review often happens). Be patient but persistent—if no response in 1–2 weeks, resubmit the form with any new details or politely reference the previous ticket. Avoid tweeting @XSupport publicly about it (scammers monitor those); DM if needed, but forms are better. Other Notes / Realistic Expectations There's no public phone line, live chat with humans, or direct email for hacked accounts—everything funnels through forms. If the hacker has fully changed email/phone and posted malicious content, X might suspend the account first (to limit damage), which could complicate recovery but also gives another appeal path via suspended account forms. Success isn't guaranteed (especially with minimal proof), but providing detailed ownership evidence improves chances a lot. Many users recover this way after hacker changes, though it can take time. Steer clear of any "recovery services," paid helpers, or DM offers claiming to fix it—pure scams. If your friend has specific details (like if a phone was linked, or exact timeline), share more and I can help refine what to emphasize in the form. Hang in there—good luck getting it back!
English
1
0
1
73
SeibertLab รีทวีตแล้ว
Jeff Ryckman
Jeff Ryckman@jryckman3·
@SeibertLab @X @dr_coops @OncoAlert @LoebStacy @DrewMoghanaki @sophia_kamran @HenningWillers @mharisinghani @Xristodouleas @subatomicdoc @APCCC_Lugano @X please restore this account to its rightful owner. The community relies on Tyler for education and for sharing his excellent work. @grok any idea why @X hasn’t restored it yet? It seems obvious that @TylerSbrt was hacked. Do we need a petition or something to get this fixed?
English
7
4
12
1.1K
SeibertLab รีทวีตแล้ว
Drew Moghanaki
Drew Moghanaki@DrewMoghanaki·
@SeibertLab @X @grok Yo @grok. Can you fix this account that’s been hacked and return it to its rightful owner?
English
7
1
3
1.4K
SeibertLab
SeibertLab@SeibertLab·
🚨 My usual account has been hacked. I'm sure that is completely obvious to anyone looking at it. @X refuses to fix it, saying they cannot verify that I am the owner. So much for the power of AI @grok
SeibertLab tweet media
English
19
1
11
6.6K
SeibertLab รีทวีตแล้ว
Sophia Kamran, MD
Sophia Kamran, MD@sophia_kamran·
🚨Thanks for the shout out! Specifically, we assembled a coalition of 7 institutions & pooled data looking at treatment specifics/outcomes for patients with oligometastatic prostate cancer who received RT (given that there is no consensus or guideline for management). #asco25
English
3
4
46
3.4K
SeibertLab รีทวีตแล้ว
Andrew Vickers
Andrew Vickers@VickersBiostats·
@DrSpratticus Indeed, including those open at MSKCC where we accrue perhaps 122 patients per year. Cancer RCTs accrue slowly because they are too complex, too burdensome for patients & MDs, & don't address the reasons why patients don't go on trials (& why MDs don't approach them for consent)
English
2
1
14
841
SeibertLab
SeibertLab@SeibertLab·
@piet_ost Fantastic work, Piet! Thank you for doing this! 👏🏻👏🏻
English
0
0
1
28
SeibertLab รีทวีตแล้ว
Piet Ost
Piet Ost@piet_ost·
📢 STORM trial breaking results at #ESTRO25! 🧪 MDT vs ENRT+MDT for nodal oligorecurrent PCa. 🧬 ENRT+MDT: ✅ Superior bRFS (57% vs 41%, p=0.014) ✅ Superior pelvic control (lrRFS 85% vs 62%, p=0.006) ✅ Superior MFS (76% vs 63%, p=0.06) ❌ No increase in ≥G2 GU/GI toxicity
Piet Ost tweet mediaPiet Ost tweet media
English
17
103
206
20.2K
SeibertLab รีทวีตแล้ว
Piet Ost
Piet Ost@piet_ost·
Link to full paper: shorturl.at/NGwdG
English
2
10
29
1.8K
SeibertLab รีทวีตแล้ว
Jeff Ryckman
Jeff Ryckman@jryckman3·
Jeff Ryckman tweet mediaJeff Ryckman tweet media
ZXX
0
3
4
483