Is that limited to the kitty terminal? I don't see any compatibility notes on Kitty Graphics Protocol nor your TUI project - which given the TUI label I would expect to work on any terminal?
I don't see how it solves the mentioned issues. Instead, federation introduces new issues of complexity, multi-layered moderation, and potential for distributed inefficiency, confusion, or more malicious attacks.
I think we can see on Lemmy some of the problems it introduces. But for an Encyclopedia, which is supposed to be a source of truth, I think it's much worse.
If you depend on instance admins as curators, it's not that different from Wikipedia roles, which at least has open governance and elections.
They say other projects didn't reach critical mass. I don't think spreading your contributors thin - even while connecting them to some dynamic degree - is how you reach critical mass.
Damn just realized that I should probably change the title when cross-posting stuff like this. I didn't write this, it was originally posted here: https://programming.dev/post/13590224
Cool stuff, I was looking for something like this!
Only thing I'm missing is an option to prefer local imports over alias imports - I like to use alias imports for different modules, but local imports for stuff in the same module (but only downward, never parents). Would such a feature be interesting to you?
It is, but I'd specifically like a rule that enforces this style of import over aliased imports. I.e. when importing a package, the order of importance is:
Relative import (if on same or lower level)
Aliased import (if in ancestor directory or different module)
Current plugin is just about force use aliases instead of relative paths (and back for deprecated aliases).
If you need to sort imports, you may try rule simple-import-sort/imports from https://github.com/lydell/eslint-plugin-simple-import-sort
It is very flexible, so you may customize your own groups. For instance, you may group aliases in one group and relative imports to another group. Check their docs
Sorry, maybe I'm not being clear - I'm not talking about sorting. I'm talking about an ESLint rule that flags alias imports that can be expressed as relative subdirectory imports, but flags other imports that could have been alias imports. Does that make sense?
Examples:
// we're in @/lib/foo
// correct
import A from "./foobar/a"
import B from "./b"
import C from "@/lib/c"
import D from "@/d"
// incorrect
import A from "@/lib/foo/foobar/a"
import B from "@/lib/foo/b"
Dockge looks nice, thanks for mentioning. I need something like it. Too many docker composes to manage and I don't want to go to the k8s complexity for hobby/personal use :)
Cool GitHub Projects
Hot