I want to read your long form note, relink it?
personal use cases for onenote:
journal - sometimes I just want to write some thoughts down, document a mental wank. these can be 1000's of words, but I generally dont go back and edit them. sometimes I do publicly post them, either in complete or partial form. still, would assume them to be private at first.
text data save - for instance, I have a note of common commands I use on my node. I also listed all the apps on my phone, before switching to Graphene. And all the apps I use on my main PC (preparing to switch to Debian). these are also private, but not necesarily secure. some times I do want to edit them, but often edits are additive (appends)... however, having many historic copies of the same note, just with less info, might not be great, unless not visible, thinking maybe more like repository style.
secure data save - yes, bad practice, but I save passwords for systems of lesser importance. I might save seed phrases for hot wallets I dont care about. if anything, I expect these to be more editable, often passwords get updated on a regular basis. the convenience factor here is both long term and short, because I can use onenote on different devices. so, save a password on device 1, open onenote on device 2, copy paste password where wanted. there are other ways, but onenote has been very easy and accessible.
work uses:
process documentation (to share with team) - more or less wiki-style documentation. can be as simple as a text note or something more formatted and graphic, with screenshots, etc.
data repository - list of servers, table of accounts, common commands, code snippets, etc. focus is on editabilty (by team) and shareabilty (among team) and accessibilty (across networks, close enough to closed networks, etc).
secure data (try not to use onenote, but it happens): things like non-critical passwords lists, other private info that might be limited to a personal scope of access, or could be team access.
theres some other things I use notepad++ for, especially as unsaved files that still persist across even force closes of the app. but these are frequently edited.
so across all of this are the concepts of editing, scope of access (both read and write), and being available across many systems.. I see nostr being able to deliver on many of these use cases, with some work on key mgmt and editing methodologies.
consider an encrypted note that contains one seed phrase of a corporate multisig. with access built in for n private keys (representing a group of individuals within an access scope). and that seed shifts to a new seed every n days (I think this is something that doesnt really happen today, but is worth considering). how could nostr do that? I think it could, fairly elegantly. I think bitcoin could do it onchain, actually, but probably usnt necessary...
ok, that last one isnt a onenote use case, per se, but could be one if onenote was regarded as relatively secure.
