Moineauworld

Tag: sideloading

Why I’m Done Buying Kindles Permanently | Analysis by Brian Moineau

Posted on by Brian Moineau

I'm never buying another Kindle, and neither should you

I used to think a Kindle was the easiest way to carry a library in my pocket — until my device stopped being built for readers. "I'm never buying another Kindle, and neither should you" isn't just clickbait; it's the honest reaction of someone who’s watched a device I trusted become more about corporate control than quiet, private reading. Recent firmware changes, DRM tweaks, forced updates, and reports of devices becoming effectively useless have made me rethink the whole premise of buying into Amazon’s e-reader ecosystem. (androidauthority.com)

What changed: from thoughtful gadget to locked-down appliance

Kindles pioneered e-ink reading, long battery life, and a genuinely book-like experience. Over the last few years, though, Amazon has tightened the screws: new firmware has introduced stronger DRM, removed features some users relied on, and in certain cases left devices struggling after updates. The result feels less like thoughtful product stewardship and more like product control. (pocket-lint.com)

Forced updates and buggy firmware have bricked or destabilized multiple devices, according to user reports. When a device that once simply displayed text can suddenly fail because of an overzealous update, you stop seeing it as a durable tool and start seeing it as a service tethered to a corporation’s whims. (wired.com)

Why control matters for readers

Reading is a private, low-friction activity. We choose e-readers to remove distractions, extend battery life, and preserve a single-minded focus on the text. That expectation breaks down when:

  • The manufacturer can silently push updates that change functionality.
  • DRM prevents you from backing up the books you paid for.
  • Amazon can remove or alter access to features or formats without meaningful recourse. (pocket-lint.com)

When your books are tied to an ecosystem that can alter device behavior remotely, ownership becomes ambiguous. You may own the hardware, but you don't fully own the reading experience.

Alternatives that respect readers

Not every e-reader treats you like a license holder. Devices and ecosystems like Kobo and Android-based readers (Boox, etc.) prioritize open file formats, library integration, and — in many cases — local management of files. That means you can borrow from libraries, load ebooks directly, and keep local backups without jumping through Amazon-sized hoops. For people who value interoperability and control, these options are more appealing. (laptopmag.com)

Transitioning away from Kindle may involve a learning curve — Calibre and EPUB support are foreign to some Kindle-only users — but the trade-off is a system where your purchases and local files feel genuinely yours.

The DRM problem: more than inconvenience

Amazon’s recent firmware updates introduced stronger DRM layers that make backing up content harder and complicate transferring books between devices. That’s not just inconvenient; it’s a long-term risk. If support for older devices ends (as Amazon recently announced for devices from 2012 and earlier), users can lose features or compatibility overnight, increasing e-waste and effectively forcing upgrades. (pocket-lint.com)

If you value longevity and the ability to archive purchases locally, heavy-handed DRM is a red flag. It means your “library” may vanish into formats and servers you can’t control.

The human cost: frustration, lost time, and distrust

This isn’t abstract. Real readers report waking up to bricked devices, losing access to sideloaded books, or spending hours on support calls that don’t resolve the core problem. That friction chips away at trust. Once the relationship between buyer and device shifts toward paternalistic control, the emotional value of the product drops. People don’t just want features — they want reliability and respect for ownership. (reddit.com)

What Amazon could do (but hasn’t)

There are straightforward, reader-first moves Amazon could make:

  • Stop forced updates that can brick devices or remove core features without clear opt-in.
  • Provide a robust offline-side-load and backup path for purchased content.
  • Limit DRM to the minimum necessary and make archival/export tools available.
  • Offer clear, dated support timelines so buyers can make informed choices.

Until Amazon anchors its strategy around reader rights and device longevity, skepticism is rational.

Alternatives and practical next steps

If you’re fed up and thinking of switching, here’s a quick roadmap:

  • Try a Kobo if you want straightforward EPUB support and library integration.
  • Consider Android-based e-ink devices (Boox, Onyx) if you want apps and flexibility.
  • Use Calibre to manage local libraries and maintain backups of any DRM-free files.
  • When buying, prefer sellers that clearly state region and support policies to avoid warranty headaches. (laptopmag.com)

These options aren’t perfect, but they foreground user control over corporate convenience.

My take

I still love the idea of a dedicated e-reader: the tactile simplicity, the long battery life, the focus. But a device that can be subtly reshaped by the company behind it — sometimes to the detriment of the user — no longer earns my loyalty. For me, “I’m never buying another Kindle, and neither should you” captures a larger point: buy tools that respect your ownership, not products that treat you as a subscription to be managed.

Closing thoughts

We buy gadgets to make our lives richer, not to become pawns in product strategies. Reading should be low-friction, private, and durable. When a platform that once delivered that experience starts prioritizing control over readers, it’s time to look away and support alternatives that preserve the simple joy of turning a page.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.

Related update: We recently published an article that expands on this topic: read the latest post.

Delete These Dangerous Mobile Apps Now | Analysis by Brian Moineau

Posted on by Brian Moineau

Check your smartphone now — these apps are dangerous and should be deleted.

You should read that sentence again and then open your phone. Check your apps. Check what permissions they've been allowed. The FBI has just issued a public warning about mobile applications — especially those developed and maintained overseas — that can quietly collect and leak personal data. Check your smartphone now — these apps are dangerous and should be deleted. This is not fearmongering; it's a practical reminder that our pocket computers hold the keys to our contacts, location, photos, messages, and sometimes banking tokens.

Why the FBI warning matters

Over the last few years, governments and security agencies have flagged concerns about certain foreign-developed apps that request broad device permissions, persistently collect data, or route information through infrastructure in countries with different national security laws. The FBI’s recent public service advisory highlights three recurring risks:

  • Apps that ask for access to contacts, SMS, storage, and location can harvest data about people who never installed the app.
  • Some apps persistently collect information even when they aren’t actively used.
  • Apps that host or hide malware can exfiltrate data or enable surveillance.

The advisory doesn’t ban specific mainstream brands by name in every case, but it does nudge users to be extra cautious about apps that maintain infrastructure or data stores in foreign jurisdictions where local laws may compel that data be handed over to state authorities.

Transitioning from awareness to action is the point: if an app on your phone requests sweeping permissions and you don’t trust its origin, treat it as a red flag.

Which apps you should watch for

The FBI’s message is broad rather than a neat list of offenders. That’s intentional: the risk isn’t just one app, it’s a pattern in how some apps behave and where they store data. Still, coverage from security outlets and tech sites highlights common categories to scrutinize:

  • Free VPNs and “lite” streaming or downloader apps that ask for device-wide access.
  • Lesser-known social or utility apps that request contact lists, SMS, and storage access on install.
  • Apps hosted outside official stores (sideloaded APKs on Android) or unofficial versions of popular services.
  • Apps that solicit device admin rights, accessibility privileges, or persistent background access.

If an app is obscure, newly published, or from a developer you can’t verify — and it asks for broad permissions — it’s safer to delete it and find a well-reviewed, reputable alternative.

What to do right now

  • Open your phone’s Settings and review app permissions. Revoke anything that looks unnecessary (camera, mic, contacts) for apps that shouldn’t need them.
  • Uninstall apps you don’t recognize, don’t use, or that you installed outside Apple’s App Store or Google Play.
  • Update your OS and apps to the latest versions so security patches are applied.
  • Only download apps from official stores and check developer details and reviews.
  • Change passwords for sensitive accounts and enable multi-factor authentication where possible.
  • If you suspect an app has stolen data or behaved maliciously, reset the device and reach out to your bank or services you use — and file a report with the FBI’s IC3 or your local authorities if you’re in the U.S.

These steps reduce the attack surface and limit persistent data collection even if an app is trying to overreach.

How real is the risk?

A follow-up question is fair: how likely is your app to be an active surveillance tool versus just a privacy-invasive tracker? The answer is: both are possible. Some apps are simply greedy for advertising and analytics data. Others — whether through negligence or design — may process and store data in ways that expose it to foreign legal orders or hostile actors. Security researchers and agencies have repeatedly found malware-laden or trojanized apps on third-party stores and even within official marketplaces.

So while the worst-case scenarios are rarer, the cost of inaction is high: identity theft, account takeover, and privacy compromise. Treating your smartphone like a personal device that needs periodic audits is smart hygiene — not paranoia.

Navigating nuance: don’t throw the baby out with the bathwater

Not every app developed abroad is a threat. Big, reputable companies with clear transparency reports, independent audits, and local presence are different from small, opaque developers. Context matters:

  • Look for transparency: where is data stored, how is it encrypted, and what do the privacy policies say?
  • Prefer apps with independent security reviews or a track record of responsible disclosure.
  • Remember that removing permissions or uninstalling apps may break functionality — weigh that against the information at stake.

In short: be skeptical, not reflexively fearful. Make decisions based on permissions, provenance, and behavior.

My take

Smartphone security is a habit, not a one-off action. The FBI’s advisory is a timely nudge reminding us that convenience often comes with trade-offs. A regular five-minute check of permissions, coupled with a quick uninstall sweep for unused apps, will dramatically improve your safety. We can enjoy modern apps while still insisting they earn our trust.

Final thought: think of your phone like your home — you wouldn’t give a stranger permanent access to your house keys or bathroom drawers. Treat app permissions the same way.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.