h4ck_th3_pl4n3t

Sneed

That is literally how the CycloneDX SBOM packages work, well, after the fact and after the disclosure process.

Deniers should watch the movie "The White House effect". It's a great documentary that shows where and how the strategies of the oil companies changed.

Good morning, mistletoe. How are you feeling today? Are you an effective team?

Maybe they only support github?

How about sharing your working prompts then, so that others can learn from it?

Maybe we can refer to it as NOTMANGA

To also include Oracle and Tesla

Sneed

Sneed

Sneed

Sneed

How often did you see an actual UFO?

How likely is it that you saw a plane made by humans that you misclassified due to lack of data vs how likely is it that it was actually an Alien made aircraft, coincidentally working in our atmospheric conditions, gravity and drag related physics?

Guess what, it's about likeliness and you are extrapolating the wrong assumptions. Extraordinary claims require extraordinary evidence, not the other way around.

Check out Lazarus IDE, it's really good, especially for beginnerd.

[1] https://www.lazarus-ide.org/

They exist because they are either proxying networks that resell residential IPs (aka your internet connection) ...or because they are harvesting credentials.

The former will now make less sense as a business model, since UK isn't a good location to proxy traffic through anymore.

Why do you think free to use VPNs exist when both servers and bandwidth costs money?

> Yes. That’s exactly what we believe.

So all minors in the UK have their own banking account and credit card? You know, to pay for the VPN.

Repo of sourcespotter: https://github.com/SSLMate/sourcespotter

> If all you do is 'review' the output of your prompting before cutting a CR, I'd prefer you just send the prompt.

$$$ trillion dollar startup idea $$$

GP kind of implying that AGI is already there, and all companies are just dumbing them down because of regulations of the law.

I'm like "Sure buddy, sure. And the nanobots are in all vaccines, right?"

Beard: check

Glasses: check (I'm old)

Garish clothes: check

Segway: nope

So there's a 75% chance I am a Millenial hipster. Soy latte: sounds kinda nice

It is not a fork, and it is a NewTab page Chrome extension.

They didn't even change the codename that's displayed in the Settings page.

That's great, you're already addicted. The perfect regular user.

Damn this takes a long while to wrap your head around.

I think it would be better if there was a tutorial mode that doesn't show confusing screenshots but lets you play an easy preset of metaphors first, so you can learn how the game works.

To me the tutorial didn't explain anything, honestly, that's why I was so confused when I tried it afterwards and had to click Reveal anyways.

Now I can't play anymore but I think I understood the game mechanic, and am now disappointedly not able to play again until tomorrow.

It's called test driven development.

Every time I see a bait and switch like this, I'm thinking for myself "well, this could have been easily covered by AGPL...if they were actually interested in keeping it Open Source".

Oftentimes the company is worried about not being able to make revenue by providing hosted services, which is fair and I understand it. But please if you do this, don't do a bait and switch like this. Relicense it as AGPL which covers hosted services just the same as GPL would cover binary builds.

Anyways, thank you very much for this. As a former early adopter of snowplow in my infrastructure I really appreciate the fork and its new life!

Well, sync.Map is based on atomics which comes with limitations on its own as you have to use specific (potentially conflicting) hash keys for it.

What I wanted to point towards with my earlier comment is that sync.Map doesn't use resource based mutexes, it uses one mutex for everything which will always be the slowest case.

There's no real borrowing concept in Go, as there would be in Rust for that case, and if you argue that simplicity should be preferred then normal map[] should be threadsafe by default, which, in return, likely will require compile time expansion because of generics.

The core value of Go's "we want simplicity" approach always feels like it's a facade, because there is so many exceptions and footguns along the way. These footguns almost always were conscious decisions where they could have made a decision to break legacy behavior for better simplicity but decided that this is not what they want, which is weird as it's not fitting the initial language design promise.

Oh boi, all my RW mutexes for maps across goroutines would disagree.

Go is copy by default.

That means it would work if *bool is possible but it's not.

I never used errgroup but I realize that it's essentially the same what I end up implementing anyways.

With standard waitgroups I always move my states as a struct with something like a nested *data struct and an err property which is then pushed through the channel. But this way, my error handling is after the read instead of right at the Wait() call.

Not only iOS was affected. MacOS, too. Firefox, too. Chromium, too.

Essentially everything that used libicu as a unicode parser.

Was quite fun posting this in IRC and other chats and seeing clients go offline at the time :)