From Starlink's page on Wikipedia: "Starlink accounts for approximately 75% of all active maneuverable satellites in Earth orbit"
1,694 karma · joined December 6, 2018
From Starlink's page on Wikipedia: "Starlink accounts for approximately 75% of all active maneuverable satellites in Earth orbit"
> For years I’ve felt like I was in a toxic relationship with Google, and the only reason I stayed was economic dependency.
Sharing Slack with Claude:
- Using the "normal" way, it shares too much, including privates messages.
- Using your own token, it doesn't work with Claude.AI or Cowork and requires you to go to slack.com to generate an application, tokens and more.
- Using a shared token, now you need context to tell Claude to retrieve it. It still doesn't work for non-Claude Code workflows. Rotation may break currently running workflows.
In a normal scenario, the provider of ad space would be a website or an application. Google would pay the owner of that space. On Youtube, that would be an ad served by Google paid to the channel owner.
There's a part about it: https://github.com/inevolin/k8s-cpu-limits-analyzed#3-withou...
The interesting part was the software, management interface, Terraform provider and how everything just fit together. Having storage, network and compute all in a single managed rack package brings a lot of value and brings down TCO. Really appreciated the security group like approach to network policies.
Unfortunately I haven't worked with HPE or Dell recently so I'm not sure what they currently offer.
Script is good, but the directory is missing from PATH. The edited scripts hardcodes the path to the user's home. Earlier in the article, the binary was copied to ~/.local/bin/stress so the given code suggestion should not work either.
* Because vended logs to s3 are not supported (https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS..., https://github.com/aws/containers-roadmap/issues/1141)
The assumption that you care about this is baked into ANSSI certifications, otherwise you would usually not bother certifying your product. They warned in 2022 that they would do this (See Phase 2: https://messervices.cyber.gouv.fr/guides/en-anssi-views-post...) and will allow PQC-only algorithm no earlier than 2030.
In term of implementation, WeRo looks more like a response to mobile payments like WhatApp, WeChat, Alipay, ... than a response a provider like PayPal. However, I haven't seen anything that'd limit them from expending support if they wished to.
> and also giving numbers out as much as possible
In Person-to-Person, you don't have to share your number. You can use QRCode (Direct SEPA). I'm not entirely sure of the email implementation, but maybe these do not share the phone number either (Edit: seeing https://support.wero-wallet.eu/hc/en-us/articles/25599201237..., it seems you may be able to do an email-only account). In Person-to-Merchant, I'm not sure what information are shared.
> Moreover payment systems that prioritize the needs of merchants usually are horrible for consumers
Supporting merchants flow to pay is different from prioritizing their needs so I'm unsure where you're going from there. It's also completely separated from Person-to-Person payments. PayPal supports Person-To-Merchant and I wouldn't say they are great for merchant.
But we aren't there yet.
Indeed, thanks for catching that. No maximum for an actual kratom leaf but leafs cannot be too potent, right?
Interestingly Firefox, I get latency that are way worse than Chromium (Median 0.46ms vs 1.2ms, P99 1.3ms vs 1.8ms).
Since there have been with bypass on service X, we should remove auth because all you need is the vulnerability.
Address space layout randomization wouldn't exist with this mindset, and yet it does and helps for many exploits.
SGX is not fully secure. But neither are the other part of the stack. Security (or trust in this case) is done through layers because it's a question of when you'll be vulnerable, not ifs.
- Small instances are used, including a burstable instance for AWS, with no indication on where and how much throttling happened. Saying that the instance is burstable but a price-match isn't even true because later it is discussed that $48 is not a match in price due to services around the instance itself
- It seem Hostim doesn't support large instances, the largest dedicated instance offers 100GB / 4 Cores / 8 GB RAM. At that price point, you either go with AWS for prototyping speed or compliance but definitely not for performance.
- Talking about speed, you got performance, but you'll now spend time developing your own backup and restore processes which are a "coming later" feature. What's the impact of backups compared to disk snapshots on those other network-attached disks?
- It mentions only once the network-attached block storage used by RDS and the Hetzner instance compared. Which is weird because you could go for local storage for cheaper and get more performances, but that introduces some trade-offs.
- Instances are configured with different settings.
"Fixing" this would make movement sluggish: any movement would need to be validated by the server. Meaning delay between pressing keys and actual movement.
There is also a factor of scale: a cop can follow you, but a system where everyone is monitored 24/7 is a very different story.
But that isn't the case at all, maybe Europeans are immune to smartphones: https://road-safety.transport.ec.europa.eu/document/download...