LanternLight83

> 4. Don’t sleep too much. Oversleeping also comes at the cost of time you’ll never get back. Moreover, there’s a good amount of evidence that sleeping more than you need is bad for you. Usually people will tell you to get more sleep, but I think this is the wrong direction for many people. The sweet spot seems to be somewhere around 7-7.30 hours, although again this is a genetic thing and can vary!

> Some people claim that this is purely psychological and that you can train yourself to get by on four hours a night, but this has never worked for me. I’m making the weaker claim: there is a big difference between 7 hours and 9 hours, you can do a lot with those 2 hours, and often if you’re a 9 hour sleeper you can become a 7 hour sleeper, which will end up compounding if you use those extra 2 hours well. [2] So it’s worth adopting the resolution to sleep less than you want to.

My SO would be horrified; I say something to this effect every night as I squeeze in "one more thing" after work, feeling that I need this time if my projects aren't going to stall between my days off, but I know they don't handle our sleep schedule as well as I do and that I ought to be more considerate-- perhaps for my own good as well.

IIRC, wasn't scp going to be rewritten in terms of SFTP behind the scenes?

Thanks for getting back to me! I didn't know about evaluation in the current context, which should let me inspect and explore the environment like I wanted to.

To clarify for anyone reading, `eval-defun` needs to be called with a prefix argument to instrument the first function, and `edebug-instrument-callee` (`I`) can be used to instrument the function following point in edebug's source-code-buffer, which I think is what you reffered to as a backtrace; I printed the edebug manual and brought it to work with me, in which I see that you can get a real back trace by calling `edebug-pop-to-backtrace` (`d`).

By `disassembled `, I meant bytecode, which after thinking about for a bit, maybe it could be done with lapcode, which is like bytecode made of s-expressions, but what I'd really want is a way to see the stack. Anyway, that seems like a whole 'nother beast, outside the scope of edebug.

Edit: I was looking for an evaluation list, see `edebug-visit-eval-list` (`E`) and `edebug-update-eval-list` (`C-c C-u`) c:

Just stumbled upon edebug yesterday after looking through the options that you can put in a `declare` form and it's become an invaluable portion of my workflow; if I may ask a noob question, is there an easy way to keep a persistent eye on a closure or arbitrary set of a variables, and is there a way to debug-step through disassembled code? Totally okay if you don't know off the top of your head, I'll have time to search for these eventually.

It was brutal. That town where the NA temp. record was tied would burn down the next day.

https://en.m.wikipedia.org/wiki/Lytton_wildfire

Thanks for sharing! I think it is just your team.

23.3% percent of respondents indicated that they use Vim in this year's Stack Overflow[1], noting specifically:

> PyCharm is used more by people learning to code (26% vs 16%) while Vim is used more by Professional Developers (24% vs 16%)

[1]: https://survey.stackoverflow.co/2022/#technology

Direnv has been mentioned, and it meshes well with functional package managers like Nix and Guix, each of which include the concept of "Profiles". Each profile can access a specific set of programs via it's environment, but PATH is far from the last variable that you can use Direnv or Profiles to control.

I like this, and will be changing my mail situation in the near future, when I might take some inspiration c:

I hadn't heard of these options before, thanks for highlighting them.

Oh, what an issue! There's plenty of context in there, and it's right up my alley. Thanks!

I just wish Qubes had a simpler architecture, such that dom0 and the Qubes Components could be implemented in eg. Guix or Nix instead of a traditional distro. Love Qubes' desktop integrations.

If those lower returns were coupled with lower volatility, I think we'd see more people utilizing crypto, for specific use cases: a. Instant, negligible-fee ledgers within social cohorts (eg. Algo, Nano, vs Paypal, Zello [a bit of that "anti-corporation" philosophy doesn't hurt here]). b. Privacy-coins, which also happen to have low fees but are too slow or haven't developed the UX to play that quick social role, so they attract an alternative audience through privacy ideals (eg. Monero). c. For donations, with the same trade-off between ease of use and privacy depending on the involved parties' preferences.

I'd argue it's the risk of volatility which both drives high returns and suppresses these uses, so a stabilization of market prices would eventually see growth in these use-cases as their potential audience puts proportionally less weight on the risk-factor.

One might not see 1 out of 100 current investors remain, but do think that these audiences could grow to equal or surpass such a small segment of the current interest.

I often think it's a program or set of docs that someone happened upon for the first time themselves, but that can't explain all of them; regardless, I love these kinds of posts, for the opportunity to encounter something that others might have assumed to be obvious and the spontaneous discussions that occur

Those who prefer to listen to their articles and news can find Blind's coverage this post here:

https://youtu.be/PT7adnfzmSU

https://youtu.be/QdDxuU0rVvE

This is a really awesome project, and I really appreciate how pleasant the interface is. Wonder what it would take to parse in existing man files? It works great for all those front-end frameworks, but Linux Man Pages /are/ the most voted request, and several other suggestions provide standard formats.

Comment on the Linux Man Page request frequently focus on where to get HTML versions, or where to source the files from.

I think the answer is to parse the man pages into HTML (maybe with Pandoc) with the existing CSS/JS, not scrape existing man page web front-ends (of which this would qualify). A swath of docs could be imported by creating such an importer and collecting the "doc" outputs from functional package repositories like Guix and Nix, which tend to stick very closely to upstream; any modifications are rare, explicit, and easily removed.

I don't know that the number of times a track is started would have any perceptible impact on an SSD, especially given the small size of the write (much smaller then, eg., a game save). I do think it would be cute to have an old rip of my favorite ambient YouTube mix that has accumulated hundreds of plays, even if that count isn't synced between devices (it'd accumulate them on whichever device I actually played it off of), and that that sort of passive, local scrobbing is worth at least as much enjoyment as a small game save.

Idk if you're on Linux, but what worked for me with Linux+Nvidia was enabling CONFIG_SGI_GRU

As far as I'm aware, this is the first domain name registration and resolution system without renewal fees, and hence, by tying the concept of ownership (not just theoretically, but practicality) to an NTF, this is the first system under which you /own/ (rather than lease) your domain. No one can take it from you, you don't need to remember to pay your rent on it, and you can give it away or sell it freely in a decentralized manner however you see fit. You don't even have to pay gas fees to give it away if you fund a dedicated wallet, the keys are the deed to the domain, though fees may still need paid to update it or transfer ownership to another wallet, haven't looked into the details. At least those fees don't go to an arbitrary corp, but into the ecosystem that allows this platform to exist with the virtues and ideals that it prioritizes, which might not otherwise be possible.

Me too, they've been updating and maintaining this wide array of apps for longer than I've consciously sought open-source. It's a shame they've discontinued Open Camera, but their suite is still very impressive, and they likely work under the same thankless conditions as any developer of free apps. Lead Dev has a Patreon, and if you use a few of their apps, and appreciate their continued existence, it could be worth a regular pay-what-you-can-esque contribution.

Haven't taken a look yet, but as a general attitude, biggest does not mean best, and size only makes a list more difficult to currate; it becomes the kitchen sink.

I first ran into Cockpit when it was included on a Fedora Server install, and I've been really impressed! It's sleek, I've never had any major[1] issues with it, and I really appreciate the wide variety[2] of functionality that you can include, eg. cockpit-machines for Virtual Machines and the EOL[3] cockpit-zfs for all sorts of regular RAID activities.

My sole gripe is that, IIRC, it's really tied into a dependency on Systemd, so I can't use it on any of my current machines which run elogind-based distros like GuixSD or a typical Gentoo installation. I don't happen to have any systemd-based distros installed atm, and if I did, can't imagine I'd use Cockpit regularly unless I could use it everywhere-- but I do wish I could! Maybe the systemd functionality can be factored out and re-implemented, but I'm not sure if anyone's going to decide it's worth their time and effort.

[1]: I did have to set $TERM=linux for the web-shell to behave correctly, but am not convinced that's an issue with Cockpit itself.

[2]: https://cockpit-project.org/applications

[3]: https://github.com/optimans/cockpit-zfs-manager/commit/80190...

My 2¢ as someone who's partial to crypto shit is that I think it's a cool idea, and really appreciate them going out and setting up the infra and /doing it/.

That said, not like this. The idea is great, but the NFT needs to be clear memorabilia, not just because of where it came from, but like, a quote or illustration from the article, just something that'll make me smile when I see it in my wallet and remember or w/e.

It's also gotta be cheaper! This could be a great way to support a content creator, but it's crowdfunding, you're running a per-article Patron here, who on Patreon has a three tier membership that goes $20-$200-$2000 (before gas fees!)?? We got run this shit on Nano or smth.

These arguments apply to external backups, but if you use a filesystem like ZFS or BTRFS, than snapshots are atomic, essentially instant, and can even be sent over the network as diffs/deltas against the last snapshot that was sent, so backing up a TB drive over the network every hour is total reasonable. These filesystems also give you access to snapshots via the FS, so you don't need to restore a snapshot to access your files, it's as easy mounting the readonly-snapshots directory, which you could even just keep mounted 24/7, making deleted files just a `cd` away, or quicker with a shell script that jumps first into the last snapshot of your current directory and then recursively back to the last one before that.

Not that I've gotten around to writing that script for myself :c

But the automatic snapshots are much easier c:

Some aggregators include archive links automatically; maybe an aggregator should mirror/pin content on an IPFS node, and users can help host front page content?

I was just looking around the other day, and can't reccomend enougj to do so yourself-- several user's pages are gems of character, one in particular has great nostalgia links like textfiles.com, and the site really captures small-web vibes.

Ah, I missed there was a unique label indication GPT was involved in the protective MBR; I I'd read it, it essentially is just an MBR with a single max-size entry, and I didn't consider there might be anything else; and ofc, it is a bit of a pointless thought experiment. Thanks for sharing!

Loved your story, I learned `./configure && make && make install` under similar pretenses.

Maybe Nix/Guix can bring us closer to that fanciful reality. I haven't used Nix, but have been really impressed with I'm hearing about festures like Flakes, and particularly Nix Comma, which uses nix-index to make downloading, compiling, and running (without installing) a package as easy as `, firefox`.

Loved your story, I initially learned `./configure && make && make install` under similar pretenses :p Maybe Nix/Guix will make this a reality some day. Nix seems closer, with Flakes (which I haven't used, but think they're kinda like docker entry points, standardized package metadata related to specific package stages or capabilities?) and comma (a project which uses nix-index to make compiling and running a package as easy as ', firefox' even if it hasn't been downloaded or installed)

Neat! I went looking for ways to create a protective MBR, learned a lot from the Gentoo wiki, some interesting info about how Windows does things in the link below, but the way to achieve this seem to be to just format the disk as GPT and then truncate it to the MBR (or just use one big GPT partition).

https://thestarman.pcministry.com/asm/mbr/GPT.htm

I showed your link to my partner, who reccomended some of the inventory of Peter Pauper Press: https://www.peterpauper.com/product_info.php?products_id=704...