DominoTree

This will be great to use on the Librem 5 when it's released! (https://puri.sm/products/librem-5/)

The moment I clicked on this link, without even browsing, I was greeted with a recommendation to follow an account with a racial slur in the name. No thanks.

BlackBerry has been doing this with the keyboards on their phones for some time now

https://www.youtube.com/watch?v=Yn6DRcUFj8Y

For hand assembly I usually break out all of the components into little iFixIt project trays and print out labels that correspond to the board, but when there are a bunch of components with the same value, I just put the value on the label instead, and use highlighters on to point them out on printouts so I don't spend forever hunting where to place them. Then, I just go one by one down each spot in each tray until I've populated a board, then I throw it in the oven and start on the next.

https://pbs.twimg.com/media/DvIU0gSXQAE883Y.jpg:large

https://pbs.twimg.com/media/Dv2KXBuW0AAQY5c.jpg:large

I didn't realize assembly/programming services were that cheap and I'll definitely consider them for final runs of things in the future if it's a decent quantity like this. I'm just a hobbyist and I enjoy putting these things together, and most of the time it's just a handful of boards at once anyways so it's not a big deal.

The real issue was that I had ended up cutting a lot of corners to try and get things done in time, particularly with regards to testing. Definitely a major lesson learned.

The MCUs didn't take long to program with a ZIF socket, but once they were baked onto boards and I was finding bugs that needed to be fixed, that's where it really turned into a pain doing it over SPI.

After all of that, I still ended up having to bodge 2 connections on all of the final boards after all was said and done (which was the 5th or 6th board revision after I did small test runs to play with things and fix issues)

I knew this existed but had no idea it was still under pretty active development. How cool!

What's unusable?

At this point, vanilla Vim has async jobs as well, although it's not as clean as NeoVim

Found the library being used to generate the passcodes for the PKCS 12 stores. We're almost there!

https://pbs.twimg.com/media/DamdwvVWAAAn8_C.jpg:large

Update: private keys acquired. Need to figure out the password for these now. https://twitter.com/DominoTree/status/984272671549677568

Here are links to current firmware images:

http://gateway.c01.sbcglobal.net/firmware/00D09E/10.6.0.5300... http://gateway.c01.sbcglobal.net/firmware/00D09E/10.6.0.5300... http://gateway.c01.sbcglobal.net/firmware/00D09E/10.6.0.5300... http://gateway.c01.sbcglobal.net/firmware/00D09E/10.6.0.5300...

It doesn't contain art assets or audio and that sort of thing.

This is probably my favorite game of all time and I really hope somebody does something cool with this!

Semi-related: once some hardware arrives, I should be able to finish finding a way to rip the 802.1x certs off of the 5286AC so we can use our own routers, or at least put these things into a proper bridged mode.

https://spun.io/2018/03/18/getting-into-the-pace-5268ac-rout...

I'm still mostly just wondering why the hell a company that does shady advertising and pushes adware is doing security write-ups.

FWIW, at this point, the Firefox 57 betas are more responsive than Chromium for me. Not planning on looking back any time soon.

I haven't seen an AltGr key on a keyboard in the US in at least 15 years.

Yeah, isn't this what an autoclave is for?

This is why 802.1x exists.

Some genius at my company decided that ~180,000 Windows endpoints needed "localhost" removed from their hosts file, which has resulted in millions of requests per minute for localhost hitting our resolvers just to return 127.0.0.1.

My guess is that it was some hack they tried to disable IPv6, but aside from the insane load it added to the DNS infrastructure, the other result is that if these machines talk to a malicious resolver, their traffic destined for the loopback interface could end up going anywhere and being captured by anyone.

Great job!

I've used Nom to parse a couple RFC-based protocols now, and I'm amazed at how easy and performant the result ends up being.

There's a great walk-through of using it here, including fuzzing your parsers to make sure they're solid. https://github.com/Geal/langsec-2017-hackathon-code

For several years, I worked doing installs for eCW and I have nothing but negative experiences to report about the software and the company itself. This is wholly unsurprising.

Yes.

Not directly related to Osquery, but we're using Tanium to run queries against ~180,000 endpoints and we get good results back in about a minute.

This guy has several other similar microcontroller/microprocessor training kits available as well - http://www.kswichit.com

Neat stuff!

Failure to boot, random freezes in Windows and Linux.

That said, I got it sorted out. It turned out to be an incompatibility with both the NVMe disk I was using as well as an incompatibility with the memory I had purchased.

Getting the exact parts listed in your motherboard manufacturer's compatibility list appears to be pretty important for Ryzen currently. It's been rock solid since I swapped out those components.

Mice in general are shockingly unproductive as compared to keyboards - using Gnome in a primarily keyboard-driven manner is where it really shines.

My Ryzen 1800x box is so disgustingly fast that it almost makes up for the consistent stability issues I've encountered while using it

It seems as if your paradigm shifts it from "only wealthy people can access" to "only people technically competent enough to set up a sandbox can access"

Why are you using such an old browser? Part of the reason sites are built for current browsers is that responsible users should be updating their browsers frequently.

With as many ways as you can have your machine compromised by simply browsing to a website that had some malicious advertising code embedded, I can't imagine why anybody would use such an old browser if they weren't absolutely forced to.

ReactOS is one of the most impressive software endeavors I've ever seen, both from the scope of the task and the progress that's actually been made, especially from such a small core group of developers.

Many of the comments here are saying they're surprised it's still alive, or that it's sad someone would work on it, or that it should have more features. You're all missing the point.