It is not clear to me that classic confinement is absolutely required
I’m not sure about that either, but whatever the case might be I don’t have the man power to address all the issues, and there are many, the alternative is just pulling the app from the store.
I would be suprised if it was only a small percentage of users who wanted to use
notable to access notes outside their home directory or from external media (and so in these cases for strict confinement plugging the
removable-media interfaces would give the vast majority of users all the access they would need).
I don’t have any numbers on this, but I for one store my notes elsewhere. Supporting “most” users is not good enough.
If you need to spawn a shell process to access the clipboard, then you should plug the
desktop interface and ship whatever binaries you need inside the snap to do this rather than relying on anything from the host environment.
I’m not sure it would be best to ship stuff like xclip (https://github.com/mushanshitiancai/vscode-paste-image/blob/master/res/linux.sh) with my app, and I surely don’t want to spend time figuring out how to compile it myself for all archs/distros. Plus I’m not sure just shipping these sorts of binaries with the app will be ok as far as the sandbox is concerned
I understand that launching external editors is only possible with classic confinement however as
notable provides it’s own markdown editor, I assume this is the most used interface for note editing and so it is not clear to me that spawning an external editor is core functionality.
It doesn’t matter one bit how core this functionality is to the app. There actually are in fact a surprising amount of people who use this feature, the built-in editor doesn’t even have a search bar and surely doesn’t support all the fancy plugins one might have in a standalone general text editor.
Note the making a snap classic does provide a small barrier to installation as there are some users who may not wish to install a classic snap since it does not provide the usual isolation guarantees of strict confinement.
The alternative is a broken snap so I don’t see this as an issue.
As such, I believe if as the developer and publisher of
notable that you really wish for it to be granted classic confinement in light of this, then this can be done to support this external editor use-case, but in my opinion strict confinement would be a better option.
Yes, let’s do it please.
Strict confinement is not a viable option right now, the other option at this point in time is just pulling the broken snap from the store. In the future, when more resources are available to me, I’d be happy to allocate some of those toward trying to make the app work under the strict sandbox if that’s possible.