this post was submitted on 05 Jul 2026
11 points (70.4% liked)

Privacy

49858 readers
599 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 6 years ago
MODERATORS
 

Posting here because the whole reason Compass exists lines up with why a lot of you are on Lemmy: no ads, no tracking, no account, no Big Tech middleman.

It's a news aggregator that pulls public RSS/Atom feeds and opens articles in a built-in reader that strips out the scripts, ad slots and tracking pixels before rendering. Everything — your feeds, saved stories, settings — lives on your device. The app collects nothing.

Android, closed testing right now. If the ethos resonates and you'd like to test, DM me the email on your Play account and I'll add you. Feedback from people who actually care about this stuff is worth more than a hundred casual installs.

you are viewing a single comment's thread
view the rest of the comments
[–] DiscoDan_IN_NZ@lemmy.world -1 points 2 weeks ago (1 children)

This is a genuinely good set of points — let me take them honestly rather than pretend I've got a slick answer to all of them. "Tons of RSS readers already" / lite.cnn.com / gnus.el — completely fair. I'm not claiming to reinvent RSS. What I was actually after was a specific combination: curated NZ outlets working out of the box, a political-lean indicator on each source, and — the main thing — an article view that strips the ads and trackers rather than dumping you into a bloaty page. If you already have a reading setup you like, I'm honestly not going to pull you off it, and that's fine. Why a built-in reader instead of a webview — this is the crux, and it's the opposite of "yet another special text UI for its own sake." A webview loads the page with its scripts, ads and tracking pixels — which is exactly the thing I was trying to avoid. The custom reader exists specifically so none of that executes: fetch the page, extract the article, discard the rest, render clean. The text UI isn't the goal; killing the trackers is, and a clean reading view is the byproduct. Could it be a static page with local storage / a local httpd — you're close, and you've basically described what it is under the hood: it's an HTML/JS app. The reason it's wrapped natively rather than being a pure browser page is CORS — a plain static page can't fetch arbitrary third-party RSS feeds from the browser; the outlets don't send the headers that would allow it. The native shell is really there to make the cross-origin fetch possible, plus give durable local storage. A local httpd would work for you personally but isn't something I can ship to non-technical phone users. Headline-only feeds + bot detection — this is the sharpest point and you're right. Some feeds are headline+summary only, and some article pages sit behind bot-detection that a straightforward fetch won't beat. I don't try to defeat that — when extraction fails or a feed is summary-only, the app is honest about it: it shows the summary and offers to open the full page externally, rather than pretending it scraped something it couldn't. Full "orchestrate a real browser to get past bot walls" scraping is a road I've deliberately not gone down — it's an arms race and it's exactly the kind of heavy machinery I was trying to get away from. The name — ha, fair. "Compass" is not what you'd call unclaimed. Noted. F-Droid / no Play account — totally understood, and same as I said to another commenter: an APK and eventually F-Droid are the direction I want to go once it's stable. No worries if you'd rather wait for that. Appreciate you engaging with it properly. 🧭

[–] solrize@lemmy.ml 0 points 2 weeks ago (1 children)

The webview isn't supposed to show the bloaty page directly. Your client would retrieve the bloaty HTML, strip the junk out or maybe completely reformat the page, and then show the "purified" page in a browser. I did this for a while with local proxy cgi's but they eventually stopped working due to AI bros over-scraping everything. Also, are you going to write custom de-bloating for different sites that your client reads? It helps quite a bit. I can send you some of mine if you want.

Yes a normal web page can't pull arbitrary feeds but I had thought there were permissions you could give to enable that. Like I think Manifest v2 lets you turn off the cross origin check, so you could write a Firefox extension. But, they shut down Manifest v2 in Chrome in order to prevent ad blockers from working.

[–] Greg@lemmy.ca 3 points 2 weeks ago

It sounds like you're chatting with someone else's coding agent