You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any interest in an app for web, desktop and mobile to allow users to easily use this ?
I think it will be quick to build because the APi is so simple.
The following is my thinking about how a User might want to send files to themselves but also to others
The concept of explicitly making a bundle name might be a little weird for a user. I can see why it's designed this way, because on the receiving side you need to say what you want - ie what bundle name. We can leave the current bundle concept and overlay "subjects".
A "subject" can be introduced which NATS uses everywhere for segregating data routing.
This way you can have a "room" like in many communication apps that maps to a "subject". You can then send a file or a chat message or anything to a "subject".
I am sure there are more elegant ways to do it also but it's just a first stab at the way the GUI and routing to work for making it flexible enough and easy for users to use.
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion @gedw99, I am personally not much of a UI/Web developer. Even something as simple as this would take me quit a bit of time to create. Backend systems is where I dabble.
But of course I'd love if someone with more frontend-fu were to contribute this. I'd be more than happy to collaborate.
Any interest in an app for web, desktop and mobile to allow users to easily use this ?
I think it will be quick to build because the APi is so simple.
The following is my thinking about how a User might want to send files to themselves but also to others
The concept of explicitly making a bundle name might be a little weird for a user. I can see why it's designed this way, because on the receiving side you need to say what you want - ie what bundle name. We can leave the current bundle concept and overlay "subjects".
A "subject" can be introduced which NATS uses everywhere for segregating data routing.
This way you can have a "room" like in many communication apps that maps to a "subject". You can then send a file or a chat message or anything to a "subject".
I am sure there are more elegant ways to do it also but it's just a first stab at the way the GUI and routing to work for making it flexible enough and easy for users to use.
The text was updated successfully, but these errors were encountered: