The opinions stated here are my own, not necessarily those of my employer.
- Prepaid credit cards tend to be a very common fraud vector (very similar to gift card scams).
For chargebacks, the merchant has to pay at least a $15 fee on every chargeback, regardless of the outcome of the result. It's why many merchants prefer for you to contact them and ask for a refund rather than going through the chargeback process. For small purchases, merchants tend to just refund rather than dealing with an angry customer that's going to charge back.
- Chargebacks or disputes will lock your account, so definitely stay away from that path.
But just closing the bank account will stop auto billing (it's considered a decline). So if you closed the account, it would just stop paying for whatever it is, and then cloud may lock the gcp account until it's paid. (I'm not 100% sure what cloud does with unpaid invoices).
- Direct YouTube link: https://youtu.be/Yg-qV6Fktjw
- This. You can disable all smart features (which includes things like mail categories, AI auto-complete, and most things that look at your emails).
Gear -> All Settings -> General tab (default) -> Smart features: Turn on smart features in Gmail, Chat, and Meet
Linked help page: https://support.google.com/mail/answer/15604322
- They have around at least 3000 commits, assuming this search is right?
https://github.com/search?q=repo%3AFFmpeg%2FFFmpeg+%40google...
And they have done large pushes in the past: https://security.googleblog.com/2014/01/ffmpeg-and-thousand-...
- The biggest for me: merge-conflict as first-class state within JJ.
I regularly have multiple commits being worked on at a time across different parts of the codebase. If I have to sync to head (or any rebase) and one of my side branches that I'm not actively working on hits a merge conflict, I don't have to deal with it in that moment and get distracted from my work at hand (ie: I don't need to context switch). This is a big productivity win for me.
If you want some other points, check out: https://fallthrough.transistor.fm/43#t=0h31m5s
Some points from the episode:
* With no separate index vs commit, (everything is just a commit), you don't need different commands and flags to deal with the different concepts, they are all just marked together. In JJ, if you want to stack/stage something, it's just a normal commit (no reason to have different concepts here).
* You don't have to name/commit a change at all. Every time you run any JJ command (like `jj log`, or `jj status`), it will snapshot the changes you have. This means that if you want to go work on some other branch, you don't have to go and commit your changes (they auto-commit, and you don't have to write a description immediately), then update to master branch and start working again.
* Or you can just `jj split` (https://jj-vcs.github.io/jj/latest/cli-reference/#jj-split), and split a working changeset into 2 separate commits.
- The "dig" command can get them for you
$ dig ycombinator.com mx
;; ANSWER SECTION: ycombinator.com. 300 IN MX 20 alt1.aspmx.l.google.com. ycombinator.com. 300 IN MX 10 aspmx.l.google.com. ycombinator.com. 300 IN MX 20 alt2.aspmx.l.google.com. ycombinator.com. 300 IN MX 30 aspmx4.googlemail.com. - Semi related: there is an active proposal of having a go OS Target of "none" (or noos (No-OS)).
https://github.com/golang/go/issues/73608
Sounds like they want to maybe include https://github.com/usbarmory/tamago in the compiler.
- My point was replying to the OP who said:
> I dont get how you US guys can live in an environment were your next door neighbor, the person beside you in the supermarket etc can carry a lethal weapon that can end your life.
Knife killing can happen for the every-day citizen that doesn't have a security detail. The OP is scared about the neighbor having a weapon to kill them with... and every household already has one in the kitchen.
If you are scared about being killed in a given society, it's more likely a cultural problem rather than a tool problem. Yes, guns make it easier to do. The question is, why are more people doing it now adays? What changed?
Go back a few decades, and you can find plenty of kids in highschool in the US that would keep rifles in the back of their truck in the school parking lot. They would use those guns to go hunting after school. They weren't being used to shoot eachother.
- Has there been a case where a single person killed hundreds with a gun? The worst I know of is the Vegas shooting, which was 60. There have been mass-stabbings that have reached ~30 people killed (https://en.wikipedia.org/wiki/Mass_stabbing#Examples_of_mass...).
- This is a pipe dream. Advertising always has existed and always will. It comes and goes in different forms, but people like selling things they make or services they provide. Without a way of getting those things in front of people, nothing new could come to light.
I agree that some sites make advertisements a massive eyesore, but that's a problem that can be solved in other ways.
- One example: Merge conflicts can be submitted as a proper entry and dealt with later: https://jj-vcs.github.io/jj/latest/conflicts/
- They did a interview 2 weeks ago about this on the changelog podcast with Sugu Sougoumarane, the co-creator of Vitess, who is at Supabase now. Watching the competition year will be interesting
- Protobuf has a text and binary format. https://protobuf.dev/reference/protobuf/textformat-spec/
Google uses it a lot for data dumps for tests or config that can be put into source control.
- From the source: https://cloud.google.com/blog/topics/threat-intelligence/voi...
> The instance was used to store contact information and related notes for small and medium businesses. Analysis revealed that data was retrieved by the threat actor during a small window of time before the access was cut off. The data retrieved by the threat actor was confined to basic and largely publicly available business information, such as business names and contact details.
https://www.hyrumslaw.com/
> With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.