LanternLight83

Mullvad also notably accepts Monero, and if/when emulated, we should encourage and celebrate their comprehensive scope as much as any individual method

Personally, I've been building my mesh network up over Yggdrasil[1]. A router can even hand out Ygg IP's, resolve traffic for-, and firewall off- naive IOT devices (neccessary if you route through the public mesh, which isn't the only way to set things up).

1: https://yggdrasil-network.github.io/

I think this looks great, but will need to create or discover that no-systemd route Thx!

Love the idea because it feels like I have less control over the timer (which I shouldn't have!)

I've always thought of it as "the full article", having not made the connection :p

I think it's more broadly applicable

Could we get a (2021) in the title? I've been rocking this as my daily driver for years :p

I remember when they added the new themes, and hold-to-increase in the timer and alarm app, which are 100% my biggest use-cases.

I've never used Zig or C++, mostly Bash, Python, and Lisps, but have recently began learning C. I see C++ in search results, and it looks like C with higher level features in a register that reminds me of Java. I see this, and it looks similer: C with higher level features that remind me more of Python. I'm sure it's got other important features and priorities that set it apart (oft' discussed here), but that's what I see, and I dig it.

To be clear there are definitely a few ideoms I'd need to learn before considering this readable (it ain't psudocode), but I generally see all the building blocks and recognize what they're achiving. Maybe I'd have put them together slightly differently, but that could be equally true in Python. I'd rather learn this next than C++.

The density of how it's been written reminds me of some lisp code I've read, some implementations of state machines can be hard to follow too (in the classic "but where does it do the thing?" sense). I attribute a lot of the stuff that I don't follow to the lower-level C influence; I'm working for the first time with memory managment, structs, static types, pointers, bitwise opperations, etc.

Think I made my point in there somewhere >z>

Would love to know where you're coming at it from, I'd imagine that the C or 'kinda functional control flow' aspects might explain what looks most forign to you too (unless you have broader experience with low level languages)?

I use a nix-like os; I should just wrap or patch bash!

Mildly related thought: What I need is an RSS feed, Youtube, and local file manager (for content addressed buckets) that regularly brings a handful of "items" to my attention Anki-card style for quick metadata review/updates, relative (bracket-style) ranking, monotonically-increasing "priority" counter I can tick over time, and "Do you still want to keep this?" for de-cluttering.

Will probably need to DIY, but if you know any (ideally composable) tools that can cover even a portion of this system, please let me know before I start wiring Buku into Emacs.

Just to clarify, the missing component in my mind is in mirror advertisement. The need for manual compilation and review is a hindrance to casual participants, we need a config option that you just toggle (maybe a configuration struct with eg. bandwidth limits) to opt-in to IPFS or GNUnet distribution of store items present on your system.

I get that it's out of scope right now, but it'd be so cool to have a decentralized solution for regional caching

I've come across across him, yeah-- I might have a problem :p Was just focused on folks making content in that 8-22hr range (with one exception :p), otherwise I could include:

KingK, Mandalore, Daryl Talks Games, RagnarRox, Adam Millard, Chariot Rider, HBomberGuy, SuperBunnyHop, Lambhoot, GManLives, GrimBeard, ThorHighHeels, Nerrel, MathewMatosis, WillLovesVideoGames, Writing on Games, Game Makers Toolkit, and (duh) Jacob Geller

I really thought this going to be about the folk, making 8-24 hour long video game reviews and retrospectives, ie. the likes of Noah Caldwell Gervais, Joseph Anderson, PatricianTV, Private Sessions, Whitelight, Liam Triforce, Chris Davis, i am error, and NeverKnowsBest

Other comments appear to consider anything over a single hour unrelateably long, nevermind for scripted content...

This is great, thanks for sharing! I picked up most of this over time, but wouldn't have needed as much with such a great overview as this-- matches all the best practices I learned trying to make sure things looked right c:

What I didn't pick up along the way was accessability... anyone got recommendations for lesser known, quality, maybe even first-hand resources on eg. ARIA?

> Lisp is an old language with lots of dialects and systems.

Absolutely, my first thought was `dynamic-wind`.

https://www.gnu.org/software/guile/manual/html_node/Dynamic-...

i think its cute

That's really interesting, thanks for sharing!

Prikler's suggested syntax feels apt, as sugar for (I imagine) a set of native Guile parameters around the remaining fields of the package definition. Infrastructure will need created to implement inheritance, possibly at the level of fluids, in a manner that complies with the Guix maintainers preferences.

Thinking about how I tended to manage my USE flags (ie. through `package.use` as a directory), I think that the balance of package-level impact and operating-system-level syntax (how will services be affected?) will be interesting to see developed

I used Gentoo for over a year, from at least early April 2020 until my migration to GNU Guix in early December 2022. Got into DWM, LTO, minimal systems. It taught me more than any other distro, and there's still a lot I miss about Portage and the Gentoo community. Still use `functions.sh` to style my personal Bash scripts. Functional package managers have not nurtured the same culture around diverse USE flag support and quality packages + docs, and I wish I could just glue them together. Some day.

Perhaps the yellow dot is placed slightly off from the axies of the standard grid, making it unforgeable through input data-- I'm not sure that's what they've done, but surely they have to have considered input sanitization to some degree

I've found libreoffice to work well enough for any docx simple enough to have come from an older version of Word, but I might just be ignorant of how Word actually differs from the tools I use to view it; it just works for me ¯\_ (ツ) _/¯ I do find the suite rather large, but use functional package management to keep most of it's files abstracted away-- I bet the appimage or flatpak is pretty sweet in the same way

I would love to see Qubes rebuilt on this

Just anacdotally, I see OSM mentioned a lot, guides for contributing, use in HomeLab and Raspberry Pi articles-- haven't check it out myself in a long time, but I wouldn't be surprised if it's continued growth really is inevitable, or even has a cumulative snowball-ball component

> ~evil-mode~ Deprecated, check out Vimpulse or Vim Mode. Lol, the linked pages for Vimpulse and Vim Mode both start with the statement: > Superceded by Evil

Though frankly, any Vimmer using Emacs knows this already. Someone's either trolling, or never saw any reason to leave Vim and find out what these are options are really like, picking up the misunderstanding along the way.

I'd totally get that, these lists are awesome and maintaining them is hard work-- it's otherwise pretty great, and congratulations to everyone involved! I've always felt jealous of the folks funning neovim in their browser text-areas.

As an aside: I stick with emacs because of the modal and recursive minibuffer(s) (ie. command-line(s)). What vim setting do I change to be able to use normal mode down there?

Maybe a solid use case for local models are they're optimized for consumer hardware-- someone clever could preserve as much context as possible between requests

If you're really alright with a few minutes delay, you might be able to run =<13b param. models on CPU

There's also the widespread use of the term ricing, which, yes, I kniw has been debated and broadly accepted by the community

I think this is neat! Love the cute lil' characters, and I believe that simplified build systems are still fertile ground. Filtering and deriving from collections will be essential for larger projects.

> $_IN: [...] For collections, this is a space separated list of filenames > [...] > I haven’t written any software for this

Bit early for this sort of nit-picking, but that will need to be either a.) an escaped and quoted list or b.) an argv array that doesn't undergo word-splitting.

Bonus consideration: What if the user's shell isn't sh? Perhaps it's out of scope (ie. this shouldn't support every use case of Make), but for what it's worth, they support all sorts of recipe interpreters.

Sometimes I bake Nix into my personal Makefiles.

This means that we lose the non-Nix build processes, but I get to keep the best of both worlds, and don't have to run `nix shell` or setup direnv.

"Uhm, actually" I use Guix, but the idea is the same:

  SHELL = guix shell -m manifest.scm -- bash
  public: hugo content
      emacs $(pwd) --batch -l export.el
  [...]

Or without an external manifest:

  SHELL = guix shell --pure bash coreutils emacs emacs-ox-hugo hugo -- bash

This is equivalent to the common shebang trick:

  #!/use/bin/env -S guix shell -m manifest.scm -- bash

Or just invoking Guix inside the recipe:

  public: hugo content
      guix shell -m manifest.scm -- emacs $(pwd) --batch -l export.el

Depending on the complexity of `export.el` (< 5 lines?), I'll often keep that inside the Makefile too; the less files, the better!

But I get it if one wants that file available to call from elsewhere.

It's really matured, and although the RAID5/6 Write Hole still exists, I wouldn't reccomend a ZDEV over RAID10 either, which is what I believe offers the best tradeoffs for most users on both filesystems. Love the flexibility that BTRFS provides via eg. the balance comand, and Snapper is great for snapshot management.

It's interesting to compare this to the flexibility provided by functional package manager based OS's; in Nix too can rebase your system, perhaps even more literally.