Please hold on. kde-frameworks-5-core18 is owned by another publisher (the KDE project) and that publisher has not requested auto-connection for the world and unlike the gnome content snaps, there is no statement from them stating their pledge to not break consumers (this is completely within their right-- it is their content snap to be used by their snaps).
@roadmr - the point of content snaps is to have them auto-connect from the same publisher, not arbitrary publishers. For arbitrary publishers, we either need a global auto-connect or both sides need to acknowledge the risk (which is not good for users if both sides say “sure, I’m fine to break/break you”).
For all the same reasons as discussed in lyricfier, I vote -1 to auto-connect this interface. ksnip could easily break at anytime since the kde team has not declared to not break consumers and the store granting this would be inappropriate since that would be the reviewers vouching on the store’s behalf that ksnip won’t break. As reviewers, we can’t make that guarantee and it would be unfair of us to place that burden on the kde team or ksnip’s users.
If the kde team wants to seek a global auto-connection, that should be done elsewhere. Otherwise, ksnip should probably instead use kde-frameworks-5-core18 as a build snap or fork it. In this manner, the ksnip publisher can release on their own cadence and QA and not risk breaking its users.