I’m the nostrability product janitor. 
 
nostrability repo contains negative interoperability issues like the one you run into.

There are many of these.

If we dont systematically catalogue, these wont be fixed. If these are not fixed, the average normie big tech user who expects things to “just work” in app, and across apps will drop off.

Specifically the “hop” between apps is a user friction point. If the hop friction is too high, users wont bother with using the strength of nostr - many apps, and nostr will recede into obscurity. 

Now that I write this, there may be perpetually unmaintained apps. 

Maybe its worthwhile to catalog these to a high friction list to warn devs, and end users of potential for a crap experience. 

 Per fan’s request. 

 Fan as in fanquake? 

 Oh  I meant per Dan”s request. @WedgeSocial 

 I am a fan of both their work! good observation Hodl 

 This is a good strategy for public service.  But can be difficult
If the devs who are targets are not paying attention 

 I cannot guarantee human action of others, and I have been bringing up to the attention of devs various issues their app is involved with. 

Thus far, many devs have been receptive and worked together with their counterparties to resolve multi-app bugs, negative UX behaviors. https://image.nostr.build/6941ccc7bd3e54e2c05958756ff1818fd82ae550e8ad36dda5975cde9453cf0f.jpg https://image.nostr.build/a953542b1f42f250d8e3b0f354e8f3f0fe69d50b5f1ad36128f05f2d1835e685.jpg https://image.nostr.build/03c8f9f9ccb3059f8866d2ce779ad444b40430f7fff06dce00574c8bcc4cde6f.jpg  

 Yes that is because they are full time paid by grants and have lots of free time. Good for them. I am not so if i get spammed, all you will likely get is no response for a long time😅 

 I hear you. 

There are quite a few devs and other contributors who are active, and are not sponsored