PC Ekspert Forum - Google Alternative ili kad stvari odu predaleko

PC Ekspert Forum (https://forum.pcekspert.com/index.php)

- Streaming/online servisi, linkovi i ostale zanimljivosti (https://forum.pcekspert.com/forumdisplay.php?f=18)

- - Google Alternative ili kad stvari odu predaleko (https://forum.pcekspert.com/showthread.php?t=229438)

Pretpostavljam da do HR još nije došlo, ako uopće bude zainteresiranih da ovo ganjaju

https://www.lawnews.co.uk/legal-news...lligence%20(AI).

Uglavnom, Microsoft i Google su dokazano koristili privatne podatke korisnika za treniranje AI. Ameri ih stisli, ali sad i UK isto.

Prijavio se i ja kod ovih, pa da vidimo hoće li sjest išta :D

Raspitajte se kod HR i EU odvjetnika jel ima kakva inicijativa da im se dodatno sjedne za vrat.

Citiraj:

Autor 1v@n (Post 3777812)

Kad je AI tema mislim da nisu oni jedini takvi. Mislim da svi "kradu" informacije gdje god stignu da bi njihovo AI rijesenje izgledalo pametno.

Citiraj:

A new YouTube tool will let advertisers use Google's Gemini AI model to target ads to viewers when they're most engaged, reports CNBC:
Peak Points has the potential to enable more impressions and a higher click-through rate on YouTube, a primary metric that determines how creators earn money on the video platform... Peak Points is currently in a pilot program and will be rolling out over the rest of the year.

The product "aims to benefit advertisers by using a tactic that aims to grab users' attention right when they're most invested in the content," reports TechCrunch:
This approach appears to be similar to a strategy called emotion-based targeting, where advertisers place ads that align with the emotions evoked by the video. It's believed that when viewers experience heightened emotional states, it leads to better recall of the ads. However, viewers may find these interruptions frustrating, especially when they're deeply engaged in the emotional arc of a video and want the ad to be over quickly to resume watching.

In related news, YouTube announced another ad format that may be more appealing to users. The platform debuted a shoppable product feed where users can browse and purchase items during an ad.

Nisam nimalo šokiran :goood:

Citiraj:

If you ever wanted to know what it was like to be an engineer at Google during the early to late 2000s, here you go.

Citiraj:

Now even though Google is fundamentally a spyware advertising company (some 80% of its revenue is advertising; the proportion was even higher back then), we Engineers were kept carefully away from that reality, as much as meat eaters are kept away from videos of the meat industry: don’t think about it, just enjoy your steak. If you think about it it will stop being enjoyable, so we just churned along, pretending to work for an engineering company rather than for a giant machine with the sole goal of manipulating people into buying cruft. The ads and business teams were on different floors, and we never talked to them.

↫ Elilla

Even back then, Google knew full well that what they were doing and working towards was deeply problematic and ethically dubious, at best, and reading about how young, impressionable Google engineers at the time figured that out by themselves is kind of heartbreaking. In those days, Google tried really hard to cultivate an image of being different than Apple or Microsoft, a place where employees were treated better and had more freedom, working for a company trying to make the web a better place.

Of course, none of that was actually true, but for a short while back then, a lot of people fell for it – yes, including you, even if you now say you didn’t – and reading about the experiences from people on the inside at the time, it was never actually true.

Ak još nije bilo očito:

Citiraj:

After yet another crackdown on ad-blockers, YouTube users are noticing videos that load slowly and direct them to a support page about turning off ad-blocking extensions.

> PcWorld

Zanimljivo da ja to još uvijek ne vidim na YouBoob. Samo čekam da pojačaju retoriku pa da otktantam YT do kraja i gotovo.

Već dugo se vidi da throttlaju download nekih vrsta videa, ne vidiš kod gledanja u 1x, ali kod 1,5-2x i pogotovo downloada se fino vidi da ne ide preko parsto kB/s.

Ja uglavnom sve gledam na 170x. Doduše rijetko na preko 720p.

Vjerojatno ste skuzili da je prosli tjedan doslo do vecih smetnja Google usluga i svih koji ovise o njihovom Cloudu (npr. Signal)...cini se da je ovo razlog:

Citiraj:

Google Cloud has attributed last week's widespread outage to a flawed code update in its Service Control system that triggered a global crash loop due to missing error handling and lack of feature flag protection. The Register reports:
Google's explanation of the incident opens by informing readers that its APIs, and Google Cloud's, are served through our Google API management and control planes." Those two planes are distributed regionally and "are responsible for ensuring each API request that comes in is authorized, has the policy and appropriate checks (like quota) to meet their endpoints." The core binary that is part of this policy check system is known as "Service Control."

On May 29, Google added a new feature to Service Control, to enable "additional quota policy checks." "This code change and binary release went through our region by region rollout, but the code path that failed was never exercised during this rollout due to needing a policy change that would trigger the code," Google's incident report explains. The search monopolist appears to have had concerns about this change as it "came with a red-button to turn off that particular policy serving path." But the change "did not have appropriate error handling nor was it feature flag protected. Without the appropriate error handling, the null pointer caused the binary to crash."

Google uses feature flags to catch issues in its code. "If this had been flag protected, the issue would have been caught in staging." That unprotected code ran inside Google until June 12th, when the company changed a policy that contained "unintended blank fields." Here's what happened next: "Service Control, then regionally exercised quota checks on policies in each regional datastore. This pulled in blank fields for this respective policy change and exercised the code path that hit the null pointer causing the binaries to go into a crash loop. This occurred globally given each regional deployment."

Google's post states that its Site Reliability Engineering team saw and started triaging the incident within two minutes, identified the root cause within 10 minutes, and was able to commence recovery within 40 minutes. But in some larger Google Cloud regions, "as Service Control tasks restarted, it created a herd effect on the underlying infrastructure it depends on ... overloading the infrastructure." Service Control wasn't built to handle this, which is why it took almost three hours to resolve the issue in its larger regions. The teams running Google products that went down due to this mess then had to perform their own recovery chores.
Going forward, Google has promised a couple of operational changes to prevent this mistake from happening again: "We will improve our external communications, both automated and human, so our customers get the information they need asap to react to issues, manage their systems and help their customers. We'll ensure our monitoring and communication infrastructure remains operational to serve customers even when Google Cloud and our primary monitoring products are down, ensuring business continuity."