modderation

In the event that there is tracking, it seems to be well-built and doesn't interfere with the user experience.

Indeed, perhaps something like Simple Television Interface (STI) or Visual Display (VD) would be better? ;)

Alternatively, that means Framework doesn't need to spend resources building their own version, or acquiring a company that makes one. It's to Framework's benefit that they don't compete with module vendors. They just need to let the vendor list them in the official marketplace and promote them as a success story for the modular laptop concept.

With this in mind, trampling module vendors doesn't seem like a great idea. What's the point of creating an ecosystem if there's nobody around to participate?

Agreed, I'd kill for a modern version of the TouchStream LP. Comfiest and quietest keyboard I've ever used, with no elbow strain from reaching for a mouse/trackpad. They even had a product that could replace a MacBook keyboard. [1]

That being said, the company was acquired by Apple and turned into the iPhone and iPod Touch. The keyboards were effectively museum pieces at that point. I wonder if the patent situation would allow for third parties to revisit the design. It'd be interesting to see what could be done with by borrowing ideas from the programmable keyboard community and mobile touch hardware.

[1] https://en.wikipedia.org/wiki/FingerWorks

Incidentally, I'm still waiting for GitHub to implement Spacebar Heating: https://m.xkcd.com/1172/

If they do have that cash laying around, hopefully it's not stored on-premises.

You can always set copies=2 to work around block-level failures on important datasets.

Beyond that, you still get all the other ZFS goodness for management, snapshots, compression, zvols, error detection, send/recv, and so forth. Best of all, you can always throw another disk at it and convert to a mirror if the situation changes.

Rephrasing slightly: The animations are playing slower than grogenaut's reading speed, and they are forced to wait for animations to complete before advancing. Faster animations, a way to control animation speed, or even a way to skip animations could make for a more comfortable user experience.

Granted, this animation hails from 2014, so the above might not be possible without significant effort.

For anyone curious or learning about SELinux, I highly recommend the SELinux Coloring Book [1] as an overview of core concepts. It doesn't go into any of the commands or mechanics of interacting with SELinux, but it has some simple and clear examples of objects, labels, and enforcement types.

[1] https://people.redhat.com/duffy/selinux/selinux-coloring-boo...

It's not quite as secure as having a password, but you can force the proxy to listen on localhost-only (or any other specific addresss) by specifying it along with the port:

  ssh -D 127.0.0.1:8080 some-host.elsewhere.example

This won't protect you from people who already have access to your host, or from people standing behind you, but at least folks on your network can't use your proxy.

Ref: https://man.openbsd.org/ssh#D

That sounds like you're still streaming in traditional 2D with a static viewpoint being rendered somewhere in the cloud.

Full pre-rendered VR streaming would need to ship video of the entire environment for both eyes (or a reasonably large subset), and the client would be responsible for rendering your point of view. There'd be no latency that way, but the bandwidth needs would be significant given 4K per eye and a 90-degree FOV. That's on the order of 16K per eye, or 32K @ 120Hz video for static location. Add on some extra bandwidth for volumetric video to support position tracking, and you're looking at some even sillier numbers. Granted, a headset might spontaneously combust with that kind of data rate.

GA? Edge for Linux (version 97) still can't sign in to a corporate Office 365 account for sync. Personal accounts only.

I'm bewildered, as this functionality works on Mac and Windows, but somehow not on Linux. This is the one feature I actually need to start using Edge as my primary browser for work tasks. Until sync works with Azure AD, I'll have to continue using a separate instance of Chrome Beta/Dev that's tied to my corporate Google account.

I'd agree that a basic mapping of SSID name to approximate location is a bit useless on its own, but it can be combined with other information to narrow down your physical location.

Geographically speaking, how were those SSID's distributed? Were they spread all around the world, across the continent, or were they all in the same city?

For example, if your home SSID was known and those 216 SSID's were spread around the world, your home could likely be narrowed down based on some general facts from forum posts. "You spell honor with a U! You often complain about the rain on the forums, and those posts came from that ISP's IP block! According to the public coverage maps for that ISP in that English-speaking country that uses British spellings, your wireless network overlaps with this side of the street, give or take 30m. Let's check it out!"

Paranoid fantasy? I truly hope so.

Why not get the best (?) of both worlds with the macro-lisp crate: https://github.com/JunSuzukiJapan/macro-lisp

A small snippet from the project's examples shows minimal boilerplate between Rust and a native-looking Lisp experience: lisp!(defun factorial ((n i32)) i32 (if (<= n 1) 1 (* n (factorial (- n 1)))));

You may be interested in Lossy Zip [1]. It's coming up on 22 years old, as of April 1st.

Admittedly, it's somewhat unclear why the format didn't take off. At its core, it uses the Lessis-Moore algorithm to perform a global bit-wise sort of its inputs, then performs a run-length encoding (plus some other magic) on the results to achieve up to 100% compression.

[1] http://web.archive.org/web/20050402203136/http://lzip.source...

To clarify, you're redistributing the missing data across all of the other disks in the array simultaneously, rather than to one disk sequentially.

Let's say you've got an array with 10 disks and 100TB of data. You experience a single-disk failure.

If you're running a RaidZ, you have to write the lost data (100TB / 10 disks) to the single replacement disk. Writing 10TB of data to a single disk takes quite a while, especially on inexpensive SATA disks.

If you were running a dRAID with equivalent redundancy settings, you have to write (100 / 10)TB to the 9 remaining disks in the array. Each disk will have to write about 1.2 TB of data in parallel.

Writing 1.2TB to each disk should be roughly ~5-10x faster than writing 10TB sequentially.

On that note, I'm a bit surprised that RFC 2100 [1] hasn't seen any mention. It's quite relevant to the topic at hand.

[1] The Naming of Servers https://tools.ietf.org/html/rfc2100

It's not as straightforward when you're trying to create a master image for your corporate machines, though. Several steps [1] are required to properly remove it from all users on the machine after it is silently auto-installed or auto-updated, and this requires trawling through the error log to find the root cause [2].

1: https://docs.microsoft.com/en-sg/troubleshoot/windows-client...

2: https://social.technet.microsoft.com/Forums/windows/en-US/2c...

I've been leaning on an online .gitignore generator [1] as of late. Just punch in whichever combination of OS, Build Tool, and Development Environment you're using, and it provides some reasonable defaults that filter out IDE config files, temporary files, build output, and other undesirable shrapnel.

As an added bonus, the site outputs a URL that can be easily fetched with your command line tool of choice and output directly to a .gitignore file.

[1] https://www.toptal.com/developers/gitignore formerly known as [2] [2] https://gitignore.io is the easier-to-remember entry point.

Git Flow actually makes some sense if you need to track and retain history of self-contained fixes and features across concurrent release trains, where "retain history" means more than just a commit message.

With that said, I don't think this need is particularly common. Most projects are happier to throw away merge history in favor of a linear history with ephemeral branches and semantic versioning, and that's perfectly fine. The repository layout should be dictated by the project's needs, be it a glorified personal Undo Log, or a management tool on top of a Subversion repository.

Production-worthiness depends on your needs. The free edition is perfectly good for most people, however there are several features and modules that are only available in the Enterprise Edition. Notably, some of the disaster recovery, scaleout, and multifactor authentication features cost extra.

ref: https://www.hashicorp.com/products/vault/pricing

ZFS on Windows is slowly getting better.

I wouldn't actually trust it with data yet, but I suspect the developers would welcome any contributions or effort sent in their direction: https://github.com/openzfsonwindows/ZFSin

(I'm not affiliated, but I think it's a cool project, and I really want it to succeed)

It could also be Bring Your Own Breastmilk, or Breastfeed Your Own Baby. The hospital seems quite flexible in that regard.

They can always tar up their repo and send it over. You then unpack it on your end, then set it as a remote, pushing/pulling from it as you see fit. Admittedly, not the greatest workflow, but it doesn't require any new tools if you are already familiar with remotes.

As another alternative, git-format-patch/git-apply or git-bundle may be a quicker way of shipping changes around.