Follow

@nolan

Hello, Nolan, good morning!

I wanted to ask a couple of questions - regarding and the configuration of instances in use.

All of the info for these (instance name, user name and authorization token, user selected colour themes, etc) is as we know saved in the user's browser. But that makes it non-portable, even in the same machine, if I wanted to switch to another one.

Which is the case, currently, for me. I have about 20 instances configured in Pinafore, and it really makes it easy to switch and visit whichever I want, anytime.

Could you consider an export or save feature for Pina, which would export a text file with :

  • instances names, and selected colours.
  • maybe the username as well?
  • and save this in the same order as we have in the current pina setup?

With an export like that, we could later import into another browser; maybe even a different device, and keep the full list, order, selected colour schemes.

All we would need is to re-do the authorization in the new device, which is safe as it depends on the user knowing the password.

Thank you for considering this!

tools, Pinafore is the client of choice for the digital .

@rgx It's an interesting idea, but it's also a security risk. The file you export would contain the security tokens giving anyone full access to your account. I understand the problem, though – this also applies to all of Pinafore's settings.

As a temporary workaround, you can copy LocalStorage from one Pinafore instance to another, as long as you have access to the devtools.

E.g.:

copy(JSON.parse(JSON.stringify(localStorage)))

Object.assign(localStorage, <paste>)

@nolan Thank you Nolan!

Please consider the idea, I know exporting the access tokens is a bad idea - but restoring the authorizations is the easy part (with a password manager, quick work to re-login to each instance in the new device or browser).

I will try the copy you suggested, if i can figure out how, lol. I am learning. Thank you!!

@nolan And I am just experimenting with the object inspector and found the column width control.

Would you consider offering a wider center column for devices with the wider screens? More space to read and write.

I understand the need for the column in the center, to support the mobile devices.

But on my 1600x900 display, Pinafore so far uses 602px for the center, content Div. Here's a snapshot with it at 802 px instead. Maybe a user selectable option, in the future?

Took two snapshots and attaching them. The default setting gives me 602px wide Content area; about 40% of my viewport.

Second one, shows 802px on center, now it's 50% of viewport.

For small, single line toots it probably doesn't matter, but for people reading longer posts, it could be nice?

@rgx I guess my thought process was that people could use the zoom-in, zoom-out controls in the browser? Admittedly this also increases the font size. Maybe font size or column width could be a separate setting.

@nolan I did a little experiment, and took this editor screenshot.

As @lanodan mentioned, there's a time tested suggested maximum width, in characters, at about 80 per line for best readability.

Took a screenshot of Pinafore, running at normal screensize, and I see about 66 chars or so; I compared that with what 80 chars would read.

Having a responsive design class for the wider screen devices would allow setting their central Content panel wider, in percentage of the screen, plus define their char width - I am thinking at 80 em?

@nolan And I did an experiment with zooming. Saved a screenshot just now, and at 133% zoom on my system, the central Content column is just over the 800 pixels I tried yesterday (via css hot edit).

Copied the highlighted line, which is this toot, and on my text editor counted the displayed chars.

Zoomed pinafore view at 150%, 120% same results :

"With the layout shown in the first post in this thread, I think it's |"

70 chars shown, a line copied from a post in a regular toot, in a thread.

When the Toot is clicked on, a larger version displays in pinafore - larger font, less chars :

"*Gargron I have a 1600 pixels wide screen - why let"

52 chars shown, in this case.

(note: the linked toots display wider if clicked, opening to mastodon default web client. There they seem to display 82 chars per line if I zoomed to the same 133%. Their default font, no zooming, is pretty small, and displays 88 chars per line or so. Screenshot below.)

At 120% zoom, the mastodon web client content panel is near 800 pixels wide (785px), and I count 88 characters on a line.

Sign in to participate in the conversation
Muensterland.social

Ein kostenloses und werbefreies soziales Netzwerk für Personen aus Münster und Umgebung - und auch alle anderen!