douglasg14b @ douglasg14b @lemmy.world

Posts

11

Comments

950

Joined

2 yr. ago

You.... Are kidding right?

You would have to be living under a proverbial rock to have no inkling that Spotify is a product still in use, or be willfully ignorant.

It's like saying:

• People still use Google?
• People still drive cars?
• People still use Windows?
• People still go to churches?

...etc

Not that I agree that we should use Spotify. But playing pretend that they are small, irrelevant, and have no effect on the industry they are in isn't doing us any favors when it comes to pushing back against it.

Internal documentation leaking is still a data leak, it's just a subset of a data leak.

If it was sensitive information that commit would have been purged by now. The original PR (on the Google Clients repo) has no mention of problems, and there are no issues of discussions around rewriting the git history on that item.

This makes me think this isn't actually a problem.

My org is less practiced on operational security than Google and we would purge that information within minutes of any of us hearing about it. And this has been on blog posts for a while now.

Wait why is that commit still up if this is a data leak?

Where can one get a hold of these documents?

This appears to be the original blog post, but I'm not finding a way to download this. https://sparktoro.com/blog/an-anonymous-source-shared-thousands-of-leaked-google-search-api-documents-with-me-everyone-in-seo-should-see-them/

Is this not leaked past this one person?

Edit 2: No, these appear to be normal public docs.

Edit: seems these are the docs? https://hexdocs.pm/google_api_content_warehouse/0.4.0/GoogleApi.ContentWarehouse.V1.Model.QualityNavboostCrapsCrapsData.html

See: Hanlon's Razor

Give it time.

Butt hurt much

Please go back to Facebook, YouTube comments, or even Reddit with this petulant behavior.

No one here wants this sort of low quality, personally, attacking, bratty behavior in their discussions.

Yeah but don't let reddit lemmy hear you having a nuanced or thoughtful take.

Beer is expensive.

The whole point of this is to show the dad making a sacrifice for his kid.

I'm not entirely sure why you think it shouldn't?

Just because it sucks at one-shotting programming problems doesn't mean it's not useful for programming.

Using AI tools as co-pilots to augment knowledge and break into areas of discipline that you're unfamiliar with is great.

Is it useful to kean on as if you were a junior developer? No, absolutely not. Is it a useful tool that can augment your knowledge and capabilities as a senior developer? Yes, very much so.

TIL, thanks for the link!

Sure they do all they need to do is a bit a regulatory capture and free electricity for them means more profits while you continue to pay the same or higher prices.

How does it incentivize it?

The problem with energy storage isn't a lack of incentives, it's a lack of solutions. There are currently no proven, grid scale, economical, and robust energy storage solutions.

There are lots of storage solutions that work within limited geographical areas (ie. Pumped hydro). But past that it's a crap shoot.

Batteries are absolutely nowhere near the capacity or longevity needed for grid scale storage.

The largest battery storage system in the world is primarily used for grid leveling and emergency power. And would be depleted in minutes under its maximum load.

That's a global problem unfortunately.

We do not yet have effective and economical means of storing energy in grid scale quantities that are readily deployable near where that power is consumed.

It's a huge problem actually, the biggest one facing renewables like solar.

Good to see that Lemmy is becoming as toxic A wasteland as Reddit ever was.

• Armchairing ✅
• Personal attacks instead of attacking the arguments ✅
• Silent downvotes instead of actual discussion ✅
• Misrepresenting an anecdote ✅

All I did was provide an anecdote to show how easy it is to lose a round of ammunition. No one is strictly inventorying their .22 ammunition, it literally comes in boxes of loose rounds. Holes in the corners easily cause some to be misplaced during transportation. It's not common but it happens, and when it does you're not going to know, because, again, no one is inventorying their loose rounds.

Despite me calling out the armchair opinion, you decide that doubling down on the armchairness was more appropriate, and used an anecdote as a way to personally attack me, instead of my argument.

You made no attempt to actually address the point I was making, and instead took the easy route which is just personal attacks...

You can do better than that.

Do the productions actually have this in place?

I'm curious how you simulate recoil without firing a blank 🤔

Wait, maybe I'm not up to speed on the details here. But are you not pointing guns with blanks at people in movies....?

It's not the entire point of Cinema in that you are simulating, faking, an actual interaction?

Ok...

So your point is that a bad logging implementation is bad. And I agree.

I'm not seeing how that's extendable to implementations as a whole. You're conflating your bad experience with "log aggregation is bad'.

Just because your company sucks at this doesn't mean everyone else's does.

Yeah, ofc it is.

I'm working in a system that generates 750 MILLION non-debug log messages a day (And this isn't even as many as others).

Good luck grepping that, or making heads or tails of what you need.

We put a lot of work into making the process of digging through logs easier. The absolute minimum we can do it dump it into elastic so it's available in Kibana.

Similarly, in a K8 env you need to get logs off of your pods, ASAP, because pods are transient, disposable. There is no guarantee that a particular pod will live long enough to have introspectable logs on that particular instance (of course there is some log aggregation available in your environment that you could grep. But they actually usefulness of it is questionable especially if you don't know what you need to grep for).

These are dozens, hundreds, more problems that crop up as you scale the number of systems and people working on those systems.

Mozilla actually had a project for that: https://memorycache.ai//

They just suck at naming things, and unfortunately it's not getting much of the necessary dev time it needs to get out of the POC stage.

The biggest thing I want is local only models that use my activity & browsing history as a way for me to recall or contextualize events and information.