Those keycaps are a work of art, care to share where you found them?

I have a FIlco Majestouch 2 (also with MX Blues) and after a few years of daily use it began suffering extreme keybounce. It’s unusable now due to chatter/key bounce that affects nearly all the common keys. I’ve given up on it but might disassemble it and see if a deep cleaning with distilled water helps.

I too have two Filco Majestouch - one at work and one at home, both Ninjas, with different switches! At home, the keyboard’s plugged into a Mac and has a problem with dropping keystrokes / being slow as I type in a browser (and sometimes elsewhere). I can’t find a fix so I’m likely to plug an Apple keyboard in instead :(

The only remappings I do are:

• CAPS LOCK -> CTRL
• ALT -> CMD
• WIN -> ALT

The post mentions ‘programming’ - I’m assuming this is referring to remapping. I did look for keyboards where I could record macros, but those that exist are very expensive.

Your description is more or less on point.

That said, and this is what really gets me, is how Lenovo completely ripped out default S3 support. Hardware is completely capable of supporting both, but they took it out as a default.

Luckily the arch community created a great patch for fixing this issue across all linux machines (and BSD, iirc). Once I got S3, my standby time went from maybe 8 hours to somewhere greater than 2.5 days going by the drain rate between uses.

Looks like it got deleted, I archived it here: https://hastebin.com/boniyocefe.apl

Uh oh, i thought that dpaste was supposed to keep it for a year… sorry!

The “cached” link above has a copy https://archive.is/http%3A%2F%2Fdpaste.com%2F3Z4K4B0

Tell me about it. I’ve tried cross compiling Rust from Linux to OSX and it was just a saga of hurt from start to finish.

For Go, did you need to jump through the hoops of downloading an out-of-date Xcode image, extracting the appropriate files and compiling a cross-linker? Or is that mysteriously handled for you by the Go distribution itself?

AFAICT, XAR still doesn’t include the Python interpreter, so it’s not completely independent?

They seem to be using NUCs as their Kubernetes nodes, so the hardware cost isn’t going to be too great.

I imagine it’s down to a desire to not be dependent on an internet connection to run their POS and restaurant management applications, I’m sure the costs of a connection with an actual SLA are obscene compared to the average “business cable” connection you can use if it doesn’t need to be super reliable.

It could just be a basic, HA setup or load balancing cluster on several, cheap machines. I recommended these a long time ago as alternatives to AS/400’s or VMS clusters which are highly reliable, but pricey. They can also handle extra apps, provide extra copies of data to combat bitrot, support rolling upgrades, and so on. Lots of possibilities.

People can certainly screw them up. You want person doing setup to know what they’re doing. I’m just saying there’s benefits.

Yes, “Nearly all users of version control are non-developers.” is the author’s thesis for why DVCS is bad. I personally also find it frustrating when someone writes a book about something they could communicate quickly and clearly.

Their argument for why it’s bad for development is that their drive must be clean when crossing the US border as though that’s a problem that most people have.

Their argument for why it’s bad for long lived development is “your checkouts will necessarily become too big and slow someday, if the project stays on this system long enough” , which the author really has no evidence for.

Easy backup/restore + custom domain would make this really usable. I just can’t see how anyone could use this without planning for when it goes down.

indeed. I’ve used ejabberd as well as openfire in the past. Cert-Handling (as an example) was hell with openfire.

I will, however, fight to death anybody who mispronounces router as “rooter”.

What does a router do? It routes packets. It does not rout the packets, they are not fleeing the battlefield in retreat.

Do you pronounce “Route 66” as “Root” or “Rowt”?

(I realise this is an “American” vs “English” distinction, it’s just one that has always confused me.)

I think you’re right, unless I’m missing something obvious.

Worse still, if T1 enters the critical section and is followed by T2, if T1 now makes progress it will find benaphore_atom > 1 and call release_sem() on a semaphore it doesn’t hold. Which is probably either a crash or UB, who knows.

I was missing something obvious.

The semaphore, is initialized into an ‘unavailable’ state.

When Thread B attempts to acquire the newly initialized semaphore, it blocks as the semaphore is in its ‘unavailable’ state. Thread A later finishes up in its Critical Section, and seeing that benaphore_atom > 1 it increments the semaphore, allowing Thread B to make progress.

At the end of this execution, T2 sees !(benaphore_atom > 1) and continues without marking the semaphore as available.

Semaphores don’t provide mutual exclusion.

You use them to e.g. count the number of items in a queue and wake up enough threads to process them. Then those threads use a separate mutex to synchronise any operations on the queue.

I think people who aren’t up for that particular brand of interaction just avoid the project – which is probably how he likes it!

I was using OpenBSD for pf and relayd for a few years, but I didn’t participate in the mailing list.

Because it happens much less often than you or anyone else believes.

I’m participating in all the project related mailing lists daily - it’s easier to find someone completely not related to the project doing a rant on our list than it is to find Theo finally pushed into replying.

I hope I answered in my other comment, at least to some extent.

Building (and testing) recipe shouldn’t be part of CI configuration file, it should be part of Makefile or whatever is used for your language toolchain/building framework. You should be able to build application w/o having your own CI instance. Sure, Makefile won’t install packages needed to build software (dependencies should be mentioned in README file), as it’s a distro-specific thing, so that’s why CI environments need preparation step, and it needs to be stored somewhere. I just don’t like storing such things in project’s repository, as it’s strictly related only to tooling wrapping the project, and this tooling may change at some point, it’s CI-specific (and therefore often distro-specific) thing, so it’s meta project workflow thing. If you want it versioned, I think it should be versioned separately.

If you care about compatibility, you should be able to avoid lockstep changes (your older source code should build fine with newer build preparation configuration or your newer source code should build fine with older build preparation configuration). And if it’s not possible, then it’s good thing to have clear indicator as build failure, because it will most likely hit users too.

README (or INSTALL) file should be enough to let user/developer know how to prepare building environment in their own distro (which may not necessarily be your distro or distro used by CI).

tl;dr (simplistic): Today you may be using one CI, but it may be other thing in future. It’s not crucial part of the project (even if very useful), thus it shouldn’t pollute its development repository. That’s my view.

This is my pet hate with Jenkins, every time we open a new longer-lived branch that deserves a CI build, it’s an exercise in copying config from one browser tab to another. I’d love to just be able to modify a .jenkins.toml file.

It’s doubly awful when you have a couple of disjoint authentication domains, say an AD arena and a UNIX one, and they have inconsistent expiration periods, length & complexity requirements, and reuse policies.

Best of all are the systems where you can’t change your password until it expires, thus making it impossible to keep in sync with other domains.

I imagine that Kodi’s user population is difficult to measure. I have seen Android HDMI sticks that ship with a custom Kodi build enabling users to browse various streaming media repositories. It’s a fascinating ecosystem that seems to be largely invisible to people in the American Netflix/Hulu world.

Seconded. Until reading this headline, I had never heard of it.

We pinched it.

Lobstered or otherwise, it’s still toast.

Here’s the IU mirror of the thread, for anyone looking: http://lkml.iu.edu/hypermail/linux/kernel/1711.1/04620.html

The good ol’ Lobester’s hug to death.

I agree, but there’s many reasons beyond those to run your own service, such as policy reasons.

My main complaint about Slack for FOSS projects for example is that Slack is policy-wise built around being a corporate chat (which has implications to privacy policy etc.).

That address only the question of external attackers. But can you trust Slack to keep your data private? I think many people are also worried about this.

Sure, but you have to know a lot more things. WP is easy to spam, because it’s pretty easy to find. Even if 60% of companies started using mattermost, you’d have to find their instance (is it chat.example.com or is it mattermost.example.com or… ?). Plus it’s not that difficult to fend off wide script-kiddie attacks like this. IP rate limiting, regular patches, etc. That’s not very difficult to do with WP or mattermost. The upside is Mattermost being a Go application has a much smaller footprint of attack surface, plus they take security fairly seriously, and release often. WP started with a negative security outlook and PHP only helped the problem.. PHP is like the opposite of safe and sane(it’s getting better, but still).

System Admin is hard, but if you aren’t investing in good people, then chat data is probably the least of your worries.. see Equifax, etc.

I’m quite sure Slack also rents virtual instances, so it’s the same issue.

I know you are not addressing me, but: when you host yourself you can (easily) add additional layers of security. For example put the services behind a VPN.

The entire point is to be dismissive, right?

Drama submissions are categorized mainly by not being that important/actionable to daily stuff and more importantly by being “reality-free zones”.

The Google thing, as a great example, is drama because:

• Almost nobody who commented on it worked at GOOG and was in a position to really effect policy
• Almost nobody argued the core points of the memo, preferring to tangent on a particular point or metadiscussion–many didn’t even read the original thing before spouting off on it.
• Almost everybody refuses to change which side they are on in spite of evidence either way.

Such things need to be aggressively purged from the community, because they’re toxic.

Absolutely, I was unfortunately stuck for words to suggest a less dismissive tag.

A tag like ‘communities’ doesn’t feel specific enough to identify the precise kind of thread I’m referring to though, perhaps ‘political’?

I was debating between “train wreck” and “dumpster fire” when the present term was suggested on IRC.

I’ll be using this suggestion from now on though…

Boiled lobster is delicious, though….

I was worried that the problem with flagging such stories as off-topic and/or hiding them (or just stating in some rule or guideline that the aren’t on-topic for this site), could be considered to be “taking a position/side” on the issue. And that tends not to end well.