Hacker News new | past | comments | ask | show | jobs | submit | maksim-m's comments login

> Log seems like a strong reason to finally switch from Android to iPhone if you're a photography/filmmaking enthusiast like myself

On Android you have mcpro24fps app that supports multiple log profiles, shooting 10 bit video and more.


I've been a long-term mcpro24fps and a user of Filmic pro before that. It's a great app, no doubt about it. The issue is not the app, but the OEMs who makes things difficult, artificially limiting the capabilities of the devices and even removing features in updates. Nothing is consistent and each device works differently from the next one, even from the same manufacturer. A long running joke in the McPro24fps Telegram chat is to never upgrade!


> Should Your Notes Be End-to-End Encrypted?

Yes. That's why I use Joplin (which is free and open source btw) and not some proprietary freemium app that to explains me that I don't necessary need E2E encryption for my notes.


Do you have something that allows you to publish that as well?

Use case - I want to keep some notes for myself e2e on my laptop & phone but every now and then I'd like to publish a few of them under a pseudonym anonymously on the internet.


IMHO this is not the role of a note app. For this, get a private blog or use Medium.


Hit the Share button in Joplin and select your blogging app of choice.

Note-taking and publishing are different enough to deserve being separate apps, especially when the notes can contain private material.


One of our guiding principles with Supernotes is that data staleness is an undesirable property and so we're trying to build a markdown-notecard-first (read: portable) and sharing-first (read: no staleness) notes app.

I touched on the example of a blog in the article in the context of E2EE, but let's forget about E2EE for a second and just look at it from a stale data perspective: you click the share button in Joplin and publish to the blogging app of your choice. Later a reader on the blog points out a few typos so you make some changes in your blogging platform. Now you have a version of your blog post on Joplin that is stale unless you manually copy-paste your changes from the blogging platform back to Joplin. Or you make the changes in Joplin and need to manually republish to the blog somehow.

But what if instead your notes app was a single source of truth and making changes there automatically propagated everywhere you needed – whether semi-privately in the Supernotes collection of a friend, in a shared Notion workspace with your team, or published to the broader internet. That's (one of) our goals with Supernotes.


Yeah. It's called a web server and it's been around for ages, try it out some time


Relax


> Yeah. It's called a web server and it's been around for ages, try it out some time

come on, now.


What?


Trilium Notes offers this: https://github.com/zadam/trilium/

Note: I run a paid 3rd-party synchronization service for Trilium Notes that would offer the publishing part of what you mentioned easily, without setting up a cloud server: https://trilium.cc/


For this I use Standard Notes and Listed.to for E2EE encrypted writing as well as one-click sharing to either my little blog, or an anonymous link.


If you sign up for joplin cloud you can publish your notes. https://joplinapp.org/plans/


The best I have found so far is Notesnook Monographs [0].

[0] https://monograph.notesnook.com



According to Google, Gboard uses Federating Learning to train a model on user data on the local device, so no sensitive data is not sent to the server. Only the gradients are sent and aggregated on the server. https://research.google/pubs/pub47586/


I can recommend Joplin app. https://joplinapp.org/

It's:

- Free and open-source

- Cross-platform

- Support end-to-end encryption

- Synchronization via NextCloud or Dropbox

- Allows you to import notes from EverNote

- Has a web clipper


You can also sync to the filesystem. I do this so I can use syncthing to synchronize my notes w/o the cloud and duplicati to back them up :)


Then Signal have to store your social graph on the server in plaintext. It's not what's expected from a private messenger.


Storing the social graph is not required at all. For example, Threema creates a random alphanumeric identity that is linked to your public key (instead of linking the phone number directly to your public key). It's possible to optionally link your hashed phone number and/or e-mail to your identity. Finding your friends can be done by comparing hashes of the data in your address book with the hashes linked to the identities. Those address book hashes never need to be persisted anywhere on the server, an in-memory comparison is sufficient, then the data can be thrown away. If you wish to stay anonymous, just ask people to add you manually by typing in your identity (or by scanning your public key QR code, which also results in verification / trust).


Could you elaborate? I don't follow your reasoning here.


> Federation isn't possible with this protocol, which kind of sucks

Moxie has a blog post explaining why Signal won't support federalization: https://signal.org/blog/the-ecosystem-is-moving/

"After three weeks, sealed sender now represents over 80% of overall Signal messaging traffic." https://twitter.com/signalapp/status/1075918894521495552

This would be impossible to achieve with federated protocol.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: