~u9000

Student They, Them, Theirs u9000@posteo.mx

~u9000/lipu-sin

Last active 8 days ago

~u9000/blog

Last active 8 days ago

~u9000/public-inbox

Last active 9 months ago
View more

Recent activity

User-Agent / X-Mailer (Re: Why was aerc also named aerc2) 22 hours ago

From DJ Chase to ~rjarry/aerc-devel

On Mon, 2022-01-17 at 19:31 -0500, James Pearson wrote:
> Also, I'm sending this email from aerc, customized to my mbsync config
> and sent with msmtp.

Should aerc include the User-Agent and/or X-Mailer header in outgoing
emails? I notice that James' email did not have such a header.

-- 
DJ Chase
They, Them, Theirs

Re: Improving Sourcehut design, accessibility and frontend code a month ago

From DJ Chase to ~sircmpwn/sr.ht-discuss

On Fri, 2021-12-17 at 19:48 +0100, Drew DeVault wrote:
> On Fri Dec 17, 2021 at 7:45 PM CET, Thomasorus wrote:
> > My question then Drew is: do you have strong feelings about
> > how your started and organized antiweb? Or are you open to
> > suggestions about how to do it? I've looked a bit inside the code
> > and it seems very opinionated.
> 
> I am open to suggestions, yes.

I think the accessibility of the site could be improved by reducing the
number of classes. I know this does not directly affect the
accessibility, but relying on classes leads to situations like the
following.[1]

Is streaming a normative protocol expectation? (was Re: Documents with mixed languages) a month ago

From DJ Chase to ~adnano/gemini

On Mon, 2021-12-13 at 20:09 -0500, Sean Conner wrote:
>   Yes, I get the complaint about having to read anciliary sources to
> "properly" implement the protocol (my biggest beef---not many bot writers
> have bothered reading the "best practices" document sitting along side the
> specification [2]), but as I mentioned above, there are a ton of corner
> cases that need to be considered when implementing the protocol that aren't
> mentioned in either document (like text with no whitespace---how do you deal
> with formatting?).
> 
>   -spc
> 
> [2]	gemini://gemini.circumlunar.space/docs/best-practices.gmi

Not strictly on-topic, but I don't think a Gemtext document without

Documents with mixed languages a month ago

From DJ Chase to ~adnano/gemini

On Mon, 2021-12-13 at 23:48 +0100, Philip Linde wrote:
> On Mon, 13 Dec 2021 20:38:12 +0000, Krixano <krixano at protonmail.com> wrote:
> 
> > Again, I was never against making the spec more explicit and up to par
> > with what was intended. What I am for is not judging implementations
> > for using an intended design of the protocol (even if it's not in the
> > spec!) when a spec isn't even final yet.
> 
> It's the document we have as a basis for writing clients. If it's
> wrong, it's wrong. That can be fixed. But telling me that I should dig
> through old gopher holes and mailing list archives just to get a sense
> of Solderpunk's general opinion on streaming request responses, and
> interpret that opinion as a canonical part of the standard is not a
> viable basis for a standard.

Still alive... a month ago

From DJ Chase to ~adnano/gemini

On Fri, 2021-12-10 at 22:06 +0000, Oliver Simmons wrote:
> AFAIK the protocol and format are considered feature-complete, the only changes now are clarification, edge-cases and other minor things.
> 
> Formatting has always been out of the question, as Gemtext is a line-based format.
> 
> Personally I'd like a horizontal rule, but if we added everyone's desires we'd just be back at the Web.

Use an asterism (?) or dinkus (***).

=> https://en.wikipedia.org/wiki/Asterism_(typography)

-- 
DJ Chase
They, Them, Theirs

Re: [builds.sr.ht] Preserve previous build note in Edit & resubmit flow? 2 months ago

From DJ Chase to ~sircmpwn/sr.ht-discuss

On Sat, 2021-11-06 at 08:06 +0100, Drew DeVault wrote:
> On Fri Nov 5, 2021 at 6:26 PM CET, Noelle Leigh wrote:
> 
> > By appending "(resubmitted)" after a blank line, the Markdown
> > formatting can be preserved ([CommonMark example][1]). What if we
> > adopted that format for all resubmitted notes?
> 
> -1
> 
> I think it would be better for single-line notes to have (resubmitted)
> on the same line.

How about writing it like a tag? "[resubmitted] Foobar baz qux."

A Gemini-style proposal (specifically to the harm of using Unicode characters as if they were formatted ascii) 2 months ago

From DJ Chase to ~adnano/gemini

Others have already said what I would say about the rest of this thread,
so I will skip that part.

On Wed, 2021-11-03 at 12:41 +0200, babiak wrote:
> > If Gemtext can ignore the original semantics of the asterisk, the 
> > back-tick, the pound symbol, the equal symbol, and the greater-than 
> > symbol ? then why can't we also do the same with those mathematical 
> > characters?
> > 
> 
> I personally don't recall the pound symbol having any meaning in gemini, 
> I'll have to look through the spec again. However!

Charles is refering to '#', not '?'. '#' is called the 'pound

A Gemini-style proposal 2 months ago

From DJ Chase to ~adnano/gemini

On Wed, 2021-11-03 at 08:08 -0500, Andrew Singleton wrote:
> I'm reminded of the guy that went 'the internet is shit. return to PDF' 
> and everyone else just
> 
> 'PDF is terrible for a long list of reasons.'
> 
> So I ask now the same question as then without further rhetoric. 'Why?'

To be clear: I'm not proposing serving PDFs; I'm suggesting not to serve
HTML or Markdown (which is an HTML front-end, and can include HTML tags
such as `<script>`).

> > On Mon, Nov 1, 2021 at 9:35 AM DJ Chase <u9000 at posteo.mx 
> > <mailto:u9000 at posteo.mx>> wrote:

Rethinking the link line 2 months ago

From DJ Chase to ~adnano/gemini

On Wed, 2021-11-03 at 09:14 -0400, The Gnuserland wrote:
> By the way I was speaking about a predictable behavior of an external 
> resource, the presentation issue belongs only to all those client that 
> are able to display media type content in the viewport.

I feel that this would become the equivalent of HTML's `<img />` tag.
Authors would use `<=` for all link _unless they want them to be
displayed inline_, effectively making `=>` the inline-link tag.


-- 
DJ Chase
They, Them, Theirs

ANN: go-hg — Mercury Protocol client & server library for Go programming language 2 months ago

From DJ Chase to ~adnano/gemini

On Mon, 2021-11-01 at 18:59 -0400, Sean Conner wrote:
> It was thus said that the Great Charles Iliya Krempeaux once stated:
> > Regarding:
> >  gopher://zaibatsu.circumlunar.space/0/~solderpunk/gemini/status-codes.txt
> > 
> > > A good example of this latter problem, IMHO, is "410 Gone" (which is
> > > actually in the Conman Gemini server!).  If this is made official in the
> > > Gemini spec, it sends the message that Real Servers which have a Proper
> > > Full Implementation should remember every one of their URLs which *has*
> > > been valid in the past so it can respond to requests for them with 410
> > > instead of 404.  Similarly a Real Client should remember every 410 it gets
> > > so that it doesn't request them again.  In the real world, almost nobody
> > > does this with HTTP, so it's basically dead weight in the spec.
> > >