Show newer

We report late at night, the misty moon barely risen: we think it might start to rain. We have felt a few drops on the back of our neck, but it is, for good reason, a little bit difficult to make out potential rain clouds. This is a chilly night, but we hear a few crickets still.

Students, remember that science and Big Science aren’t the same things. Don’t let your professors fool you. You can learn to do science without becoming a cog. Don’t let them force you where you do not want to go.

What's that? You're still doubting the power of grass?

This is 24 hours later. I have a glasses kit. I just wanted to see how long it would last with regular daily use. Absolutely badass stuff, grass.

Show thread

@rune Yeah, agreed. But I can't find anything in either the NIST *or* original advisory suggesting it is anything more than that, other than a vague "things might be worse if the server trusts the header"?

Someone shared a comic I liked, but I noticed that somewhere in the chain, the artists name had been removed, so that stopped me. Reverse image searching proved surprisingly frustrating and involved diving into the cesspit of LinkedIn, but I eventually identified the artist as Irina Blok, but I can't link to the original image because its in Instagram jail, so here's her site.

That was a pain in the ass. Please don't trim credits. It's an asshole move.

irinablok.com

@rune Given their lack of explanation or sources that confirm this, it feels to me like that was an error, to be honest

Tech opinions 

Daydream: a smooth-talking grifter swindles the Zuck out of a bajillion simoleons in exchange for AR glasses that he never provides; Zuck shakes his fist at the sky

Show thread

"Everyone is welcome! Details on Instagram!"

Which is it? Everyone is welcome or only for people with Instagram accounts?

@rune I'm not sure where the 'arbitrary execution' part is coming from, as far as I can tell it's "just" header manipulation?

re: systemd, unix philosophy 

@clarfonthey Oh yeah, I'm taking the absolutely most generous interpretation of "UNIX philosophy" here, I very rarely see people actually interpret it this way and usually it becomes something worse - but it helps to make the point that even in an idealized, not-actually-happening interpretation of the concept, it *still* is a bad idea for end-user software. Because it just conceptually doesn't fit there.

mutual aid post, please help 

@mynameistillian @sentinian@lea.pet Would it be possible to get part-time work, survive on that + donations for a bit, and in the meantime seek an official diagnosis before uni finishes? Assuming that that *would* be a valid exemption

mutual aid post, please help 

@mynameistillian (The cheap handtrucks are usually a bit crappy so I wouldn't exceed the weight rating, they mostly work well for stuff that's large in volume)

mutual aid post, please help 

@mynameistillian I've transported a lot of stuff in the past with a handtruck (usually available *relatively* cheaply) and a lot of cheap ratchet straps, and in some places a shopping cart can also work (but very terrain/law-dependent). Neither is especially maneuverable, but they are at least independently moveable

Today, A bunch of automatic employees have published posts in their personal blogs and social accounts defending what Matt Mullenweg is doing against WP Engine.

A blind post on the automattic subforum, plus some individual accounts like it can be seen in the screencap below, say Matt is rounding up employees and asking them to publicly defend the company or hand out their resignation.

I can't verify this, I haven't been told directly, but I've seen several unrelated people confirming it's happening.

To my ex coworkers, if you see this, know that the press is very interested in what is going on and they would be more than happy to talk with you privately.

systemd, unix philosophy 

My problem with all these treatises on how software that "does a lot of things" is bad and more likely to fail, like frequently comes up in systemd discussions, is that while it is true in the abstract, these arguments never seem to account for things that people actually need to interact with.

Sure, it works great for libraries! Tiny libraries make for a very nice development experience and, with some reasonable dependency policies, very reliable and maintainable codebases. But that's because your target audience are *developers*; it's their *job* to pick the right tool for the job.

Your typical end user isn't a developer. They do not have the time or energy to allocate to painstakingly evaluate a "stack" of tools for every little thing they want to do.

They are looking to have a single program, a single UI, a single point of interaction with a coherent mental model, that allows them to complete their task from start to end. Where they can assume that the steps integrate, and they probably won't run into trouble on the common path.

And systems built to the "Unix philosophy" are notoriously bad at this! They are developed more or less in isolation - that is the point - and so they all have slightly different interaction modes, that are tailored to the specific task that the tool is meant to address. They may or may not integrate out of the box. If you're not a developer, this _sucks_.

So yes, by all means, modularize your libraries. Modularize your packages. Modularize every bit of internals you have! But don't try to universally apply the "Unix philosophy" to every piece of software without recognizing that *this is not actually what end users want to interact with*.

If you want your thing to actually be usable by people who aren't nerds, it *needs* to be usable through an application that does more than one thing. And this applies to anything a regular user might need to interact with directly; yes, including a service/system manager.

And if you insist that it is only a low-level tool, and people are expected to build end-user tools on top of that, then you actually need to make sure that it has a workable, reliable and consistent API to build against. None of this "custom string format you need to parse" crap.

(And yes, there are legitimate criticisms to be made of systemd governance. But "it doesn't follow the Unix philosophy" without further qualification is just about the worst argument you could be supporting it with.)

@onepict@chaos.social @librecast@chaos.social I appreciate it having such a clear definition :) I do generally follow the same goals, the things I work on need to be *for* something.

I do think that building a personal project in terms of "creating technology for the hell of it" is not *necessarily* wrong either, it just makes it a hobby project. What specifically irks me is that people never communicate this, and make it appear as if it's something more, by eg. actively marketing their project. You don't market your home science experiment to a nuclear lab either, and yet this is somehow considered normal in software.

But yeah, personally I'm very much aligned on viewing software development as a human rights thing too.

wordpress, WP Engine 

Going from what I've seen, and especially what either party *isn't* saying, I can really only conclude that both parties are the asshole in this whole thing.

@joelving Well, partly. Some kinds of politics are very important to sort out. Unfortunately it's often more the "office politics" kind that you get, and any discussions around the politics that actually matter tend to just turn into concern-trolling about basic values that shouldn't be in question...

@gsuberland The best part is all the source code they released which wasn't theirs...

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.