Not OP, but I'd start with a one-click way to "install" the PWA apps using an API, e.g. with a banner (like on Android) instead of an item in the share menu.
A single file with a few functions, it seemed a good test to convert it to some other languages with GPT-4 (I tried Python and Ruby). Unfortunately, my access to GPT-4 is limited to the 2k version, and the first function is 4,500 tokens (800 minified, but losing names, comments, and probably the quality of the conversion).
With some language-independent tests in such a repository, you might be able to semi-automatically convert the code into different languages, and continue with code scanning and optimizations.
Your tl;dr shows how text+reader_context can generate the best summaries. Those 5 words are perfect if you know what they did for ChatGPT.
This makes me think that to get high quality summaries:
1) they have to be generated for each individual reader
2) the AI should know what the reader knows
You achieved 2 by imagining what HN people may already know, but the ultimate goal would be to know what the individual reader knows.
And this chain of thought leads to
- Perhaps all AI output should be generated on the fly for the end user with full (relevant and compressed) context.
- Giving AI what we know is extremely dangerous if someone wants to use it for something bad (so we really, really need local AI).
Sure, these are all things people in the industry already know, but there must be a lot of people like me who are just now thinking about it.
A note: "^2" added humor to make the reading light with very few bytes. Perhaps the machine would do this too, if the reader wants.
Only few things make me very very excited and sometimes very very sad like some AI developments. But the exciting part wins for now!
Yeah, I think context is really important for future summarizers. If you think of it like information theory, the goal is what information to convey _for the message to be successfully decoded_. So the amount of information needed is not universal but context-dependent on the decoder (here the reader).
Being able to generate summaries at various levels of depth would be a great efficiency to consuming a lot of content. No more skimming through articles and books written like the author was paid by the character. But if you want more depth, it’s there. Like an LoD slider for information
Love Obsidian. My main problem with it and similar markdown apps for notes is the way they store images and attachments. I find it very confusing to maintain multiple files per note and IMO the only app that nailed it is FSNotes[1] using the textbundle[2] format (with a custom implementation for encrypted notes too). I think it's elegant and future-proof.
But FSNotes is for the Apple ecosystem only and I can't tie myself to a single platform for something so important (I don't need another artificial reason to make OS switching so difficult).
I hope the textbundle feature request[3] gets some love soon. It would be great for Excalidraw files integration too[4].
I'm having high hopes for Bear notes v2 (called Panda in beta). It does the textbundle format which makes complete sense, and also has native pen support on iPads. So actually it is simple, and a joy to use, and also you're not locked in to anyone.
Wow, textbundle on disk instead of the database, right? It would be huge.
Another great feature that Bear and FSNotes share is the ability to insert hierarchy tags like #parent/child
For some reason, I find it perfect to organize notes without too much thinking.
(not op) Logseq is open source and really great in the way it connects notes and highlights pdfs, but the sync part is too “asynchronous”. It works well if you use a single device, but as long as you add something else you have to manually reindex and refresh a lot.
Obsidian is less opinionated on the txt file format and folders too, so I consider it more future-proof.
I started with logseq and now obsidian doesn't work for me anymore. Tried to switch but I am into this small self containing bits now.
Plus journal with timestamps
Syncthing is very good, but the best iOS implementation, Möbius Sync[1], is not comparable with the Android one (the OS limits the syncs, you need a regular notification and so on).
The great things about Logseq are his weakness for me. Everything is so interconnected (you can say: "here put the paragraph of this other note") that I sometimes lose confidence in the system. It becomes too complex. With Obsidian I know that a note is a file. Less convenient but simple and reliable.
Logseq really excels with his outlining mode, I miss it (but I don't like the way it saves states in the markdown file). It has some problems with the code blocks too.
Can you elaborate on the syncing part? Last I tried Logseq, syncing across devices via iCloud was very unreliable. So I gave up. Although I would have loved to replace Roam with Logseq back then. Now I stick to Emacs + orgmode and Obsidian for plain markdown files.
I have a folder in syncthing called "logseq". This folder holds the logseq files.
I have logseq-sync on my phone so it syncs the folder. I also have a Cloudserver which is the spoke and all other devices (2 laptops, the phone) sync it.
Italians have a precise word for that: "supercazzola". It's when someone voluntarily uses this nonsense bs to sell something or simulate some kind of knowledge.
