Notesnook

Exporting = one-way door File over app = two-way door Do not mistake the map for the territory. Many apps allow you to export your data. That's better than nothing, but not the same as editing files directly. An export is a representation of your data. It's an output of the source. It's a one-way door. The file over app philosophy does not make a distinction between data and file. Both are one and the same. The source is the output, and vice versa. It's a two-way door. Exports are useful if you want to exit the tool. Exports are not useful if you want to directly manipulate your data. Exporting requires your explicit intention, whereas file over app requires no intention at all. File over app means you have possession of your data, it can be directly read and edited with multiple different tools at any time.

I want to debunk the claim that I see a lot around here that Obsidian is "just plain text markdown files" which means "you can take them anywhere and open them with any app" That simply isn't true Yes, maybe the raw text of the notes is markdown, but many other parts cannot be moved elsewhere and opened by other apps: 1. The .obsidian/ directory contains your JSON config with plugins, settings, hotkeys, workspace state, link format, attachment paths – those can't be moved elsewhere 2. Plugin state files – Readwise's path-to-ID map, Templater's settings, Tasks plugin's database, Excalidraw's drawing data – even if plugins can be recreated, these settings cannot 3. .canvas files – JSON, not markdown. They reference notes by path and won't survive a move 4. .base files – JSON-based database/views over your notes. Same path-fragility 5. .excalidraw.md files – markdown wrapper around an Excalidraw JSON blob. Looks like markdown, isn't really 6. The link graph itself – backlinks, graph view, "linked mentions" – all computed from filenames and link references. They survive because the references are in the markdown, but they require Obsidian (or an Obsidian-aware tool) to materialize 7. Plugin-managed folders – Readwise output, Web Clipper output, Daily Notes location, Templates folder. Each is a folder whose contents are owned by an external system tracked in plugin state 8. Sync state – Obsidian Sync, iCloud, Dropbox, Google Drive each maintain their own state about what's where and what's been resolved. Move operations interfere with this state 9. Embedded query results – Dataview queries, Tasks queries, Bases queries. The query is in the markdown; the result is computed live and never persisted So technically you CAN move your files elsewhere, but you'd destroy most of what makes them valuable – the graph, the plugin state, the canvases, the embedded queries, the sync state, and any structural intent encoded in folder placement Which means you're just as locked in to Obsidian as any other "proprietary" app, it's just a hidden lock-in that's obscured by inaccurate marketing Saying "Obsidian is just markdown files" is like saying "your house is just bricks" The bricks are real and moveable – but the architecture, plumbing, and wiring aren't bricks, and those are most of what makes the house function

Our servers are experiencing some downtime. We are looking into the issue. We'll keep you updated

Be honest guys, Do you still write notes while coding?

Privacy and security on computing devices need to become far stronger to protect people from pervasive violations of their rights. Users have their privacy pervasively violated by corporations, criminals and governments. There are endless privacy and security weaknesses in software with exploits of those happening on a large scale. Operating systems, browsers and other apps need to do a much better job protecting users. Enormous progress is needed on both privacy and security. GrapheneOS provides a massive upgrade for privacy and security over the standard Android Open Source Project. GrapheneOS is nowhere near good enough and we have an enormous amount of work to do improving both. Our work is an ongoing process and doesn't have an end point. Privacy and security heavily involve competition between attackers and defenders. Most defenders are making little progress and falling increasingly far behind. Attackers continue improving their exploits of privacy and security weaknesses. Commercial exploit tools are increasingly widely deployed for broad attacks. Software has a very high density of privacy and security vulnerabilities. LLMs are accelerating both vulnerability discovery and exploit development. For most computing devices, defense is increasingly far behind offense. iOS and GrapheneOS are exceptional cases not representative of degrading privacy and security across computing devices. Growing numbers of internet connected devices are incorporated into botnets. This harms the privacy and security of the internet as a whole through heavily pushing it towards centralization behind services such as Cloudflare. Insecure devices without security patches harm the internet as a whole. It isn't only embedded devices but also desktops, mobile devices and servers being used as part of these botnets. It isn't only people with these insecure devices who are harmed. It can get much worse. We're building GrapheneOS to protect everyone's privacy and security. It's aimed at widespread adoption and is highly usable. It's compatible with the vast majority of Android apps. It has major privacy benefits for every user including stopping a lot of data collection by apps and services with a better permission model increasingly addressing being coerced to grant access. GrapheneOS has many users with little technical knowledge and isn't hard to install or use. We're continuing to work on improving privacy, security, usability and app compatibility for all of our users. Contact Scopes, Storage Scopes, per-app Sensors toggle, VPN leak protection and many other features we provde are very important privacy protections. We're building alternatives to the Camera, Microphone and other permissions too. Our major improvements to exploit protections are there to protect user privacy. Privacy depends on security and that's why we heavily work on security too. Contrary to what's often claimed, GrapheneOS is far more usable and requires far less sacrifice compared to other alternatives. Providing far better protection against sophisticated exploits isn't at the expense of that. Our opt-in sandboxed Google Play compatibility layer combines privacy and high usability. We're gradually making replacements for more Google services apps rely on. Location services, network-based location, geocoding and more has already been replaced and much more is coming.

If only GrapheneOS could run on better hardware than shitty Pixels. I am really excited about the Motorola collab.

‼️ It amazes me that Signal, with "state-of-the-art E2E encryption" and a promise that "no one else can" read your messages, fails to turn off notification previews by default, while it has been known for over a decade that Apple stores them cleartext in notification storage.