Timi-jah retweeted
Imagine your kids are starving with no clothes, and as a father you buy a 65-inch TV so they can watch Cocomelon in HD.
That's exactly what this government is doing.
Timi-jah retweeted
“I believe in God, just like a blind person believes in the sun.
Not because he sees it, but because he feels it.”
Timi-jah retweeted
Today, with our team of lawyers at the Federal High Court in Maitama, Abuja. These brilliant lawyers appeared free of any charges for the case against MTN Nigeria, Airtel Nigeria, Glo World, FCCPC, and DStv.
They were led by Ogbaga Ogba Immanuel. Before 8 AM this morning we were at the court to officially begin the case. Unfortunately, the court adjourned until 15th of November.
On the 18th, we will be there and we will continue to talk about what these telecoms are doing to Nigerians and also continue the legal challenges, until the relevant authorities put an end to the open fraud these big corporations are committing against Nigerians.
Our case is simple:
If I buy a 30-day data plan and use it heavily, the network tells me my data has been exhausted after just a few days. Their justification is simple: you’ve consumed everything you paid for.
Fair enough.
But if I use the same data sparingly and still have a balance on the 30th day, the remaining data suddenly expires. The justification now changes: your subscription has reached its validity period.
So which principle is actually governing the transaction?
If the argument is that I am being charged based on usage, then why should unused data expire at all? I haven’t consumed what I paid for.
If the argument is that I paid for 30 days of access, then why is the data allowed to run out before those 30 days are over? Shouldn’t I continue to have access until the agreed expiration date?
The industry appears to switch between two contradictory principles, depending on which one benefits the company at that particular moment.
-When heavy usage favors the network, they say: “You used it all.”
-When light usage favors the customer, they say: “Time is up.”
The customer loses under both systems.
This inconsistency becomes even more obvious when you compare it with airtime.
Your airtime does not disappear simply because 30 days have passed. It remains yours until you actually spend it. The network does not wake up one morning and confiscate your remaining airtime because a calendar date has arrived.
Why then should paid data be treated differently?
The principle should be consistent.
If a data bundle has a fixed expiration date, then the purchased volume should remain available until that date, regardless of how quickly or slowly it is used.
Conversely, if the network insists that data can be completely exhausted at any time based solely on consumption, then there is no logical basis for imposing an expiry date on any unused balance. Once I have paid for it, what I have not consumed should remain mine until I consume it.
You cannot simultaneously tell customers:
“Your data can finish before the validity period because usage matters,”
and then turn around and say,
“Your remaining data has expired because the validity period matters.”
Those are two different charging philosophies. Switching between them depending on which one increases company revenue is not a coherent billing principle — it is a contradiction.
The question is simple:
When consumers pay for data, are they buying a quantity of data, or are they buying time?
If the answer is data, then unused data should never expire.
If the answer is time, then the purchased data should remain available throughout that entire period, regardless of consumption patterns.
The current system attempts to have it both ways, and in every scenario, the consumer bears the loss.
And this is why we have gone to court.
In South Africa right now, the regulator ICASA has ordered MTN and Vodacom to stop letting data expire.
New rules say unused data, voice and SMS must roll over automatically, at no extra cost, once the bundle's time is up.
MTN and Vodacom did not comply quietly. They took ICASA to court to try to block it. They are facing fines of about R5 million each for non compliance. That's about N410 Million.
That is the real story. A regulator with teeth forcing
🤖 Made with AI
Timi-jah retweeted
aight, fuck it, my turn for this kind of post
i'm looking for work.
i'm 21 and i've spent a rather unreasonable amount of time building software over the past year.
here's some of what i've been up to:
kiban: built an embedded LSM storage engine from scratch in rust. WAL, SSTables, compaction, snapshots, concurrency, crash recovery and fault injection.
the benchmarks are probably my favourite part. on warm 1M-record workloads, i got 0.96µs median point reads and over 1M point-read calls/s, with 2.2-2.7x faster point reads than tuned RocksDB. group commit pushed fully durable writes to 5,379/s at 16 writers, a 7.5x improvement. also managed to shrink the point index by 61%.
styx: a ~41k LOC bittorrent client in rust with 600+ tests. implemented peer-wire networking, verified downloading/seeding, trackers, DHT, magnet metadata exchange, daemon IPC, CLI/TUI and a desktop shell.
kurogane: implemented Raft consensus from scratch in rust. elections, log replication, snapshots, crash recovery, joint consensus, real gRPC networking and a deterministic fault-injecting simulator with linearizability verification.
konto: built a double-entry accounting engine with PostgreSQL and typescript. atomic transactions, holds, transfers, idempotency and enforced financial invariants. includes stress testing with 1,000 concurrent transfer/hold operations.
iris: built a GPU-accelerated image viewer for linux using rust, Vulkan, GTK4 and DMA-BUF. RAW decoding, ICC colour management, GPU rendering, Wayland presentation and software fallbacks.
webnotes: built a local-first notes app with a native Tauri desktop client, SQLite storage, bidirectional linking, a structured editor and web synchronization.
scribe: built an open-source publishing SDK for React, Next.js and Vite. handles Markdown/MDX compilation, typography, components, styling and local authoring. currently in public beta.
and then there's my open source work.
i've had PRs merged into HelixDB, Turso, Apache DataFusion, Zed, NativeLink, Zilliz Knowhere and Nix, covering everything from database internals and query execution to infrastructure, editor behaviour and correctness fixes.
i've also got contributions underway in RocksDB, Neon, HydraDB, FalkorDB and Starship, among others.
most of my work revolves around rust, typescript, databases, storage, networking and systems engineering. i've also been getting deeper into ML infrastructure and inference.
i'm looking for a full-time remote engineering role. internships and contracts are on the table too.
my github has all the code, benchmarks and documentation:
github.com/aetosdios27
if you're hiring or know someone who is, hit me up.
reposts appreciated :)
Timi-jah retweeted
Dem ask me salary expectation today, I say N1m.
Dem burst laugh.
I no laugh o. Who dey follow you laugh?
Timi-jah retweeted
Feel like I've spent my whole life endlessly watching Liverpool vs Chelsea in some sort of cup competition




























