![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
It feels like this needs to be managed on an instance by instance level and not post to post.
It feels like this needs to be managed on an instance by instance level and not post to post.
Seriously, now that this is more widely known, it’ll for sure be taken advantage of a lot, to the point AWS will begrudgingly protect their customers once the damage is done.
Exactly, like how an ocean liner is a step up above a sailboat. That doesn’t mean you’re unsinkable and don’t need to worry about icebergs.
Windows is banned in my household, so l’m not worried about malware.
This is a false sense of security and just because you’re not running Windows doesn’t mean you’re immune to everything and can let your defenses down. For example, KDE recently had to announce that downloading themes will execute arbitrary code and cited someone who had personal information deleted because of downloading a theme.
Are you able to include the HTTP Method being called and the amount of data transferred per request? It’s possible that the first request is an OPTION request and then the second request is a POST.
If you can see the amount of data transferred, then you can have some more indication that double the requests are being sent and quantity the bandwidth impact at least.
Just when I thought Facebook couldn’t go any lower.
Right, for junior devs or trivial changes, that’s fine. My take is if I’m going to make someone take the time to review my work, I take the time to make sure that it’s cleaned up and would be something I would merge if I were reviewing it. Most of this comes from working on some larger Open Source projects which still require patches be submitted via email which I know is a real “back in my day” moment, but it did instil good practices which I try to carry on.
If you’re using the CLI and cleaning up a branch for a PR, the interactive rebase is a godsend. Just run git rebase -i origin/main
(or whatever your target branch is) and you can reorder/squash/reword commits.
In my experience, I prefer to review or contribute commits which are logical changes that are compartmentalized enough that if needed, they could be reverted without impacting something completely differently. This doesn’t mean 1 commit is always the right number of commits in a PR.
For example, if you have a feature addition which requires you to update the version of a dependency in the project, and this dependency update breaks existing code, I would have two commits, being:
When stepping through the commits in the PR or looking at a git blame
, it’s clear which changes were needed because of the new dependency, and which were feature additions.
Obviously this isn’t a one size fits all, but if someone submitted a PR with 12 commits of trial and error, and the overall changes are like +2 lines -3 lines, I’d ask them to clean that up before it gets merged.
I’d say this is more than kinda biased, and is heavily biased. They link to a 2015 article that says only 2% of documents have been publicly disclosed through journalists, and then make the claim that Russia and China have the other 98% with no source at all for the claim.
I might be misremembering the timeline in Citizen Four, but I remember that he had given the journalists all the documents and made a point that he didn’t have access to anything before leaving for Latin America.
It’s unfortunate that Snowden’s passport was revoked while he was in the Moscow Airport, and that he’s stuck there now. For a guy who didn’t want to go to jail or be executed for speaking out against the government, I don’t blame him for not speaking up against Putin.
Good point, I’m not against the transparent salary, my company lists a salary range, and knowing I’m at the top of my range for my position is rewarding.
If it’s working for them, that’s great. I wonder how they deal with resentment if someone is not contributing as much as everyone else. Knowing compensation is equal for differing level of work could result in higher performers reducing their effort, leading to an overall decline in the work the team is doing.
I was in your camp for a while and just kept it on my watchlist for forever. Eventually I figured I would probably sink 100+ hours into the game, so the cost per hour of entertainment was quite low. After getting it and playing for more than 100 hours, I can say I’m happy with the purchase and it’s worth it.
Don’t NFTs have more protections? If I sell you an NFT, I can’t unilaterally revoke it.
This is actually a thing and is called Sherlocking: https://thehustle.co/sherlocking-explained/
What is the name of the show? I’m interested but unable to find articles about the show or who’s in it.
The EU is currently evaluating if iMessage is considered a “gatekeeper”. Killing these services now solidifies they are gatekeepers and introduces EU regulation.
Are you referring to hashicorp with recently changing license terms? IIRC the change in license was to prevent competitors (i.e. AWS) from releasing a service using the open source software from directly competing with their cloud offerings. It’s sad it had to come to it, but I think the reality of the situation is that AWS could come up with a competing cloud offering, has the built in user base, and can run the service at a loss, because they make money elsewhere.
A company like Amazon totally could afford to pay, but won’t if they don’t have to. Ultimately, I think part of the license change was in response to Amazon and AWS being a monopoly. Without the license change, their company was at risk.
Wow this looks just like my last apartment
They just really wanted to release on 9/9/99 no matter what.