What if you could get a full course on anything by just describing what you want to learn?
You tell the AI what you want to learn—any topic—and it builds a full course: outline, lessons, everything.
You read at your pace, and when you’re stuck you ask your course in the chat.
No curriculum hunting. Describe it. Get a course.
check it out at https://t.co/8gWBmroC6x
The South East now has a structured venture capital programme. Founders are pitching. Investors are committing. An ecosystem is taking shape.
MOII
#SEVCP#SEDC#VentureCapital#RenewedHope
CKB Has No Plan — But We Do.
Our previous posts about roadmaps generated some controversy.
We’re grateful to have your attention.
Because this distinction matters.
CKB doesn’t have a roadmap because it is public infrastructure, not a product operated by a company.
The goal of any serious blockchain is not endless reinvention. It is to become a stable, secure, and predictable infrastructure that others can build on for decades.
That said, CKBA absolutely has plans.
CKBA exists to coordinate stakeholders and grow the CKB ecosystem across the areas that matter most.
That means organized work to attract builders, identify use cases, improve developer onboarding, fund ecosystem initiatives, pursue partnerships, clearly communicate CKB’s value, and actively engage the teams, companies, and communities that can drive real usage on the network.
Having reorganized and unified several teams under a single structure puts us in a stronger position than ever to execute on these goals.
A ton of work is already underway, especially on the Fiber front: improving the stack and documentation, advancing Lightning interoperability and liquidity management, and identifying and removing blockers for adoption.
Work is also ongoing on the design and implementation of the DAO's on-chain treasury and voting mechanisms.
And while there are many other initiatives in the pipeline that we’ll share when the time is right, there’s one that demands immediate attention 👇
Three months ago, Google Quantum AI published a bombshell paper showing that quantum attacks against secp256k1—the elliptic curve behind the signatures used by most blockchains—may require far fewer resources than previously estimated.
In simple terms, the paper made the quantum threat to cryptocurrencies harder to ignore.
The industry conversation that followed was, as expected, hard to miss — and yet it missed CKB.
No mention in the paper, no mention in the con im versations on X and various forums, no mention anywhere.
To put it bluntly, this is a huge communication failure on our part.
CKB is the only cryptographically agile blockchain in existence, and therefore one of the few that’s already quantum ready.
It’s the only chain where devs can bring new post-quantum signature schemes permissionlessly.
No need for soft or hard forks. No need to pick a single PQ scheme and bake it in as a precompile.
CKB is the only chain that can switch between different crypto primitives without disrupting operations or requiring significant infrastructure redesign.
It’s the true embodiment of crypto-agility — yet barely anyone was aware of it.
So, our first course of action on the communication front is to remedy that.
We’ll run a comprehensive marketing campaign that’ll put CKB at the forefront of the Quantum x Blockchain discussion and position it as one of the few projects with a future-proof solution.
And we want all of you involved.
If you care about CKB and want to help push this forward, reach out.
If you’re a developer, researcher, writer, designer, translator, community organizer, content creator, or just someone willing to help amplify the message, we want to hear from you.
This campaign should not be about what CKBA has to say.
It should be about making CKB impossible to ignore.
We’ll be opening channels for community participation soon. In the meantime, reply here, DM us, or join the discussion on Nervos Talk.
In the last 6 months at @Ahrefs, we analyzed over 1 billion data points across 14 studies. Here's what we learned about AI search optimization:
1) "Best X" blog listicles are the single most prominent content format cited by AI chatbots. They make up 43.8% of all page types cited by ChatGPT specifically.
2) 67% of ChatGPT's top 1,000 citations come from sources marketers can't influence: Wikipedia (29.7%), homepages (23.8%), app stores (6.6%). Only 32.3% are influenceable content like educational pages, reviews, news, and blog posts.
3) 28.3% of ChatGPT's most-cited pages have zero Google organic visibility. These pages get cited repeatedly by ChatGPT despite not ranking in Google at all. A completely separate discovery layer.
4) ChatGPT only cites about 50% of the URLs it retrieves. It fetches dozens of pages per query but uses half as background context without attribution. This means that being retrieved and being cited are very different things.
5) Adding schema markup had zero meaningful impact on AI citations. AI Overviews actually dipped −4.6%, while AI Mode (+2.4%) and ChatGPT (+2.2%) showed changes indistinguishable from zero.
6) YouTube mentions have the highest correlation (0.737) with AI brand visibility out of all the factors we studied (including all the conventional SEO metrics like backlinks, page count, DR, etc). This held true for both Google-owned and OpenAI products.
7) AI Overviews reduce clicks to the #1 result by 58%. That’s up from 34.5% just 10 months earlier. The trend is accelerating.
8) 99.9% of AI Overviews appear on informational intent queries. Transactional, navigational, and local searches are almost entirely AIO-free. Shopping triggers AIOs just 3.2% of the time.
9) For a given search query, Google’s AI Mode and AI Overviews reach the same conclusions 86% of the time — but cite almost entirely different sources (only 13.7% citation overlap).
10) AI Overviews change every 2.15 days on average, with 70% of content differing between consecutive observations. But semantic similarity stays at 0.95. The words, sources, and entities constantly shuffle, but the actual meaning barely moves.
Some tips to help agents understand your codebase:
1. The source code either needs to be the source of truth, or have something legible as a path to the source. For example, if marketing site content is actually stored in a CMS, you need to either delete the CMS and move that content into code, or make the CMS legible through and MCP, CLI, or skill: https://t.co/zhObygzELv
2. Agents need to be able to verify their work. This includes but is not limited to: using a typed language, having high-quality and fast tests, having a well-configured linter: https://t.co/AL3eY6TBXr
3. You need to have a concise and effective AGENTS.md file, which is included in every message to your agent. Models are quite good now, so some things you can omit as the models know them. You don’t need to say the tests live inside /tests for example. It’s worth asking the models to find things in your codebase and making sure they’re named what the models might expect, otherwise consider refactoring: https://t.co/2FlVQr84nO
4. Set up automations which give you suggestions for refactoring code, catching security issues which may have slipped through code review, and optionally continuous documentation of the codebase. You can effectively create a self-driving codebase which gets better while you sleep: https://t.co/UuYL3KNTZc
To get good animations from an AI you need to get good at telling it what you want:
- "stagger this list of items"
- "make this animation direction-aware"
- "spacial consistency", "crossfade", "layout animation",
I made a motion vocabulary for this:
https://t.co/ExAxpr31no
BlackBox Devlog #3
The headline this fortnight is an ESP32 board emulator that runs actual device binaries on desktop — shrinking the embedded debug loop from minutes to seconds. Alongside it: an LVGL display port and a new post-quantum backend protocol.
Tooling — arduino-board-emulator:
🔸Built an ESP32 + TFT + touchscreen emulator that runs actual device binaries as a desktop application — closing the flash-observe-tweak loop that previously cost minutes per iteration
🔸Current feature set: ST7789 graphical display (LGFX and LVGL), XPT2046 touch emulation via mouse, SPIFFS/LittleFS virtual filesystem (PNG/JPEG support), Wi-Fi connectivity, and synced time from an HTTP server
🔸Thermal printer output and barcode scanner input also emulated — scanner via USB camera, thermal printer via virtual output
UI — LVGL port:
🔸Porting BlackBox's display layer off the previous custom driver onto LVGL — the industry-standard embedded GUI library
🔸Payoff: cleaner display abstraction, greater flexibility, and a substantially better UX baseline
Hardware — ESP32-S3 prototype:
🔸Next target board is ESP32-S3 based; peripherals being integrated for the V2 prototype in parallel
Backend — cemp-pq + light-client-lite:
🔸cemp-pq: a post-quantum cryptographic messaging protocol, unlocking a new class of communication capabilities for the device
🔸Minor optimisations landed in ckb-light-client-lite, to be integrated into the upcoming S3 iteration
Full devlog:
https://t.co/2XtGukS5FB
🐍📺 Connecting LLMs to Your Data With Python MCP Servers [Video]
Build an MCP server in Python that exposes tools, resources, and prompts, enabling AI agents like Cursor to interact with your data
https://t.co/fVwx6hrSqJ
Three weeks ago, my 23-year-old neighbor was kidnapped on her way to Kontagora in Niger State.
While in captivity, the bandits repeatedly raped her taking turns sleeping with her night after night. Still, they kept bargaining with her father over the phone, demanding ransom even as they violated her.
Her father fought with everything he had. He hustled day and night, borrowed from everyone, took loans, sold whatever he could determined to bring his daughter home.
When he finally gathered the full amount, he called the bandits and begged them, ‘Please, give the phone to my daughter. Let me speak to her. I want her to know I’m coming for her.’
They gave her the phone.
In a broken, traumatized voice, she told her father: ‘Dad, do not suffer yourself looking for the money. They have been sleeping with me. I’m traumatized. I can’t forgive myself. Even if I’m released, I’ll kill myself. Don’t bother paying the ransom.’
Those were the last words she ever spoke to him.
While her father was still holding the phone, he heard the gunshot. He heard his daughter being killed. Moments later, the bandits sent pictures of her remains to him, a final act of cruelty.
A 23-year-old girl. My neighbor. Someone’s daughter, someone’s sister, someone’s friend gone in the most horrific way possible.
This is not just one story. This is the nightmare too many families are living in Niger State and across Nigeria. Young women snatched on the roads, violated, used as bargaining chips, and discarded like nothing.
Living in Nigeria has become truly scary. You wake up, you step out, and you don’t know if you or your loved ones will return home. The fear is constant. The pain is constant. And too often, justice never comes.
Rest in peace to my neighbor.
This video is exactly what I went through in Ladipo market!
I bought an engine for my Toyota Highlander some time ago. The dealer gave me 7 days warranty – if anything went wrong, I should return it.
His own mechanic installed it. Immediately after, the engine started smoking badly with heavy knocking.
To make matters worse, plenty of bolts and nuts were removed and never tightened back. The engine and gear were vibrating so violently it felt like they wanted to fly out of the car!
I called the dealer.
He came, saw everything and said the engine would need to be replaced. I paid ₦20k for the labour. The mechanic even told me casually, “If we have to change it again, you go pay another money o.” I told them clearly: the dealer is paying – I’m not adding one kobo.
After plenty of stories, they showed me “another engine” to install the next day.
Fast forward: before I even reached the market the following morning, these guys had removed the same smoking engine overnight and repainted/refurbished (“ringed”) it to make it look brand new and different. Thank God I already took the engine number of the faulty one!
When I showed them the evidence, they started denying. The dealer had suddenly “travelled to the port to clear goods.”
I went to meet some guys on Oloruntoyin Street, settled them, and we stormed the shop. Before I could blink, strong boys arrived and properly bombed the place! Fast fast, the dealer appeared from nowhere and started begging.
After all the drama, I got a replacement. But I still towed the car to another mechanic and spent even more money.
Ladipo is full of these atrocities. That place needs serious sanitization. Lagos State government, please step in! This nonsense has gone on for too long. 🚨
Glam Up hit $1.8m ARR in 8 months.
Sprout hit $3m ARR in 7 months.
The key to that was our UGC playbook.
I'm finally dropping the playbook and lowkey I'm scared to drop this. You'll understand why once you read it.
It's gonna be three parts but here's part 1. Part 1 itself is 40 pages long.
I made sure it's tactical advice and upfront with no BS.
Bonus: repost + reply 'warmup' and I'll DM you the Account Setup + Warmup module from our internal creator course.
Must be following so I can DM.
https://t.co/2hnJJamrdm
Second time I’ve seen @madebycol tell the Glam Up / Sprout story in a way that materially misrepresents who built what.
She contributed. But this was not a solo founder story, and I’m not going to keep letting my work, nor my team's work get erased.
It's frustrating, sad & disappointing.
Dear frontend devs and UI designers. I bring you Liquid DOM, a complete and faithful implementation of Liquid Glass on the Web.
- Shape morphing
- All properties animatable
- Dynamic refraction and reflection
- Adaptive tint
- Adaptive specular highlight
- Dispersion
- Full html integration
- Super fast layout engine that works across Canvas and html
- Pointer event handling
- Framework and renderer-agnostic low level API
- High level React API
- Ootb @threejs and r3f integration
And lots more.
Read on for implementation details and demos.