~seirdy

California, US

https://seirdy.one

My handle is “Seirdy” on most of the platforms I use.

Website, contact: https://seirdy.one

Gemini: gemini://seirdy.one

My preferred forge for personal projects is Sourcehut, but my repositories have remotes for GitHub and GitLab too.

~seirdy/seirdy.one-comments

Last active 20 days ago

~seirdy/public-inbox

Last active 23 days ago

~seirdy/moac

Last active 8 months ago
View more

Recent activity

Re: Accessible documentation 14 days ago

From Rohan Kumar to ~devinprater/fossability

On Mon, Jun 20, 2022 at 12:15:58PM +0500, Anna “CyberTailor” wrote:
>I've read in guidelines for applications:
>
>> Provide an HTML version of all documentation. They are easier to
>> navigate and better convertible.
>
>What are you thoughts on documentation converted to HTML from another
>format?
>
>For example, there are lots of man-to-html converters. Which of them
>(mandoc? man2html?) produce the most accessible HTML?

Ooh, this is a good question. I'm not intimately familiar with the 
different man-to-html converters; I'll have to take a closer look and

Re: [PATCH] Fix word count in post meta 20 days ago

From Rohan Kumar to ~seirdy/seirdy.one-comments

Sorry, this slipped my radar; sourcehut emails hadn't been delivered to 
me for a while. I happened to notice and fix the same problem.

-- 
Seirdy

Accessibility versus Inclusive Design 3 months ago

From Rohan Kumar to ~sircmpwn/public-inbox

I read your post "Framing accessibility in broader terms":

=> https://drewdevault.com/2022/02/13/Framing-accessibility-in-broader-terms.html

It seems like what you're describing in the post isn't (just) 
accessibility, but inclusive design. Accessibility is just one part 
(arguably the biggest part) of inclusive design.

The goal of inclusive design is to make things work for as many special 
needs (especially underrepresented needs) as possible throughout the 
design process, taking into account disability, available hardware, 
languages spoken, inclusive language, etc.

=> https://en.wikipedia.org/wiki/Inclusive_design

[PATCH] Optimize image assets 4 months ago

From Rohan Kumar to ~sircmpwn/public-inbox

Use efficient-compression-tool's Zopfli-based PNG compressor and
jpegoptim to optimize PNG and JPEG inline image assets, respectively.
---
 static/DEC_VT100_terminal.jpg | Bin 2082914 -> 2063016 bytes
 static/avatar-148.png         | Bin 41067 -> 40450 bytes
 static/avatar-512.png         | Bin 363007 -> 357508 bytes
 static/avatar.png             | Bin 21038 -> 9221 bytes
 4 files changed, 0 insertions(+), 0 deletions(-)

diff --git a/static/DEC_VT100_terminal.jpg b/static/DEC_VT100_terminal.jpg
index 9bc744730b7a14b06db5908d8e04d461bfafde86..8a46d9d4ee60e66cc4f5345bffc5c07625da55a4 100644
GIT binary patch
delta 137
zcmWN=w+Vni06<a9Ip;jlEhLDAh3$b$xPfEb4(?#@fAC(p-`^&yLy1!fjXDjQv}n_z
[message trimmed]

[PATCH] Optimize image assets 4 months ago

From Rohan Kumar to ~sircmpwn/public-inbox

I was planning on adding Indieweb avatars to my site, and I like 
optimizing images. I figured I'd upstream the optimizations I made to 
your assets.

In particular I shaved 11kb off your favicon, which could be useful.

bitlang: document dependency on btprnt 5 months ago

From Rohan Kumar to ~pbatch/public-inbox

Bitlang depends on your "btprnt" library, which can be hard to discover 
with a package manager or web search. This should be documented in the 
bitlang README.

-- 
/Seirdy

Request for feedback from server/client implementers using\n non-OpenSSL TLS stacks 7 months ago

From Rohan Kumar to ~adnano/gemini

On Mon, Nov 08, 2021 at 01:57:53AM +0000, tidux at sdf.org wrote:
>It looks like BearSSL is just waiting for the TLS 1.3 RFC to be
>finalized, which is a totally reasonable thing to do.  I would encourage
>a similar level of patience for Gemini mandating TLS 1.3.

TLS 1.3 was finalized in 2018:
https://datatracker.ietf.org/doc/html/rfc8446

This is acknowledged in the first sentence of BearSSL's TLS 1.3 status 
page:
https://bearssl.org/tls13.html

> Long draft periods cause early adopters to have all kinds of wonderful
> broken implementations that must then be worked around until the next

Request for feedback from server/client implementers using\n non-OpenSSL TLS stacks 7 months ago

From Rohan Kumar to ~adnano/gemini

TLDR: skip to the last paragraph ("In conclusion: ...").

On Sun, Nov 07, 2021 at 08:00:29PM +0100, Drew DeVault wrote:
>Hi! We use BearSSL for gmni/gmnlm/libgmni, and intend to move to BearSSL
>for gmnisrv at some point in the future. It does not presently support
>TLS 1.3 and it's unclear when it will ship.
>
>https://git.sr.ht/~sircmpwn/gmni
>https://git.sr.ht/~sircmpwn/gmnisrv

I find the idea of using BearSSL for gmnisrv a bit concerning. As a 
popular Gemini server, switching to a TLS lib that doesn't support TLS 
1.3 could make a lot of capsules TLS 1.2-only.

Re: [PATCH] Fix some spelling mistakes 8 months ago

From Rohan Kumar to ~seirdy/moac

Thanks, applied.

-- 
/Seirdy

Re: [PATCH] CLI: warn if grapheme clusters are detected 8 months ago

From Rohan Kumar to ~seirdy/moac

Thanks; I'll apply this and also add it to go.mod/go.sum.

-- 
/Seirdy