Feature Request: Remembered, Persistent, and/or Favorited Portals

[gwpantazes]

Prerequisites

• [x ] Put an X between the brackets on this line if you have done all of the following:
  • Followed all applicable steps in the [debugging guide][debugging-guide]
  • Checked the FAQs on the [message board][message-board] for common solutions
  • Checked that your issue [isn't already filed][already-filed]?
    • I've looked and what I'm suggesting is similar and related to these issues: Buddy list #22, Feature Request: Favourites/recent collaborators list #213, Feature Request: Join/share a portal via GitHub users #214, because these issues have to do with remembering a past portal.

Description

Can the Teletype plugin keep a portal and remember it so that the next time the user wants to link the same workspace, no UUID has to be entered?

If the plugin could remember a specific portal for the user and the portal could act like a remembered, persistent, and/or favorited portal, this could save time for a user.

My use case that I can bring to the table is that I'd like to share a portal workspace between 2 (or 3!) of my own machines. Since they are my own machines and I routinely plan on connecting them via teletype each morning and throughout the day, a mechanism to make that process faster and smoother (such as the remembered portal I'm suggesting) would be nicer than having to reshare different UUID's each time.

Expected behavior:

I would want to see a one time first setup step with some kind of toggle where after setting up the portal with the UUID, each successive portal connection does not need a UUID again, since the portal would be remembered from last time.

Actual behavior:

Each portal connection needs a UUID and a brand new portal connection.

Versions

MacOS Sierra 10.12.6

$ atom --version
Atom    : 1.23.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
$ apm --version
apm  1.18.11
npm  3.10.10
node 6.9.5 x64
atom 1.23.1
python 2.7.10
git 2.10.1

[jasonrudolph]

👋 Hi @gwpantazes! Thanks for taking the time to write this up, and I especially want to thank you for sharing your use case. It's always helpful for us to understand the benefit that people are seeking when discussing a feature request. 🙇

And thank you for cross-referencing #213. It is indeed similar, but your use case is different enough that I think it makes sense to for #213 and this issue to both remain open.

As we prioritize future work, we'll be looking at feature requests like this one to determine where we can deliver the most benefit with the available engineering resources (i.e., full-time Atom engineers, community maintainers, and new contributors). For anyone else that discovers this issue: If this is a feature that would make you excited to have Teletype in your life 🤗, then adding a 👍 emoji reaction to the issue body is a great way to let us know.