sinaa

I iiiioiooo iko to keep up ok it iiiioiooo the same i

I really love the idea of "View source" for base prompts.

If we simply treat the prompts as frontend / client-side (one could even argue that it can be harder to get the original code from a JS bundle than extract a prompt using prompt injection), then function calling (the backend API) could be where folks add additional value, and if reasonable, charge for it.

As long as you can audit the function calls and see what's sent and received, same as you can do with a browser, then I think it becomes closer to a familiar and well-tested model.

The core value of code reviews is knowledge transfer and increased harmony across the codebase.

You certainly don't want to work in a codebase riddled with different ways of doing the same thing. Code reviews help with making the patterns more structured and more widely adopted. It also helps everyone at all skill levels to learn something from their peers, through reading their code and sharing thoughts.

It also makes more people in the team familiar with the codebase, such that more people are capable of changing and improving the related parts rather than just the original author.

The potential benefit of finding defects is only a nice to have!

My thoughts exactly. It's impressive that despite relying on BFS, the tool manages to be so fast on a tiny node on google cloud. Even when there's a depth of >= 5 !

Great work!

Do you simply do a BFS to find the shortest paths? If so, are you doing any tricks to avoid the path explosion problem?

You make a very good point on this.

As you say, a big win by text is that you can quickly skim it, ignore parts of it that you don't deem to be relevant, and essentially only use the working/short-term memory for the information you are interested the most in the context. Therefore, if the device responds back to you in voice, even if it's entirely a human-like experience, that's still inferior (at least in terms of speed) compared to the text-based experience.

Even for using voice as an input-only mechanism, it's still going to contain lots of redundant/useless information and verbosity.

Compare "OK google, what is the price of bitcoin today?" vs goolging "bitcoin price".

Really happy for GitLab and wish you guys all the best (and luck).

We've been using Gitlab for all our company's development, however, one major issue that is pushing us to switch over to GitHub is the fact that GitLab goes down almost every other day (or sometimes every day) due to deployments. Although during this often the site remains available, when CI is not executed or triggers are not performed, it is still extremely disruptive. I really hope that you prioritise having disruption-free deployments.

This is both clever and useful!

Is it possible to present a resized version of the route to each path underneath each target? (or perhaps show that on hover)

I understand that this would mean having overlapping map snippets of different sizes (with different centres), but some visual representation of the route to take could be nice.

Currently, the UX of having to click each target to see the path reduces the usability (having to go back and forth between the suggestions is tedious).

Just installed Nightly thinking "how can it be any different from the Developer Edition?" ... Wow, I couldn't be more wrong!

It is indeed a night and day experience! More approachable UI, and much faster performance... Big well-done to everyone working hard to keep Firefox competitive :-)

Thanks for the links.

What scares me is that over 1/3 of incidents were marked as "Investigation complete; no suspect identified".

And only 18% of attacks (156/833) resulted in a "Charged/Summoned" outcome.

Compared to 4 ns on Windows, many calls to the method can create significantly different performance profiles across the platforms.

App server availability is now 98.3% over the past month, which seems pretty bad!

I doubt they'd go for it.

Otherwise, this would give a huge boost to Firefox.

Chrome's own adblocker would only reduce the incentive to install another adblocker. Especially if it's natively implemented as part of the browser.

Still, as far as I understand it, it comes down to how good/competent the IT dept is at log-keeping, and how complicit they are in the forgery.

In a more broader way, how can one prove innocence if their company use the employee's credentials (ID/email/etc.) to drop the blame on them? Wouldn't it be the employees words against the employer, while at the same time the employer has the control over the data/evidence?

+ Shrugging-off an act of felony being committed.

Nevertheless, it does pose a more general question. Given that in many workplaces the employer has access to your work email/account, how can one prove that he/she did not send a particular email?

Maybe by suggesting that you would contact the investors directly to purchase your shares at a slightly discounted rate?

I think, while it may not be out of the goodness of Zuckerberg's heart, it's the cost of keeping the Facebook monopoly. That, and the $19B they initially had to fork out.

Are these new variants new compiles?

Is it possible that multiple variants with randomly-generated kill-switches are being automatically generated?

The goal would be to prevent security researchers from preemptively registering all domains the malware connects to.

Although it was only a thought, with what `cesarb` mentioned in mind.

This may well give birth to a new paradigm: Domain-Driven Programming.

Each condition is satisfied by a different domain lookup.

This may indeed be exactly what the authors of the next ransomware will do.

Two domains, one defuses the ransomware, the other detonates it.

This in my opinion is the exact reason.

Either they get $50 from users and let them go buy/install off-market, or make the money in the long run from paid app developers who are pressured now to put their applications on the store.

Great idea!

The following text could be improved though (looks as if it is suggesting to recommend a fake job to a friend):

"Is this job ad fake? Report it! or Recommend to a friend"

likely using the following pseudo-ish code:

  # possibly done using a session variable
  security_questions = []
  # first question
  security_questions.push({question: answer})
  # second question
  security_questions.push({question: answer})
  
  forEach(security_questions as x)
      if(!validate_answer(x))
           return false;

  return true;

If they do indeed use end-to-end encryption, there should be nothing to store/learn for Google. Though without it being open source, there's no way to be sure. Unless maybe they start collaborating with Moxie, as Whatsapp did.

It seems that a main differentiating feature is also the fact that all calls are end-to-end encrypted.

Perhaps as a video-calling alternative to Whatsapp? (given that neither of them are open source)

Extremely cool!

Now is the reverse (vision->sound) also possible? Perhaps using an array of laser sensors, so that we can reproduce the sounds in the environment.

Also, is it possible to turn the images/video back into sound? Could be a fun experiment!

Would be great if you could add an auto-complete on the supported keywords.

This way the user could explore and not get disappointed if his/her keywords aren't supported.

In hindsight, it would be hilarious (and perhaps even useful?) if the helicopter started running on its feet after landing!

Joking aside, given that the legs operate individually, I wonder what happens in case of a failure in one of them, or when one of them gets damaged during landing.

Nice work. How about a whitelist mode? Basically, the research mode + the ability to add sites (e.g., news sites, blogs, etc.) to the whitelist.