lyse @lyse.isobeef.org

Follow

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@lyse does not follow you (they may not see your replies!)

Recent Twts

Recent twts from lyse

(#g6v4kxq) @movq@www.uninformativ.de Ah, I did not have a portable diskman. Just a stationary radio with an integrated CD player. Or my parent’s stereo. But it’s sooo long ago, I can’t remember how long switching tracks took. Yeah, on second thought, maybe a second. Well, that actually improved then. Finally. Nice. :-) Loading the CD took several seconds, that’s for sure. And some devices were certainly slower than others.


#uw2s6ja

(#g6v4kxq) @movq@www.uninformativ.de There’s a big difference between being usable somehow and having fun using it. My tolerable limits are lower, but yeah. Up to five seconds for the “next track”? What music player are you using? :-D This must happen in way under a second, and luckily, this works here. :-) (But I’m also not streaming my music, it’s all on the local disk.)


#okcba3a

(#g6v4kxq) @movq@www.uninformativ.de My issue is, now that we have the chance of getting something fast, people artificially slow it down again. Wether they think it’s cool that they added some slow animation or just lack of knowledge or whatever. The absolute performance does not translate to the relative performance that I observe. Completely wasted potential. :-(

In today’s economy, nobody optimizes something if it can be just called good enough with the next generation hardware. That’s especially the mindset of big coorporations.

Anyway, getting sidetracked from the original post. :-)


#ae43b6a

(#ug2ndqa) @stigatle@yarn.stigatle.no Worky, worky now! :-)

Mate, these are some really nice gems! What a stunning landscape. I love it. Holy cow, that wooden church looks really sick. Even though, I’m not a scroll guy and prefer simple, straight designs, I have to say, that the interior craftmanship is something to admire.


#botltwa

(#ndodcuq) @prologic@twtxt.net I reckon, it’s just so that they can say: “Oh, whoopsy daisy. Too bad that you fell for our trap. Sorry, it’s entirely your own fault. Go away, leave us alone.”

The bullet point 8.6 continues right away (I forgot the ellipsis in my initial quote, excuse me):

[…] Customer agrees that it is Customer’s responsibility to ensure safe use of an Offering and the CrowdStrike Tools in such applications and installations. CROWDSTRIKE DOES NOT WARRANT ANY THIRD PARTY PRODUCTS OR SERVICES.

And in the one before that:

8.5 No Guarantee. CUSTOMER ACKNOWLEDGES, UNDERSTANDS, AND AGREES THAT CROWDSTRIKE DOES NOT GUARANTEE OR WARRANT THAT IT WILL FIND, LOCATE, OR DISCOVER ALL OF CUSTOMER’S OR ITS AFFILIATES’ SYSTEM THREATS, VULNERABILITIES, MALWARE, AND MALICIOUS SOFTWARE, AND CUSTOMER AND ITS AFFILIATES WILL NOT HOLD CROWDSTRIKE RESPONSIBLE THEREFOR.

In other words: “Just give us your money and hope for the best. It might work. Maybe.” Nope, of course it doesn’t.


#irvsqvq

(#ndodcuq) It’s also funny to read their terms and conditions:

8.6 […] THE OFFERINGS AND CROWDSTRIKE TOOLS ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED OR INTENDED FOR USE IN ANY HAZARDOUS ENVIRONMENT REQUIRING FAIL-SAFE PERFORMANCE OR OPERATION. NEITHER THE OFFERINGS NOR CROWDSTRIKE TOOLS ARE FOR USE IN THE OPERATION OF AIRCRAFT NAVIGATION, NUCLEAR FACILITIES, COMMUNICATION SYSTEMS, WEAPONS SYSTEMS, DIRECT OR INDIRECT LIFE-SUPPORT SYSTEMS, AIR TRAFFIC CONTROL, OR ANY APPLICATION OR INSTALLATION WHERE FAILURE COULD RESULT IN DEATH, SEVERE PHYSICAL INJURY, OR PROPERTY DAMAGE.

That’s why all airports remained operational. Oh wait…


#s2a7pga

(#ttjvaya) @prologic@twtxt.net Just look at their website. Yesterday, there was this quote, it’s already gone by now:

Cybersecurity’s AI-native platform for the XDR era

Mo-mo-mo-monster bingo!

Someone archived this screnshot, that I’ve also seen yesterday: https://assets.chaos.social/cache/media_attachments/files/112/812/257/953/926/994/original/c9de6459751f2ebf.png „Your company can be ruined in just 62 minutes“ Luckily, ClownStrike can shorten this timeframe even more. :-D

@movq@www.uninformativ.de I hope all admins can at least tell management: Told you so! But of course, no manager gets fired for their bloody stupid decision.

@xuu@txt.sour.is We got several e-mails about this whole desaster at work.


#a2ijqaq

(#ttjvaya) @prologic@twtxt.net @movq@www.uninformativ.de Haha, didn’t affect me or my direct workmates either. But our scrummie logged off with BSOD and another workmate also told me to have already experienced three with successful reboots, though. Another branch was completely offline and I heard rumors about factories being shut down, too.

Anyone who reads the CrowdStrike self-description and then buys the product has really earned a major fault.

This is exactly what’s going to happen, movq. Zero lessons learned. No consequences. Maybe just a bit more snake oil on top.


#la5stoa

(#c2afqsq) @movq@www.uninformativ.de Yeah, I don’t get it either. Some “security” scanner at work also complains about “dead” libraries all the time, just because the most recent commit is a few years or even just months old. What a giant joke.

This mindset might come from today’s kids who can build stuff only with gazillions of dependencies. And plenty of these suck, are full of bugs, vulnerabilities and bad code in general. So they have to be patched constantly. If one is always surrounded by that, it just feels normal. One might even come to the conclusion that it simply has to naturally be that way. And then, the incorrect deduction is that the project is abandoned, once there are no new commits in a week. It maybe doesn’t occur to these people that it is actually possible to work out differently.

To be fair, there is also a lot of unfinished and truly dead code out there. So that assures their theory even further, once they stumble across one of those projects.

And the same doesn’t only happen to private projects. All enterprise software systems also pull in so much stuff, that there is always something to update.

The lack of proper planning, just building and delivering buggy banana software in cycles and the mindset of shipping fast and often and doing things agile in general does not do this any favor. It just feels like today’s sofware is never ever finished. And if it finally reaches such a point, it must be dead.

I know of some otherwise reeeeaaaaally great software developers who also think that way. I don’t understand why they disagree with us here. :-?


#d2lmxdq

(#bl7a36a) @movq@www.uninformativ.de Why would that be surprising? :-) They definitely fit my style of music. Well, I don’t wanna know how much a ticket is. And the Wasen is also a terrible location. :-D

The overcrowded train was run by GoAhead, the S-Bahn by DB. They’re interchangeably bad.

Over fifty kilometers is a very long bike ride. That at least doubles my commute to more than six hours in total. No, thanks. ;-)


#jjk7zla

(#c2afqsq) @movq@www.uninformativ.de @prologic@twtxt.net Good analysis! Another aspect is: Trying out new stuff is appealing to a lot of people. I’m certainly not unguilty of that either. But when you experiment, things will naturally go wrong somewhere at some point. You probably don’t even know that at this point in time and realize this only much later. If at all.

To make it better, throwing things away and starting over with the newly aquired knowledge would be the right thing to do. But that doesn’t happen for a myriad of reasons. So you ended up with overly complex stuff.

A bit like building a prototype and keeping it alive forever. “Denn nichts hält länger als ein Provisorium.” – “Nothing is more definitive than the temporary.”

Then there comes in feature creep. And preliminary optim^Wfeatures, “hey, maybe somebody would like to bla in the future, let’s add this”.


#lmywqfq

I just heard AC/DC play live in Stuttgart-Bad Cannstatt for the first time in my life!

Well, when I was waiting for my train home on the station platform. I didn’t recognize that it was Acca Dacca, and I tried hard. In fact, the stage was 500 meters away, so it was just some music-like sound that found its way into my ears. Still kinda cool to know that I heard them live.

I had a barbie with my old workmates. That’s why I have a story to tell now. On the way there, the train was hopelessly overcrowded with AC/DC fans. You couldn’t fall down, simply impossible. It was like in the videos of Japanese subways, where guards press in passengers to utilize every square centimeter. At later stations, plenty of people didn’t get in. Not a chance. This caused quite some delays. And boy, was it hot in there. Streams of sweat running down everywhere.

Originally, I wanted to meet up with a workmate in a city train for the second part of the trip. Due to a signal failure, his train was delayed, though. It got delayed even more and more and was finally cancelled altogether. I eventually got my connecting train while he was still stuck and decided to abort mission and go home after 40 minutes. Catching my connection was another adventure. It was rerouted to another platform, of course without announcement. Because why would you? Fuck the passengers! Luckily, I noticed that it took a different branch at the switch on arrival and ran down and up the stairs to the other platform. The delay counter in this train showed 40 minutes when I finally got off.

With the exception of Acca Dacca, the way home was pleasantly uneventful. Just a few minutes delay and a relatively low passenger volume.

I’m so grateful for not having to experience all this shit on a daily basis anymore. Not looking forward to the next time I have to go into the city. Not at all.


#bl7a36a