Re: [damus-io/notedeck] Multi-account panel header (Issue #12)

[William Casarin]

Re: (https://github.com/damus-io/notedeck/issues/12)

On Thu, Mar 28, 2024 at 11:13:31AM GMT, kernelkind wrote:
>I think this is an interesting idea. Instead of one account being
>associated with the whole viewing area of the app, there is one
>account per panel.

One thing we want to be global to the viewing area is a user's mutelist.
This is where you might need an initial login account anyways.

Your mute list would apply to other peoples timelines by default, but
maybe this would be configurable otherwise it wouldn't 100% reflect
their timeline.

>I haven't used tweetdeck before, but I think there should be a place to
>store accounts. Then, when the user wants to add a new panel, they can
>select the account from their storage that they want the panel to be
>associated with

yeah that's the idea, but keep in mind you could in theory use any
profile from your profile database and add it as a panel, like your
friends notifications and timelines to break out of your bubble, but
the accounts in your current login manager would likely be the first
N options.

For panel/lists state, I was thinking there should be some kind of
"profile" configuration. Which may be as simple as a nostr note or json
file that describes it.

I am definitely leaning towards having an encrypted note for client
configuration options. One annoying thing we had on damus was that a
users settings would get wiped out every time they reinstalled the app.
If your panel state, login pubkey set, and client settings were all in
an encrypted note, this would be cool!