Rob G. boosted
Rob G. boosted

@joaopinheiro

Pois... :-D

Parece que funciona -- apesar que o Zotum pensa que meu endereço aqui é esse 'Will_De' por alguma estranha razão, lol....

Bom fim de semana!!

Just read this on Reuters - I had seen some of the photos yesterday on The Guardian, and found it quite touching.

"The man who saves forgotten cats at the Fukushima nuclear zone"

widerimage.reuters.com/story/t

@yann2 @joaopinheiro E esse comentário chegou aqui tambem - pelo menos posso vê-lo.

O endereço na mensagem não parece ter sido reconhecido como válido pelo Hub, que mostra vários dos meus outros endereços, mas não o @rgx como deveria...

@joaopinheiro Good afternoon, boa tarde! E bom fim de semana...

Testando enviar mail direto para seu hub.

cc: @yann2

Windows 10, change System Font for a better one?

Something I have done, and planned to post about

A simple change which I am really enjoying. For Windows 10 users, the default System font is the new 'Segoe UI' font and its variants, all included in the default Windows 10 install.

However, it IS possible to change it, to whichever font you feel would be more readable, or prettier, or that you prefer for any reason.

A quick search will reveal many pages written about this topic, and even videos for those who prefer that form of presentation.

Why change it?

Because, there are better alternatives. Microsoft itself developed at least two families of Fonts in the 1990's which were specifically designed and optimized for on-screen reading. They are outstanding for that. These fonts are:

Georgia - a Serif font, which I would recommend as a replacement for your default Browser font, instead of the plain Times New Roman usually configured by their developer.

Verdana - a Sans Serif font which is an improvement on the Arial font, and could also be adopted as a better one for Browser default. (Arial and Sans being usually the browser predefined picks).

And now here it is. A Guide on how to easily improve system wide readability...

That is the topic of Today's Blog Page

information gathering for us all..

is beautiful.

Rob G. boosted

@joaopinheiro@libranet.de @joaopinheiro@zotum.net

Hello João, thank you for the post -- I am glad you are enjoying Zot , and will read it with attention later. Very good to see your perspective.

I have not logged into the other two accounts you tagged me with in the post, curious to see - but their logins are stored in pinafore in another browser, which I am trying to avoid using for now.

Thanks, have a great Sunday, will get back to you on this. 👍🙂

@globcoco this allows Pinafore to run in its own separate tab, and is quite neat! Writing from it now.

Super easy...

@nipos Wonderful, logged in with no problems now. 😊✔

What a delight to be back in my comfortable Pina client. 👍😎❤

@nipos

You are very welcome, and thank you for the excellent service, Niklas.

Have a good night!

Hello Niklas! @nipos

Good afternoon, hope all is well with you.

I have just installed a PWA version of the Pinafore client I always use, and am having trouble adding my Muensterland.social account to it.

This is a new install, no instances are configured; the other install worked fine yesterday, it has an access token.

Trying to add MS to Pinafore gives the error message shown in screenshot. I have added a couple of other instances, and it's working normally. I think the problem here is a CORS issue.

Nolan has a page for admins explaining it ;

github.com/nolanlawson/pinafor

We need the access control I think; I don't see it on the source code for this page as I write, logged in via web client to the instance.

Thank you!!

of choice for me

recommended, tools of the trade.

Rob G. boosted
Rob G. boosted

Installing a PWA app locally - SUPER Easy

I had read a bit about this, and tried, to get a local copy of Pinafore fediverse client. With NodeJS and Nativefier, it works in some cases, but didn't for Pinafore in my case.

Tried again to find a solution and just discovered this page - and it worked, it's super simple, no NodeJS or black magic neeed. Really.

I am writing this via my Developer branch Pinafore client, installed from dev.pinafore.social/

(the regular, stable version is homed at pinafore.social/ )

How to do it ?

Read the article and get it installed - only caveat is you will need a Chrome family browser to do it (not the dreaded Google Chrome spyware). I suggest Bravo browser, which I recently started using and am quite impressed by. Or the new Chromium based version of Microsoft Edge, which is quite good too.

Seriously, it takes no effort at all.

Article is here : androidheadlines.com/how-to-do

Recommended reading. #pwa #chromium #webapp #pinafore

Wishlist - wider rez screens layout support?

In the lovely Pinafore client.

As a laptop user primarily, it's been an uphill battle getting good clients for which recognize and respect the fact we have lots of pixels.

Responsive Design is great - I have started learning and practising it, understand the logic. Good stuff.

But, honestly - the internet has too much to offer for real work to be performed in a mobile device. Content creation, we need better software that allows us to use what's in our chosen platform.

Case in point, Wide Screen Displays.

Which I have made various attempts at getting improvements for. I explain and show screenshots of some solutions and ideas on the post.

Pinafore Responsive Layouts

Shows 3 classes of devices, see screenshots in blog post.

  • Mobile ( 320x480p) portrait/landscape
  • Small Tablet (600x800p) 2 modes also
  • Tablet (768x1024p) standard iPad res, 2 modes also

If we could get a couple of added new, wider classes it would be wonderful. Could we, please ??

That is the topic of Today's Blog post

on the crusade for better wide screen devices support.

(Uphill battle, but we shall persevere)

@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.

@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?

@lanodan

Here's the topic with the mockup Pinafore 2 panels.

I am writing a blog post version of this new thread, and will include this as a mention too.

@nolan

Show older
Muensterland.social

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