~b @torresjrjr@qoto.org

It's so disheartening when a project's domain name *redirects* to a GitHub README page. There's not even anything worth bookmarking.

Even something as dead simple as this is miles better:
https://soju.im/

@ryu_s0 @YesIKnowIT
Same, though I stick to [:alnum:] (when possible) and a minimum of 32 chars, if not 64. Length is by far the most important factor for its strength.

pan

RE: https://mk.nixnet.social/notes/8wlr1zeof8

Another recent example.

Indent all but the first line of your paragraphs. This is useful when you have long lines which, when wrapped, become hard to dicern. It’s like a cross between a description list (<dl>) and a list (<ul>).

p {padding-left:2rem; margin:0; text-indent:-1rem}

Also, use <dl> and !

Reminder that negative margins and paddings in CSS are a thing, and are quite useful. Some of my favourite uses follow.

More space between document sections:

h1, h2, h3, h4, h5, h6 {	margin: 2rem 0 -0.5rem;}

When viewport width is small (mobile, etc.), <pre> stretches to the walls, and it’s content is aligned with the rest of the document’s text:

pre {	margin: 0 -0.5rem;	padding: 0.25rem 0.5rem;}

https://torresjrjr.com/ast/style.css

https://torresjrjr.com/

@nytpu
Timezones in principle are fine. What complicates things and what should be abolished are:

1. Multiple observed offsets, which include that of DST (daylglight saving time). Certain jumps in offset result in seemingly valid but actually ambiguous or nonexistent datetimes. For example, in "Europe/Amsterdam" on 1995 March 26th, the local time 02:30 was never observed, whilst on September 24th, 02:00 was observed twice (02:00 CET and 02:00 CEST).

2. Certain offset changes result in some timezones skipping entire days! In Samoa "Pacific/Apia", on December 29th at late midnight, their offset changed from -10 to +14, skipping December 30th entirely.

3. Speaking of midnight, some politicians are dumb enough to change offsets on midnight, which causes some midnights to be observed twice. The question is, how do you calculate the start of a day? Bugs bugs bugs.

I have previously worked on a datetime library. There's many more cases to cover. Leap seconds between UTC and TAI (International Atomic Time) complicate things even more, which means certain UTC datetimes aren't even valid.

@retroedgetech
"why not use HTTP with another media-type"

1. One of Gemini's primary points is that user privacy is extremely important. Simply just adding gemini support to browsers gets us nowhere. Even recently, some people have tried to add favicon support to gemini browsers, which has been shut down, because we take privacy that seriously.

2. Gemini is supposed to be minimalist in nature, in all aspects. Gemini comes from permacomouting culture. While it's easy for people in wealthy countries to enjoy the latest tech and high speed Internet, others have to struggle to keep up. Running a high RAM/CPU browser is a luxury.

3. Gemini comes from the free culture community. We have high regards for our software. A new modern fully compliant Web browser would take hundreds of hours and people to make. A gemini browser can be made in one afternoon. That simplicity matters, and is why we have dozens of available gemini browsers, and only ~3 usable Web browsers which aren't reskins.

@Seirdy @ljn @extinct@redroo.ml
It felt good receiving an email thanking me for just my gemini.vim plugin. And I'm a cynical guy. Send "thank you" emails more often.

@xarvos @reedyn
Same. Although I do /archive/YYYY-MM-DD-title because I don't want a bunch of directories in the root directory, and I use a personal ssg which has its limitations. I don't like how long the URL paths can be, but it works fine.

@ieure @Seirdy
Same, that's pretty unique

@freemo
Thank you for hosting and administrating this instance. If I can give back, please let me know how.

@freemo
Amazing! Where will it be uploaded?

Am I deep down a lisper?

@worldsendless
Wow, I've got a headache now. The misuse of the word is evident. I think people mix up "work" and "communication between workers" when using the word.

One should use "concurrently/non-concurrently"?