>National security and "public safety" carve outs need to be eliminated. So long as those exist, we have no right to privacy.
This is overly absolutist, or maybe idealistic view. National security and public safety IS more important than individual right to privacy. As an extreme example, if your friend was dying, you had a password to my email, and you knew that you can use information in my inbox to save that person i really hope you would do it.
In general I think that police with a court order should be able to invade someone's privacy (with judge discretion). I mean they can already kick down someone's doors and detain them for several days - checking email doesn't sound too bad compared to it, does it? I think they should also be legally obliged to inform that person in let's say 6 months that they did it.
The problem is that modern world is drastically different than the old world when you needed to physically hunt down letters. Now you can mass scan everyone's emails, siphon terabytes of personal data that stasi could only dream of, and invigilate everyone. This is something that is worth fighting against.
> National security and public safety IS more important than individual right to privacy.
I disagree.
Because as soon as you open the door to governments reading your mail, they will read your mail. They can't help themselves. [0]
The only way of stopping them from doing this to excess is to stop them doing it at all.
The "National Security and Public Safety" thing is what they say to justify it, but that's not what the powers will actually be used for. They will actually be used for far less noble purposes, and possibly actually for evil.
We are actually much more secure if we don't let the government read our mail.
I'm not a lawyer, but are there any potential trademark issues? AFAIK in general you HAVE to change the name to something clearly different. I consider it morally OK, and it's probably fine, but HTTPXYZ is cutting it close. It's too late for a rebrand, but IMO open-source people often ignore this topic a bit too much.
There are unregistered trademarks as well as registered ones. Usually the "TM" symbol is applied to unregistered trademarks, and the ® symbol for registered ones. Both enjoy protection, although it's generally an easier time in court when your trademark is registered.
Whether actively defending your trademark is actually required is a bit of a nuanced topic. Generally, trademarks can be lost through genericide (the mark becomes a generic term for the type of product) or abandonment. Abandonment happens when either the mark owner stops using the mark itself, or takes an action that weakens the mark. The question, then, is whether failing to defend infringing use constitutes a weakening action. Courts differ on this, and there is a large gray area between "we didn't immediately sue a local mom-and-pop shop" and "we allowed a rival company to use the mark erroneously across several states for years without taking action."
He would probably win in a legal case, but is he actually going to take it to court? I doubt it. Also I wouldn't be too offended about the name if I were him and for users it's better because it makes the link clearer.
I think if had named it HTTPX2 or HTTPY, that would be much worse because it asserts superiority without earning it. But he didn't.
>The Requests package is recommended for a higher-level HTTP client interface.
Which was fine when requests were the de-facto-standard only player in town, but at some point modern problems (async, http2) required modern solutions (httpx) and thus ecosystem fragmentation began.
Well, the reason for all the fragmentation is because the Python stdlib doesn't have the core building blocks for an async http or http2 client in the way requests could build on urllib.
The h11, h2, httpcore stack is probably the closest thing to what the Python stdlib should look like to end the fragmentation but it would be a huge undertaking for the core devs.
> but it would be a huge undertaking for the core devs.
More importantly, it would be massively breaking to remove the existing functionality (and everyone would ignore a deprecation), and confusing not to (much like it was when 2.x had both "urllib" and "urllib2").
It'd be nice to have something high level in the standard library based on urllib primitives. Offering competition to those, not so much.
The original author (who is also the leading maintainer of httpx, another huge package) started a crusade against male-dominated spaces such as... Github issues and discussions.
>So… sharing the source isn’t the problem here. The issue is the GitHub working environment. I’m not interested in the smokey boys-only-club atmosphere, it feels starkly unprofessional.
>We’re not having any more conversation in all-male online spaces. Not happening.
>I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value.
As a mkdocs user and a httpx user I find that concerning - I hope personal issues won't harm those projects long term (well it looks like mkdocs is already dead).
I'm not an MkDocs user yet but I've been meaning to be for years! It's unfortunate to hear about the issues with project leadership. Why bring the drama about gender into this?! It should be closed as off topic.
The only "killer app" for crypto*currencies* is being a payment method. Not counting speculation. This is what they are used for right now, but the scale at which this happens doesn't justify their current valuation (even after recent losses).
But is that a better experience than just using your visa? Nobody wants to wait at the cashier for 15 minutes to pay for their groceries, which is what has to happen if you really want the decentralized experience. Otherwise you really are just reinventing a worse, centralized payment rails. Volatility and wait times are features of crypto, not bugs, but they make for terrible payment experiences.
Doesn't lightning settle basically instantly, while still being decentralized? You're just trading signed transactions iirc, with settlement happening whenever.
The settlement happening whenever is a problem. Instant authorization is very different from a practical settlement model.
At least with card networks, there are layers of liability if solvency issues occur. There’s merchant protections from the acquiring bank and if for some reason the acquiring bank fails there is the guarantee of the card network.
On the issuing side there are chargebacks. I hate chargebacks as much as the next startup bro but consumer protections are a necessary aspect of a functioning payment rail. There are reasons we don’t use ACH for everything.
I think hand waving the pesky settlement details is absurd. The settlement process is the payment rail.
If you do want those protections you end up back with a custodial wallet, which brings us back to a centralized model.
I’m not arguing crypto doesn’t have its place in the universe, I am arguing it’s a very bad payments product.
I don’t have a horse in this race, but my only point was you don’t have to wait 15 minutes for a really decentralized experience. Yeah, you do need to be ok with not being able to later chargeback your grocery store, just like with cash. Which is fine for your example of groceries in hand, less great for large purchases over the internet.
Maybe we don’t need an alternative when Visa handles everything, but it might be nice to not pay a 3% markup on everything. Alternatively, we could try to be more like India and Brazil, which each built instant bank to bank transfer setups you can use at the grocery store, without the risks that come with losing debit/credit cards. Convenient without poor people with no rewards cards subsidizing everyone else to cover Visa’s take.
>Yeah, you do need to be ok with not being able to later chargeback your grocery store, just like with cash.
Well the reason that works is because in grocery stores you have a concept of card present so the liability shifts to the issuing bank... so there are no chargebacks. Concepts like card present and card not present demand a centralized authority and really can't exist in a decentralized payment rail, unless you're going to somehow invent decentralized pos hardware for merchants. Once you enter the world of atoms, you have re-introduced centralized trust into your payment rail though.
> Convenient without poor people with no rewards cards subsidizing everyone else to cover Visa’s take.
I fully agree. This is a crappy part of ccs and the best remedy is to disallow rewards programs for credit products. This isn't a fault of the card networks its a fault of issuing banks (and the airlines). Every crypto company in 2021 was offering 8% APY, you think those guys would have been better about this than Amex?
> Maybe we don’t need an alternative when Visa handles everything, but it might be nice to not pay a 3% markup on everything.
I'm actually not bothered by a take from the banks and networks involved. They are underwriting risk and affording insurances to me and the merchant. I guess my main argument is that it's good to have centralized insurance in money transfer facilitation. 3% is high and a failure of Dodd Frank. The Durbin Amendment should have reigned in cc fees and not just focused on debit interchange.
> Alternatively, we could try to be more like India and Brazil, which each built instant bank to bank transfer setups you can use at the grocery store, without the risks that come with losing debit/credit cards.
I don't disagree. As you pointed out it really comes down to the crappy reward programs from the issuing banks that make merchants and poor people suffer.
I don't mind crypto as an idea. I don't have a horse in the crypto race either. What I mind is the notion that it is somehow a viable payment rail. I'm sorry, it's been 20 years and crypto's best use case for payments has been buying acid on the internet because it was the only payment option.
I think one of the most interesting business stories in the world is about the guy who invented the Visa network, Dee Hock. It truly is a story of decentralization at its finest. John Coogan did a great video on him a couple of years ago I highly recommend: https://www.youtube.com/watch?v=RNbi2cUZt1o.
Mobile is different from desktop. Dark mode became popular with OLED panels because on those it saves battery, and blacks actually look nice, compared to the average LCD. I use dark mode on mobile but light mode on desktop.
I'm not sure how much Android use generalizes - I prefer light mode, but I'll use dark mode for the battery savings on portable devices with OLED screens.
Unless this whole setup is self-hosted (which I doubt), it's also uploaded to some data lake of a company which is in business of profiting from information.
Intelligence agencies are really heading into a golden age, with everyone syncing all the data they have to the cloud, in plaintext. I mean it was already bad, but it's somehow getting worse.
The thing about that is the benefits, saving a couple minutes a day and not having to click to different windows where the information is stored, is apparent and intimidate whereas the harms associated with loosing most, if not all your privacy and security isn't felt in the same type of immediate way, so the dopamine of the positive effects completely overwhelms. It is hard for many people to be able to weigh different cost/benefit in situations where it is so one sided on the immediacy spectrum.
It may be cherry-picking, but I think some commenters misunderstand this (or maybe I do).
The implication seems to be "12 hours before the resolution things are obvious anyway". But if that were the case, then I could pick some wager that is obviously true but has, for example, 70% chance, and putting my money on that. If it was true that "12 hours before the resolution it's obvious what the result is", everything would be in 0% or 100% buckets. I believe getting event with 30% confidence right exactly 30% times is impressive no matter if that's 12h or 120h before.
Disclaimer: I don't know much about prediction markets, just what I understood from the blog post.
This is overly absolutist, or maybe idealistic view. National security and public safety IS more important than individual right to privacy. As an extreme example, if your friend was dying, you had a password to my email, and you knew that you can use information in my inbox to save that person i really hope you would do it.
In general I think that police with a court order should be able to invade someone's privacy (with judge discretion). I mean they can already kick down someone's doors and detain them for several days - checking email doesn't sound too bad compared to it, does it? I think they should also be legally obliged to inform that person in let's say 6 months that they did it.
The problem is that modern world is drastically different than the old world when you needed to physically hunt down letters. Now you can mass scan everyone's emails, siphon terabytes of personal data that stasi could only dream of, and invigilate everyone. This is something that is worth fighting against.
reply