I blame node.js and Rails for the global memory shortage that keeps prices sky high
Hi! We notice you're driving past our bookstore!
That's great, but you have your car windows closed. Would you mind opening your windows? We'd like to fill your car with wasps and locusts.
Now just one minute. Filling strangers' cars with wasps and locusts is how we pay our bills. Do you want us to starve?
We understand you may have had some bad experience with other wasp-and-locust providers. Some low-quality locusts got in the mix. But that's all been sorted out now!
Window. Open it.
Jeez, JIRA can be nasty.
Tried migrating a single user from LDAP to JIRA internal user registry. Took me a few renames, some manual fooling around with the database, and a restart, but it finally works.
I don't know how many phantom users were created in the process, but what matters is that the user can now login to JIRA using their old username which is not in LDAP anymore, and any comments posted by that user are still owned by that user.
It's an bot account btw, no real person was hurt.
"(...) Kogan’s app, called thisismydigitallife, gave him permission to access their Facebook profiles. And not just theirs, but their friends’ too. On average, each “seeder” the people who had taken the personality test, around 320,000 in total unwittingly gave access to at least 160 other people’s profiles, none of whom would have known or had reason to suspect."
More Effective Security Policies
I should really go to sleep, because I start having stupid ideas, like putting an HDD in PowerEdge 2900's floppy drive slot. Or putting an HDD next to the floppy slot, on top of the regular HDD enclosures. Or disconnecting the flexbay backplane from the main 8-drive backplane, and connecting it to a second RAID controller, whose battery will be laying around in a random place in the case.
Yeah, I need some sleep.
Remnants of #DRM are being removed from Polish ebook market. The last big bookstore removes all DRM-protected #ebooks from its offer, describing this technology as cumbersome. If a publisher insists on using DRM, then its books will not be sold at all.
I find Mastodon much less outrage-prone than Twitter, which to me is a virtue. But it also means I had to make a deliberate effort to use Twitter less and use Mastodon more. (And eventually, to quit Twitter entirely.)
On Twitter, it's easy to get lost in a stream of hot takes, bickering, and drama. Whereas on Mastodon, I often scroll to the end of my timeline and say, "Huh. I'm all caught up." For my quality of life, this is great, but for "engagement," it's a disaster.
WebKit has been doing some interesting privacy work recently: https://webkit.org/blog/8146/protecting-against-hsts-abuse/
Then a friend told be about
It doesn't quite do things the way I wanted to do them, but it's close enough. I like the tree-ish UI.
Haven't had time to investigate further.
Has anyone taken a closer look at it, and/or has an interesting opinion on this kind of discussion platform?
I was thinking of creataing an online discussion platform, where you'd argue claims instead of people making them. There'd be counter-arguments to claims and whatnot. It wouldn't show who created each claim, but there'd be stackoverflow-like karma (downvotes not for disagreement, but for arguments being badly formed / irrelevant / ad-hominem, etc.)
I was thinking that'd be an interesting social experiment.
Be my guest !
I don't mention that explicitly but I point to some resources (the GNU guidelines and the Christopher Lemmer Webber post and my own post on the guix mailing list)
But the reason is that many npm packages cannot be built ffrom source. On npm there's the binary only
This is for many reasons
But many of them are not buildable