Hi @Michelist
There’s no stupid question here 
Here a small synthesis of situation:
| Action | Krita 4.x | Krita 5.x With Plugin | Krita 5.x Without Plugin |
|---|---|---|---|
| Opening document | YES | YES | YES |
| Reading Buli notes | NO | YES | NO |
| Saving document | Notes are lost | Notes are kept | Notes are kept |
So you can share a Krita 5.0 file with some BuliNote inside, everyone will be able to open the file.
But only users with plugin are of course, able to read them
Concerning the save action, I can’t do anything for Krita 4.0 (the thing is, I’m just used a functionality implemented in Krita 5.0 to build this plugin)
Notes will be lost if file is saved, because the annotations system is not implemented in Krita 4.x
For a file opened on a Krita 5.0 without plugin, BuliNotes are normally not lost because annotations are part of Krita 5.0 and even if there’s no plugin to read/modify/save them, Krita will internally read and save them without trying to understand content or determinate is annotations are used or not (this is the goal of annotations system in Krita: being able to manage extra data)
After, I said normally because:
- Another plugin than BuliNote can decide to remove them (but ok, consider that if a plugin start to modify/delete annotations made by another plugin, there’s might be a problem in plugin conception)
- Krita can have bug and by myself I can’t guarantee that open/save process will always be safe in future: a bug can always occurs, but I think Krita’s team is very attentive to this and then do what is necessary to ensure users don’t loose any data in open/save file process
Usually this kind of problem if tehy occurs, will be seen in alpha or beta version testing (so if you use a stable version I think it’s safe)
Just, keep in mind that currently plugin is only available on Krita 5, and Krita 5 is only available as pre-alpha for now. So you can use it for test purpose, but it’s not really recommended to use it for production workflow (or do it at your own risk)
Grum99