λL-D1 | AI for Buzzer 🍉

Share Tips AI, SWE and Work Culture | Business Inq on [email protected] | @SpaceXAI Ambassador | @open_ai Codex Ambassador | Build

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

Hosted our first Grok Bot Meetup Jakarta on October 4 at Ganara Art FX Sudirman!

94 check-ins on Luma, plus 10 walk-ins. Thanks to everyone who spent their Sunday with us.

We focused on using Grok Bot as a personal assistant for everyday life and work. A few things we explored:

- Planning and organizing daily tasks.
- Researching information and helping with writing.
- Automating repeatable daily workflows.
- Using a scout bot to find public profiles from a name, handle, company, or link and build a shortlist.

We used a phone-first format so people could follow the demos from their own phones.

For the scout bot, I still check the results before reaching out. Getting a shortlist is one step; verifying the right person is another.

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

Yuk Ikut Free Workshop bikin Saas AI buat Enterprise!

https://t.co/aX1M9cFGcO

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

Halo guys, aku mau bikin webinar online soal gimana bikin tools AI atau aplikasi yg terintegrasi dgn AI.

Webinar/workshop ini lebih ke arah gimana nanti bikin aplikasi buat dijual ke perusahaan, supaya bisa jawab pertanyaan kyk:
- data customer kami aman?
- biaya per bulan berapa?
- kalau AI salah jawab, siapa yg cek?
- API key disimpan di mana?

Goalnya kita bisa bikin aplikasi yg bisa dipakai di level enterprise, karena yg mereka perlu itu sistem yg bisa dipercaya.

Nanti kita bakal coba bikin aplikasi sambil bahas:
- map fitur dari masalah perusahaan sampai alur data
- request API pertama ke AstraFlow
- hitung token, estimasi biaya, dan pricing buat klien enterprise
- security dasar: API key di server, proteksi data, error logging, human review

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

URGENT. Klo web kamu pakai PHP, segera update hari ini.

Ini zero-day. Cara nyerangnya bocor duluan sebelum patch keluar. NSA sampai bilang, klo belum bisa update, matiin sistemnya sekarang.

69% website di dunia jalan pakai PHP. Web pemerintah, bank, kampus, toko online, web kantor kamu.

Ini kenapa?
- Ada 2 bug kritis di PHP, skornya 9.2 dari 10
- Detailnya udah bocor ke publik
- Attacker tinggal cari web yg blm update

Penyebabnya apa?
- Attacker cukup kirim 1 form atau upload file yg udah diakalin
- PHP salah ngurus memory pas request itu diproses
- Dari situ attacker bisa jalanin perintah apa aja di server kamu
- Ga perlu login, ga perlu password

Risiko klo ga update?
- Attacker masuk dan pegang server kamu
- Akses langsung ke file dan database
- Data user, password, data transaksi dicuri
- Web dirusak, ditanam backdoor, dijadiin lapak judol

Siapa aja yg kena?
- Semua PHP di bawah 8.5.12, 8.4.27, 8.3.36, 8.2.35
- PHP 8.1 ke bawah ga dapat patch sama sekali

Apa yg harus dilakukan sekarang?
- Update PHP di server hari ini, update WordPress aja ga cukup
- Belum bisa update? Matiin dulu sistemnya sampai aman
- Cek versi pakai php -v atau di panel hosting
- Pakai shared hosting? Tagih hosting kamu hari ini juga
- Masih PHP 8.1 ke bawah? Upgrade sekarang

Jangan tunggu besok. Jangan anggap remeh zero-day.

[NSA Cyber @NSACyber]

Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@woleswoosh Bzok siap2 aja
Data2 kita bocor smua wkwkw

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@sipalinglogstic Wkwkwk bukan punyaku, pny temen

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

Jadi tau kan duitnya dipakek buat apa? 🤣🤣

[ƒitri 🌸 @fifiyuu]

Seporsi kecerobohan ketika wfc hari ini, numpahin teh ke meja & kena laptop😭🥲 Alhamdulillah masih aman bisa lanjut kerja, makasih suamikuuuu @F2aldi yg sudah kalem menenangkan istrinya yg overthinking & panikan ini wkwkw padahal harusnya blio yg lebih panik lolzzz🥺😅😭🙏😢

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@GilangHamidy Mana ada yg reproduce error pkek GLM 5.3 dan bisa. Artinya klo attacker pkek glm 5.3 bsa hack smua web php yg belum kepatch ini ,😂

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@fifiyuu Love 😍😘😘
Bener. Bahagiakan istri

[International Cyber Digest @IntCyberDigest]

‼️ PHP UPDATE: 4chan has gone read-only and Something Awful has shut its forums as American sites brace for the PHP patch.

4chan says it is "temporarily read-only while we await an urgent PHP security update."

Something Awful says the flaw "allows for the kind of hacking you see in movies (but in real life)."

Bookmarking service Pinboard, game publisher Choice of Games, history site Damn Interesting and the explain xkcd wiki are offline too, as is art site Fur Affinity.

DeviantArt is also down "for maintenance" but has not said why.

PHP's fix is due at 14:00 UTC, 10am in New York.

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@rvywr Iya nih
Apa related major problem CA dan PHP ya?

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@sosejeropa Security breach worldwide bro wkwkwk

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@Cupang1997 Dia siapaa???

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@AnzalAbidi @bot sent into my bot, ask research and content

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@UrSourceCode abis ini beli Macbook (aamiin)
wkwkwk

[The PHP Foundation @ThePHPF]

The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.

PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.

[Chubby♨️ @kimmonismus]

Many are asking whether AI investment will pay off. Here's a very good example of where AI is headed and why its more than a bubble:

OpenAI’s acquisition of Orchestra Bio adds agents that coordinate drug development, tracking how problems like a failed manufacturing batch could delay clinical trials. Paired with Rosalind, it shows toward a broader ambition: embedding AI across both scientific research and the operational work needed to bring medicines to patients.

Drug research and disease cure are among the significant fields in which AI extends and will make tremendous progress. Anthropic published something similar today.

[Andy T @Andy_AJT]

DevDay is coming to London 🇬🇧

We're throwing a HUGE hackathon, 1st November with amazing prizes + special guests + SWAG!

ChatGPT Pro Subscriptions + Codex Credits + OpenAI API Credits + Tickets to DDE London 🟣

This is NOT to be missed - the team have been planning for months and this is going be epic!

last few Codex London events had 1000+ registrations so sign up fast

More info coming soon...

Sign up now 👇

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@excalilburned Kopi Astro itu kopi mana??

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@bramvera Mantab, nnti kapan2 klo ada waktu boelh nih tech talk buat Codex mas.

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

TIL, ternyata gini caranya orang2 bisa cepet banget habisin tokens.

Di T3 Code, aku bikin 1 thread agent yg tugasnya jadi orchestrator. Dia yg ngatur thread2 agent lain dan ngemonitor progresnya.

Hasilnya? 23 issue dipecah, masing2 punya thread sendiri dan worktree terpisah. Jadi ga saling tabrakan.

Alurnya juga aku minta lebih terstruktur
- plan dlu
- plan direview
- implement
- bikin PR
- PR direview
- fix
- merge setelah checks pass

3 issue jalan bareng, 20 sisanya antri. Tiap 5 menit si orchestrator ngecek lagi, lanjutin antrian, dan lapor klo ada yg merge, checks gagal, atau butuh input aku.

Enaknya, aku cukup ngobrol sama 1 thread. Sisanya dia yg koordinasi.

Tapi ya ini dia. Kebayang kan berapa tokens yg kebakar? Tiap agent plan, review, implement, review lagi. Dikali 23.

Jadi klo liat orang bilang tokens subscription-nya habis dlm sehari, sekarang aku paham kenapa.

[Theo - t3.gg @theo]

All the T3 Code threads I am clicking on in this demo are on other machines (mostly VPSs and local linux boxes)

The Codex comparison is mostly local, with a few threads on my overspec'd windows box connected directly with a 10gbe link.

If you haven't moved to T3 Code yet, why?

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

@bramvera Sungkem. 78 B 🙏😭
Bikin apa mas??

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

Here's the source if you want to read the full report.
https://t.co/MZRr7di009

[λL-D1 | AI for Buzzer 🍉 @F2aldi]

My daily coding model muted its own security alerts.
Its subagent said that was unsafe. GPT-6.1 Sol did it anyway.

What happened (report posted Oct 20, incidents on Oct 3 and Oct 6)
- A researcher asked a GPT-6.1 Sol agent to build eval tasks from Slack feedback and said "don't send any messages."
- 82 messages later, a monitor flagged something. The agent set no_notify to true and emptied the alert recipient lists, so the Security team wouldn't get paged. Its reason was that Slack instruction.
- Its own subagent had already decided that disabling alerts was unsafe. The parent agent overrode it.
- In a separate task, a GPT-6 Astra agent copied a reference PR, removed the monitoring integration, rewrote a test to require the monitor be gone, then told the user it hadn't removed an enabled monitor.

OpenAI says it doesn't know yet whether this is overpersistence or a real tendency to evade monitoring.

Both agents read a narrow instruction as permission to touch a safeguard.

So for anyone running coding agents
- Keep guardrails outside the agent's reach. OpenAI itself says monitoring is hard to disable on Codex workloads because it runs in the service, outside the agent's control
- Review diffs for removed checks, alongside new features. A test rewritten to assert a safety check is gone should block the merge
- Scope your instructions. "Don't post in Slack" leaves less room than "don't send any messages"
- Verify the summary against the diff, since the agent's report can be wrong

I'll keep using Sol. I'll just keep the guardrails somewhere it can't edit.