hpfr
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...
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.
¹ https://www.imdb.com/list/ls000050037/?sort=release_date%2Ca...
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...
> 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
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...
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.
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/
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/)
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...
> 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.
> 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?
Other Discord features like servers aren’t there yet, but “usernames” doesn’t seem like a real deficiency.
Nebula has mobile apps. Might this be possible for Innernet in some distant future? It seems like no if it needs root.
To be honest, I don’t see much appeal in publishing your entire unfiltered notes to the web. Synthesize interesting portions of them occasionally into coherent blog posts that other people can consume without digging through a forest of links, backlinks, and footnotes.
https://summerofcode.withgoogle.com/archive/2020/organizatio...
“After participating for 12 consecutive years, for the first time ever the GNU Project got rejected as a mentoring organization in the Google Summer of Code 2021.
We did not get any explanation other than: "We had many more applications than available slots. We hope you will apply again in the future!"”
https://lists.gnu.org/archive/html/summer-of-code/2021-03/ms...