Malibou

Back on X after 12yrs IT/CTO/IoT founder. Solo grind: sharing stinging lessons that free you (tools/hacks/real talk). Solopreneurs who get it. Mindset first.

[Malibou @MalibouGeek]

Always compare yourself to who you were yesterday, not to who someone else is today.

Fill your own gap for tomorrow.

[Malibou @MalibouGeek]

Hey @Microsoft, instead of trying to force Copilot into every single corner of Windows and Office... funny how nobody thought to deploy it on @LinkedIn first?

After all, that's literally where people network.

Maybe you could take inspiration from what actually works right here on @X ? No?

(Disclaimer: Please don't send a recruiter to my DMs - 😎).

[Malibou @MalibouGeek]

🤖 Get KlynPix on Android and start sharing safely:
https://t.co/JsTDtZONS2
🍎 On iOS? The waitlist is open: https://t.co/v1M8W32Iuf

[Malibou @MalibouGeek]

People often wonder if @flutterflow can handle complex, production-ready architectures.

Meet KlynPix. 🛡️

We pushed the engine to its limits to build a strictly local-first privacy tool. It uses on-device ML models to blur faces and custom Dart processing to scrub EXIF data in milliseconds. No servers, no lag.

Proof that you can build way beyond standard CRUD apps.

Play Store link in the first reply 👇

#FlutterFlow #BuildInPublic

[Malibou @MalibouGeek]

Project sample here:
https://t.co/44r8wZPkJm

[Malibou @MalibouGeek]

I finally completed Android Developer Verification (ADV) for two Flutter apps using delegated signing with Samsung Galaxy Store—in under 30 minutes—so I wanted to share a few lessons learned.

The process turned out to be much simpler than I initially expected.

✅ Built a minimal Flutter project.
✅ Used the exact production package name.
✅ Placed https://t.co/grlCY3ZJIf under:
android/app/src/main/assets/
✅ Built a release AAB.
✅ Uploaded it to Samsung Galaxy Store.
✅ Retrieved the Samsung-signed artifact.
✅ Submitted it to Google Play Console.

Both apps were verified almost instantly after the Samsung → Google Play step.

The biggest takeaway?
I initially assumed https://t.co/grlCY3ZJIf belonged in Flutter's root assets/ folder. It doesn't.
The official Android sample places it under:
android/app/src/main/assets/

That small detail can save hours of debugging.

Hopefully this helps someone going through Android Developer Verification with Flutter or another delegated signing provider.

And hopefully this saves someone a few hours too!

Happy building! 🚀

[Malibou @MalibouGeek]

@InterestingSTEM @grok give us more infos

[Malibou @MalibouGeek]

@markproduct Stop building, start learning from ur users then start marketing—Or not

[Malibou @MalibouGeek]

@cheaf25master That’s the focus mode 🤷🏻‍♂️

[Malibou @MalibouGeek]

Instagram & Co strips location data from your photos to "protect" you. What they don't say: they secretly keep it for their own ad servers. 🛑

I got tired of my friends feeding Meta with hidden home GPS data, so I built KlynPix to wipe it before Big Tech gets it.

🛡️ 100% local-first privacy
📍 Wipes EXIF data instantly - Hidden metadatas
🎭 Auto-blurs faces on-device
📲 Hooks directly into your native "Share" menu

Built by a solo mobile dev. Free forever.

Join the waitlist to get Early Beta Access & your "Founding Member" status: https://t.co/eAuwGjNaqd

[Malibou @MalibouGeek]

@MicroLaunchHQ 0 is still <100 😉
Launching soon...

https://t.co/v1M8W32Iuf

[Malibou @MalibouGeek]

@freemius Guess it 😉
Hint: https://t.co/v1M8W32Iuf

[Malibou @MalibouGeek]

Sam is 100% right. The "pet account" blind spot is huge. People think hiding their face equals privacy, while their EXIF data broadcasts their daily dog-walking route.

I built KlynPix exactly for this: a local-first utility to wipe GPS data before your photo ever touches the internet. https://t.co/eAuwGjMCAF

[Sam Bent @DoingFedTime]

#OPSEC365 120/365

Photos of your pets often reveal your location and routine.

That daily walk photo has metadata showing your neighborhood route. The vet check-in confirms your area. The microchip registration contains your address. Pet accounts geotagged at dog parks reveal where you spend weekends.

Pet photos carry the same GPS metadata as anything else you post, plus the pattern of your walking routes and vet schedule. Pet accounts seem harmless because they're not about you, but they contain the same metadata and geotagging as personal photos. Remove EXIF data before posting. Avoid tagging specific parks, vet offices, or groomers.

[Malibou @MalibouGeek]

@rohangotwal The best UX anti pattern
Did you see users as dumbs?

[Malibou @MalibouGeek]

@GithubProjects Buggy tracks v99.9

[Malibou @MalibouGeek]

@PythonPr X is a social network, can’t be printed
😁

[Malibou @MalibouGeek]

@GithubProjects And slowly going out of control 🤷🏻‍♂️

[Malibou @MalibouGeek]

After MVP, most startups don’t break because of technology....

They break because they keep shipping… without changing how they operate.

✅ Pre-MVP, speed fixes everything.
⚠️ Post-MVP, speed without structure creates friction.

As a Fractional CTO, this is the most common trap I see: scaling features before setting a clear way of working.

When the team grows: – decisions get blurry – priorities change too often – delivery slows down, even if everyone is busy At this stage, I focus on a few simple questions:

👉 Who decides what?
👉 How do ideas go from “nice to have” to production?
👉 How are teams organized to actually move fast?
👉 What are the few technical rules we don’t break?

Nothing heavy.
Nothing corporate.

Just enough structure so teams can move faster without burning out or breaking the product.

Post-MVP scaling is not about adding more features.
It’s about building a system that allows teams to ship consistently as the company grows.

That system is what I call the Operating Model — v0, built for initial traction.

Not a document.
Not a process factory.
Just clear rules on how decisions are made, how teams work, and how value gets delivered as the company scales.

This is usually the moment when founders realize they don’t need “more developers”… they need clarity.

[Malibou @MalibouGeek]

Grok is a little busy for now… Here is his answer

Hey Malibou! Thanks for the ping 👋 Quick fact-check on the fresh WhatsApp/Meta lawsuit (filed ~Jan 24-25 2026, San Francisco federal court).

Bottom line: Serious allegations, but **unproven** so far and strongly denied by Meta.

- WhatsApp's end-to-end encryption (Signal Protocol) is real and has been audited multiple times since 2016. Private 1:1/group messages stay encrypted – Meta doesn't hold the keys to decrypt them in standard chats.
- The suit claims Meta can "store, analyze & access virtually all" private messages, based on anonymous whistleblowers saying employees can request content via internal tools. No public technical proof yet (no logs, no code leaks).
- Meta's reply (immediate): “WhatsApp has been end-to-end encrypted for a decade. This is a frivolous work of fiction.” They’re threatening to countersue.

What Meta DOES collect (confirmed):
- Heavy metadata (who ↔ who, timestamps, IPs, device info) → gold for ads & profiling
- Unencrypted cloud backups (Google Drive/iCloud – most users leave this on)
- Business API chats (not always full E2EE)
- Public content (channels, statuses, link previews)

Verdict: Not the "they read every message" apocalypse the clickbait implies – no mass E2EE break proven. But privacy isn't bulletproof (metadata + backups are real weak spots). Looks similar to past suits that fizzled without hard evidence.

For bulletproof privacy → Signal (same crypto, minimal metadata), disable cloud backups, or Threema/Session.

Happy to dive deeper if you want sources or more details! Stay vigilant 🚀

[Malibou @MalibouGeek]

@XFreeze Hey @grok what about this?
A quick facts check please

[Malibou @MalibouGeek]

@GithubProjects I can’t figure out why—Asking for divorce?