~nhanb

Vietnam

https://hi.imnhan.com

~nhanb/mcross-announce

Last active 4 years ago

~nhanb/public-inbox

Last active 4 years ago

~nhanb/mcross-devel

Last active 4 years ago
View more

Recent activity

McRoss 0.5.19 supports Windows again 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-announce

On Windows, McRoss will now fall back to what is basically an 
inefficient polling approach. It's not pretty, but it works.

Also fixed the pointer cursor on Windows I guess.

On a somewhat unrelated note, I considered migrating my own blog to 
gemtext and using some sort of dual html/gmi output but the lack of 
inline links was a dealbreaker. So close!

Re: McRoss 0.5.18 released 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-announce

P.P.S.

 > It's reached the point where
 > I started bothering me so here goes.

I meant where _it_ started bothering me.
Dammit.

McRoss 0.5.18 released 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-announce

Since the introduction of preformatted block alt text, McRoss started 
breaking on an increasing number of sites. It's reached the point where 
I started bothering me so here goes.

Also starting from this release, McRoss will be AGPL instead of MIT.

I plan to tackle gratuitous emojis next 
(https://todo.sr.ht/~nhanb/mcross/8). Personally I think it's an 
unjustified pain in the ass that goes against the no-bullshit simplicity 
that (I think) gemini strives for, but hey, standards are standards.

But I swear the day color escape codes make it into the gemini spec is 
the day I drop this whole thing like a hot potato - thankfully 
solderpunk seems to be sane about it

Re: McRoss distribution 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-announce

Hi Yin,

> (3) I rename my fork "picross" which means a sort of puzzle involving
> arranging pixels into a picture

I vote for option (3). Though I don't have the spare capacity for McRoss
development now, I do wish to come back to it from time to time at my
own pace. Honestly I'm too lazy to review patches now, and at the same
time I don't want to block others (that is, you) from further
development so a separate fork makes the most sense to me. I quite like
the McRoss name, so I hope you don't mind me clinging to it :)

Cheers,
Nhân

Re: [PATCH v2] Download binary files 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-devel

Aaaaaaaand ofc the sourcehut list rejected my previous email because it dared to include an HTML version **even though it also has a plaintext version**. Goddammit Drew.

On Fri, Aug 7, 2020, at 8:50 PM, Bùi Thành Nhân wrote:
> Hi there,
> 
> Sorry for the late response but I'm halting McRoss development for now. I'm currently busy settling in with my new job and, frankly, I'm losing interest in the gemini ecosystem. I might eventually come back to it from time to time (GUI programming is f u n ), but I suggest forking if you plan to do regular development. Thanks for you contributions, they've always been greatly appreciated.
> 
> Yours,
> Nhan

Re: [PATCH] Dark mode 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-devel

 > still be able to remain "simple but no simpler", if every node is
 > customizable

Well my stance is that only constant values should be configurable, not 
custom behavior. As long as we stick to that the config module should 
add no extra complexity to the rest of the code base. For example,
`bg = 'black' if config.dark else 'white'` is custom logic, while
`bg = config.bg` is just a configurable constant. I'm aiming for the 
latter, so while the number of configurable values increases, the 
complexity is actually decreased.

Re: [PATCH] Support alt text for preformatted text 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-devel

 > Do you subscribe to the Gemini list? If so you can catch up with the 
important updates*.

Right, I forgot about that, thanks. Better than nothing I guess.

Re: [PATCH] Dark mode 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-devel

 > What will the format be? YAML, TOML, INI?

I like TOML the most so most likely that.

The idea is to have a mechanism where you define an option once and it 
becomes available as both a CLI arg and a config item, for example 
defining an `h1-font` option should make the application first read from 
`--h1-font` CLI arg, then fall back to `ht-font` key in the TOML stored 
in, say, `$XDG_CONFIG_HOME/mcross/mcross.toml`.

It's not worth implementing 2 different sets of configuration options IMO.

Re: [PATCH] Support alt text for preformatted text 4 years ago

From Bùi Thành Nhân to ~nhanb/mcross-devel

 > In Gemini's new, pending spec

Aw crap, looks like it's promoted to official spec now. Do you know if 
they maintain some version controlled repo of the spec? Implementing an 
evolving spec with neither a changelog nor a diff is... not fun.

There's no excuse for missing the "Any line whose first three characters 
are ```" though. My bad.

Guess I'll comb through the new spec.