hpfr · HackerTrans

hpfr

no profile record

投稿

The New Stability

nejm.org

3 ポイント投稿者 hpfr6 年前1 コメント

コメント

6 か月前議論

Indeed. It seems there are multiple questions in these comments on this subject, so I’ll just copy my reply from the Zotero 7 release here, since I don’t think anything has meaningfully changed since then:

WebDAV support is nice to save money, but from a privacy perspective it’s a huge bummer that the sync servers get all your citation metadata. A better self-hosting story¹ is one path to resolving this. End-to-end encryption² similar to e.g. Firefox Sync is another. Zotero has a security overview³ that shows they clearly care about good practices, but it’s still bothersome to have to trust the server when many other applications have proven E2EE works great even for non-technical users⁴.

Unfortunately from the main Zotero dev’s responses, it seems clear that they have no incentive to implement either and probably never will (look, the same comment from 2½ [now 4!] years ago⁵) without some shift in circumstances (massive increase in funding, new regulatory requirements). Even if a community member implemented the entirety of either solution, dstillman can just (rightly, tbh) claim it will increase their maintenance burden when they are trying to support paying customers.

1: https://github.com/zotero/dataserver/issues/105#issuecomment...

2: https://forums.zotero.org/discussion/comment/380780/#Comment...

3: https://www.zotero.org/support/security

4: https://support.apple.com/guide/security/advanced-data-prote...

5: https://news.ycombinator.com/item?id=29774935

昨年議論

Doesn’t look like “yes, but” language to me. Looks like the code is plain old MIT and the author is doing their due diligence with respect to vendored content in the repository subject to different licensing. Seems like they are being paid by a company to work on this, so it’s not surprising that they actually pay attention to copyright.

The fact that many project maintainers forget about vendored content and haphazardly slap the MIT license (or whatever) verbatim into a LICENSE file doesn’t actually give you a get-out-of-paying-lawyers-free card! If anything, Xee’s COPYRIGHT file gives me more confidence in my legal footing than an unadulterated LICENSE file would. It indicates the maintainer at least has a basic understanding of how copyright applies to their project.

2 年前議論

Looks like that’s a list of films from the 1930s (the whole decade). Four of the listed films are from 1930 if you sort by release date.¹

¹ https://www.imdb.com/list/ls000050037/?sort=release_date%2Ca...

2 年前議論

WebDAV support is nice to save money, but from a privacy perspective it’s a huge bummer that the sync servers get all your citation metadata. A better self-hosting story¹ is one path to resolving this. End-to-end encryption² similar to e.g. Firefox Sync is another. Zotero has a security overview³ that shows they clearly care about good practices, but it’s still bothersome to have to trust the server when many other applications have proven E2EE works great even for non-technical users⁴.

Unfortunately from the main Zotero dev’s responses, it seems clear that they have no incentive to implement either and probably never will (look, the same comment from 2½ years ago⁵) without some shift in circumstances (massive increase in funding, new regulatory requirements). Even if a community member implemented the entirety of either solution, dstillman can just (rightly, tbh) claim it will increase their maintenance burden when they are trying to support paying customers.

1: https://github.com/zotero/dataserver/issues/105#issuecomment...

2: https://forums.zotero.org/discussion/comment/380780/#Comment...

3: https://www.zotero.org/support/security

4: https://support.apple.com/guide/security/advanced-data-prote...

5: https://news.ycombinator.com/item?id=29774935

3 年前議論

Can’t believe I never thought of piping info output, but of course it works as a Unix utility should. Nicely parallels the dual HTML versions

3 年前議論

In the replies, the author writes:

> I literally did not know info pages existed for the first 15 years I used GNU tools, and I've still never used one

A bit of irony: the link and screenshot in the OP are from the HTML version of an Info manual! In my book, that counts as using one :). HTML Info manuals are right up there with Stack Overflow for most queries about GNU tools. Most people who have searched the web for how to do something with Make, GCC, or tar have used an Info manual, unwittingly or otherwise. There are even two types of HTML export¹: one web page per node, good for sharing links, and everything on one page, good for lazy full-text search.

And while the TUI program is indeed pretty niche these days (probably partly due to the fact that it’s not installed by default in many environments), any Emacs user worth their salt is intimately familiar with Info-mode :D

1: https://www.gnu.org/prep/standards/

3 年前議論

And much like “man man”, “info info” is a good place to start :)

3 年前議論

Makes sense. I should give Builder a try sometime. Thanks for your work!

3 年前議論

It seems to me we’re seeing something of a native GNOME application renaissance, both core and third-party, buoyed by GTK 4 and Flatpak (as well as the trend towards immutable base images). Rust seems to be part of this too—Loupe, Fractal, and Emmanuele Bassi’s recent GUADEC talk on oxidizing GTK¹ are examples. There are now three newer VTE-based terminal emulators targeting a native GNOME UX: Console (C), Black Box (Vala), and Prompt (C). Is there something about VTE or terminal emulators that makes Rust less appealing, or is this just a coincidence? I’m curious.

Prompt will probably be my next terminal emulator. That inspector looks interesting. Have you seen Ghostty’s recent demo²?

1: https://www.youtube.com/watch?v=WVWrllJQJ_s&t=6155s

2: https://mitchellh.com/writing/ghostty-devlog-005#terminal-in...

4 年前議論

There’s a proposal for Matrix on the associated mailing list from Element people: https://mailarchive.ietf.org/arch/msg/mimi/jvyvyJwgUhNgFyNYm...

4 年前議論

> Symlinks are just as problematic honestly, an app writing to it will change the object in the persistent "immutable" storage.

Well, anything stored by git-annex has read-only file permissions. Apps will follow the symlink, yes, but they will fail to write to the location if they try.

> The way the "check out" feature works is also weird, causing a change in the shared version history.

Unlocking a file changes it from a symlink to a git-annex pointer file from git’s perspective (git-annex accomplishes this via git’s smudge filter interface), but you don’t have to commit the unlock. You can unlock, modify locally, re-lock, and commit the new changed version in one go. It’s nice that you can commit the unlocking action itself if you want a file to be unlocked in all clones of the repository. You can choose whether to commit the unlock depending on if it fits your use case.

For curious readers, https://git-annex.branchable.com/tips/unlocked_files/ discusses these topics in more detail.

4 年前議論

If you configure annex.largefiles, git add should work with the annex. I start with something like

    git annex config --set annex.largefiles 'largerthan=1kb and not (mimeencoding=us-ascii or mimeencoding=utf-8)'

> By default, git-annex add adds all files to the annex (except dotfiles), and git add adds files to git (unless they were added to the annex previously). When annex.largefiles is configured, both git annex add and git add will add matching large files to the annex, and the other files to git. —https://git-annex.branchable.com/git-annex/

Note that git add will add large files unlocked, though, since (as far as I understand) it’s assumed you’re still modifying them for safety:

> If you use git add to add a file to the annex, it will be added in unlocked form from the beginning. This allows workflows where a file starts out unlocked, is modified as necessary, and is locked once it reaches its final version. —https://git-annex.branchable.com/git-annex-unlock/

4 年前議論

Ikiwiki’s definitely a bit weird, but I’ve been experimenting with git-annex recently and it worked fine every time I commented. Seems like it’s chugging along: https://git-annex.branchable.com/recentchanges/

When does it use hard links? As far as I remember it used symlinks unless you used something like annex.hardlink (described in the man page: https://git-annex.branchable.com/git-annex/)

4 年前議論

Take heart: https://github.com/matrix-org/matrix-spec-proposals/pull/357...

4 年前議論

Can you elaborate on why you would want two worktrees set to the same branch? I think if I were trying to compare two approaches involving incompatible changes, creating a branch for one approach would feel more natural anyway, and then I'd be able to use the worktrees.

5 年前議論

You're not getting old; this is a real nuisance.

That said, and to add onto the other reply, you're in luck: OpenSSH 8.8p1 includes support¹ for setting TERM in your SSH config with SetEnv². In my experience this works fine with just the client OpenSSH being up-to-date connecting to servers with older SSH versions and terminfo databases.

In your case, you might want to use a wildcard host at the end of your file to default to a more compatible TERM variable, and then override to foot's TERM variable value for the hosts you use that do have up-to-date terminfo:

    Host my-up-to-date-terminfo-host
      SetEnv TERM=foot
    
    Host *
      SetEnv TERM=xterm-256color

I've been using Foot for months now and just came across this issue, so it's nice there's now a path to get the full-fledged Foot experience only where it's supported. I usually stay comfortably inside GUI Doom Emacs for most shell workflows, but it's nice to have a modern, Wayland-native, no-nonsense terminal emulator when I do break my config :P.

¹ https://github.com/openssh/openssh-portable/commit/f64f8c00d...

² https://www.mankier.com/5/ssh_config#SetEnv

5 年前議論

Can you view relative links (for footnotes) in Elfeed? That hasn't been my experience.

5 年前議論

>> - every day I deal with broken links and broken images because my feed reader doesn't know from which URL it should resolve relative links

> These are the fault of broken RSS feed generators. The RSS feed should contain a textual summary of the article.

Footnote relative links are quite common in blog posts, and my RSS reader punts me out to a browser to view them. Given that most blogs I follow provide full-text feeds, it's a bit disappointing I can't easily navigate that last (textual) portion of content.

5 年前議論

I can’t quite tell if you think this system is reasonably effective or not. It certainly seems less invasive, so it would be good if it were. Are you able to comment on that?

> You can readily download the biggest script client for Dota 2, and VAC ban waves for using it have been unheard of for years now (you only get an in-game ban when enough other players verify the cheating via Overwatch).

Does this mean you think the ban process is too slow and involved?

5 年前議論

This validates my LaTeX usage, but honestly, can’t you only detect it if I’m using Computer Modern? I am, precisely because of people like you, but I don’t think you could tell a XeTeX-built resume with a Unicode font from one done in Word. And conversely a Word user could simply download CM Unicode and reap the LaTeX bonus points, no? :)