~fkfd

Shanghai

https://fkfd.me/x

~fkfd/picross

Last active a month ago

~fkfd/gemini

Last active a month ago

~fkfd/misc

Last active 6 months ago
View more

Recent activity

Re: [PATCH] TOFU: Create file if it didn't exist a month ago

From Frederick Yin to ~fkfd/picross

On November 30, 2020 5:28:27 AM UTC, Zach DeCook <zachdecook@librem.one> wrote:
>---
>
>Notes:
> Note that we should probably support ~/.local/share/gemini/known_hosts
>(but that uses a different fingerprint format, so we may have to mind
>for backwards compatibility)
>
> picross/tofu.py | 2 ++
> 1 file changed, 2 insertions(+)
>
>diff --git a/picross/tofu.py b/picross/tofu.py
>index d2fc3d8..f188e9a 100644
>--- a/picross/tofu.py

Re: picross doesn't launch 2 months ago

From Frederick Yin to ~fkfd/picross

On November 10, 2020 11:55:43 PM UTC, Bopol <bopol@e.email> wrote:
>Hello,
>
>When I launch picross (build from source), I get this error
>
>Traceback (most recent call last):
>   File "/home/USERNAME/.local/bin/picross", line 33, in <module>
>     sys.exit(load_entry_point('picross==0.6.1', 'console_scripts', 
>'picross')())
>   File 
>"/home/USERNAME/.local/lib/python3.9/site-packages/picross-0.6.1-py3.9.egg/picross/__main__.py",
>
>line 3, in run
>   File "<frozen zipimport>", line 259, in load_module

Re: McRoss distribution 4 months ago

From Frederick Yin to ~nhanb/mcross-announce

On September 11, 2020 3:19:20 PM UTC, "Bùi Thành Nhân" <hi@imnhan.com> wrote:
>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 :)
>

McRoss distribution 4 months ago

From Frederick Yin to ~nhanb/mcross-announce

Hi, hope you're more accustomed to your new job. I'm short of time, I
guess you're too, so I'll keep this short.

Major changes I've made to my fork of McRoss:
* tabs
* TOFU
* 1x status codes (input)

Still, though, with all these changes made, I thought it would be better
for the community if my changes were pushed upstream on PyPI. Right now
in my documentation only the `poetry install` installation method is
provided. This distribution hell can be escaped with the following three
(3) ways:

[PATCH] Fix duplicate "30" in response header 5 months ago

From Frederick Yin to ~dancek/twinwiki-devel

---
 src/main.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main.rs b/src/main.rs
index a58f84e..951f4f1 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -243,7 +243,7 @@ fn redirect_response(page: &str, subpath: &str) {
    let url = absolute_url(page);
    match subpath {
        "" => response_header(30, url),
        _ => response_header(30, format!("30 {}/{}", url, subpath)),
        _ => response_header(30, format!("{}/{}", url, subpath)),
[message trimmed]

McRoss fork for personal flavor addition 5 months ago

From Frederick Yin to ~nhanb/mcross-announce

I've forked McRoss (my favorite gemini browser so far) and started to
apply my own preferences to the codebase, including the patches that
were never merged and a few nuanced adjustments I don't feel is
necessary or mature enough for the public. Those include:

* 0d513e1 (HEAD -> master, origin/master, origin/HEAD) Enlarge window size
* abcad1f Custom homepage
* f888353 Fork: personal flavor version
* 61d0d7c Post-clone meta fixes
* 2280053 Support alt text for preformatted text
* a711c3f Download binary files

2280053 and a711c3f are the unmerged patches I'm talking about.
Seriously, check out the binary files one. It's my favorite thing about

[PATCH v2] Download binary files 6 months ago

From Frederick Yin to ~nhanb/mcross-devel

Summary:
Instead of reinventing the wheel and implementing downloading logic on
our own, I turned to the so-called "helpers" for help - CLI
commands that handle the dirty work of download jobs.

Changes:
- Introduced config arguments `download-cmd` and `download-dest`
- Download helper, of course
- Documentation regarding downloads
- Crossed out binary file handling on the bucket list
- Short names now optional for CLI args
---
New changes:
Handle scenarios where $URL and $DEST aren't single "words" in command.
[message trimmed]

Re: [PATCH] Download binary files 6 months ago

From Frederick Yin to ~nhanb/mcross-devel

On July 11, 2020 1:36:04 PM UTC, Frederick Yin <fkfd@macaw.me> wrote:
>Summary:
>Instead of reinventing the wheel and implementing downloading logic on
>our own, I turned to the so-called "helpers" for help - CLI
>commands that handle the dirty work of download jobs.
>
>Changes:
>- Introduced config arguments `download-cmd` and `download-dest`
>- Download helper, of course
>- Documentation regarding downloads
>- Crossed out binary file handling on the bucket list
>---
> README.md                    | 20 ++++++++++++++++++--
> src/mcross/conf.py           | 13 ++++++++++---

[PATCH] Download binary files 6 months ago

From Frederick Yin to ~nhanb/mcross-devel

Summary:
Instead of reinventing the wheel and implementing downloading logic on
our own, I turned to the so-called "helpers" for help - CLI
commands that handle the dirty work of download jobs.

Changes:
- Introduced config arguments `download-cmd` and `download-dest`
- Download helper, of course
- Documentation regarding downloads
- Crossed out binary file handling on the bucket list
---
 README.md                    | 20 ++++++++++++++++++--
 src/mcross/conf.py           | 13 ++++++++++---
 src/mcross/gui/controller.py | 31 +++++++++++++++++++++++++++++++
[message trimmed]

Re: [PATCH] Dark mode 7 months ago

From Frederick Yin to ~nhanb/mcross-devel

On June 18, 2020 3:57:07 AM UTC, "Bùi Thành Nhân" <hi@imnhan.com> wrote:
> > 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`.

I'm fine with that. One thing I'm unsure about is whether we'll still be able to remain "simple but no simpler", if every node is customizable. I suggest we allow variations in font size (and prob weight) only, except for preformatted text.