Python is easy, not because it prevent people from doing complicated things, but because with only a few simple things, you are productive.
Most python programmer use 10% of the language, the same 10% that is described in most tutorial, because that's enough, and they don't even know the rest exist.
This makes for a very smooth, but long learning curve which allow you to enjoy python in the early years, yet keep getting a kick out of it after 15 years.
I hear a lot of people raising the same kind of concern you do in comments, but in the field, I never do with people actually using the language.
That "smooth learning curve" applies when you are learning the language, use it by yourself or work in the ML/Data science industry.
Once you get thrown in a big project that makes heavy use of type hinting (plus the whole environment of it, mypy et all), Object Oriented design and all those hidden things...you realize how much you really don't know.
And that 10% is way too small. To be productive in Python, you need to know at least 50%, or you will be reinventing a lot of existing things. Poorly.
Using a different language isn't going to stop the vertigo of being thrown into the deep end of an existing project without a mentor to guide you through it.
If you make a big project, you will have to use that many things with every langagues. If the language is rich, you'll learn the language. If not, you'll learn the project patterns. It's not specific to python.
But 99.9999999% projects won't implement metaclasses.
Most won't event implement decorators, context managers or generators. Use them, sure.
The REAL power comes from the libraries. In the Olden Days, we would call these 'subroutines' -- libraries contain the gussied-up subroutines that make it possible to do amazing things in Python with that "10% of the language" we use.
Yes, also for anything else than subclass registration, there are things like the descriptor protocol or class decorators that are likely to be easier to use, debug and understand.
And metaclasses can be any callable, not just class. It's usually better to use a simple function.
No because if it's standard, they will ask you to disable travel mode and download all the data. You can say no, but you can't refuse and cross the border.
It for sure is a technical issue and by “travel mode” I mean you:
1. end-to-end encrypt a cloud backup
2. Securely wipe the phone.
3. Install OS in travel mode, which means no local data is forced and at best kept until restarting phone. Hardware enforcement of ban of updates including firmware and OS, unless system wiped. With a visual unique easily recognizable “code” to tell if the current “travel mode” was over rewritten; for example, unique consistent computer generated recognizable human face is shown on reboot until being reformatted and is different every time phone is reformatted.
4. On reaching known safe point, phone wiped, OS installed in non-travel mode, backup installed.
If there’s no data or way to root the phone, it’s meaningless effort and would no longer even be done at the border; they might find another route to get data, but current issue would no longer be a viable route.
— to be fair, I did mention multiple-logins, but to me that was intended to mean additional features/options, not a replacement for the core issue of forced access to devices/data at predictable chock points like border crossings.
Nope, if an abusive administration is committed enough, it will mark as suspicious any cleaned phone, especially if they can access freely metadata about your life without a judge.
No need for the content, they just need to make sure the activity score is higher than the one on your phone. It's not illegal not to have you real phone, but why haven't you? Do you have anything to hide? And they will make you life annoying enough, making you miss flights, waste your time, cost you money and opportunities, until most of the population comply.
It's a cat and mouse game, where you are trying to oppose technical solutions to people being simply abusive, which doesn't work on the long run, because the problem is that you are being ruled by the mob.
It's funny, because if were it be happening in China or in Russia, everybody would be loosing their mind, saying how those dictatorships are abusive. Then they would note how the Russian and Chinese don't seem to notice they are being abused and defend their country.
They don't have to, they can just say the phone synchronized on its own when set back out of travel mode. They will lie, of pressure you to download the data prior their search.
Again, it's not a technical problem. Abusive people are abusive.
Law enforcers are not good people because of their title, society shape them in who their are and how they behave. Currently, in the US, they are not shaped to be helping citizen.
Article says they can hold onto your electronic devices tho. They can also probably arrest you for the legal maximum (which unlike proper jail probably won't result in you losing your living but could result in you losing money in addition to time).
They don't have to literally prevent you from entering your own country in order to make refusal to cooperate extremely unpleasant for you. Not to mention they can do this every time going forward and they can do this to other people in your group as well. Good luck proving this is harassment and not due dilligence.
But they can, and will if the trend of abuses continue, make you loose your flight, make you waste time, opportunity, and money. And put you in a list so that they do that every time your travel.
It's just lost forever, luckily I had many others, and didn't associate my whole life to any single account or provider, nor used social sign in, so it was not life altering, just a bit of work.
But selfishly, I hope those kind of story get published more and more so that people finally realized that what we told them not to do the for the last 20 years was not just for the sake of it.
People don't listen to preventive talks. We see that with cyber security, climate change, and so on.
They only start to move when they get hurt.
I wished people would have listened to us when we advised not to give everything to GAFAM, not to put everything online, and not everything on one provider. And certainly not to trust them with being on your side.
So they wouldn't have to get hurt.
But this is not how we, as a specie, learn. We need to get hurt.
So make sure a lot of people know about this. Not just in the hope to get the account back, but because maybe more people will listen this time.
What is the alternative? For Gmail, I take the precautions of configuring mobile phone, authenticator app, backup email address, and printed out codes. What else can I do? Is it really better to use several different email addresses?
For Facebook, I’m currently completely locked out. I have the right username and password, but the email accounts I used to create the Facebook account are disabled now, being university accounts.
At one point, Facebook wanted my credit card or driver’s license as proof to tenable the account, which I wasn’t comfortable with. Then it got paired down to three randomly chosen connections that I needed to contact outside of Facebook. Once chosen by Facebook, these contacts cannot be changed. For me, it included a deceased person and two people I haven't even seen since high school. Now, it just wants to validate the email addresses with no other options.
So now what? Nothing in my control ever went wrong. I know my account, I am the person, and I have the username and password. It would be nice to be able to just call a number with a human on the other line to verify that it is me.
We've entered the era of "death by scale". We and the government allow these companies to treat customers and people as statistical entities. They don't give a shit if their products either flat out don't work or ruin a customer's life for "only" x percent if x is small enough.
What you can do is to not use providers like Google or Facebook for you e-mail or identity. Pay for a good e-mail service with human beings in charge and use a safe password, probably a password manager that generates it.
Do you or others have suggestions for email providers? I have been considering using Fastmail.
Do people use custom domain names to get around the fact of switching email providers? Aren’t there rejection/filter issues when using custom domain names?
Facebook did offer you two ways to recover: a) provide your driving license or credit card (a reasonable offer, IMHO) and b) reaching out to your three friends online.
I agree that in b), it sucks that once chosen, the 3 people cannot be change (although I kinda see the security angle of it), but what else would you want Facebook to do if you lost access to your email?
Accept my username or password that's being rejected for no reason? Driver's license or credit card is unacceptable, to me, to give to an organization like Facebook. Still, those options went away.
I don't understand why it can't just ask me questions about my account. It's not like I'm resetting my password. It was Facebook that randomly decided it needs to send an email, something it never did for the longest time.
I never used facebook for this reason and advised people not to. Now that you are locked in, there is not good solution. It's like smoking and getting cancer, there is no magic to solve the problem and a lot of pain. The best is to not start.
For gmail, have several addresses, with redirections to each others, use imap, don't use social sign it.
Well, I never used Facebook for any login nor did I ever give them my personal phone number or email because I never had any reason to. I deactivated the account a couple years ago, which doesn't delete it. It would just be nice if they let me recover it, but they don't want that as they'd rather force me to create a new account to get their hooks in.
I also never use social sign in for anything other than using my GitHub account for certain things.
You can be annoyed all you want, but the process is insane. The only options available to me are my two university emails. One of the email domains simply no longer exists. I actually took the time today to call my old university, and they were kind enough to temporarily turn on my old university email address for the other email tied to my Facebook account. Facebook won't send the code to the email after I correctly login. It reports an error. (I verified that the email is working.) There's no way to report the error anywhere. The only way you can report an error to Facebook is to be logged into Facebook. There's another login screen that allows you to reset your password. I did so there since that actually worked by sending an email code. After I do that, it takes me back to the "browser verification" screen. Now, the email I verified has disappeared from that list! The only one left is the email that is tied to a domain that no longer exists. It is impossible to get an email at that address. It's ridiculous.
TLDR: I actually recovered my old university email address, and Facebook refuses to send a code to that email and has now removed it as an option.
For email I'd say the most important precaution is to have an address at some domain of your own.
You don't need to host the email servers yourself. Many email hosting services will let you use our own domain with them.
If you want to use an email hosting service that does not directly support using your own domain, many domain registrars include free email forwarding so you can forward mail sent to your domain to your address at your email host, although there might be problems with sending from your domain if you use the forwarding approach [note 1].
It might at first seem that this is just pushing the problem back a little. Instead of the problem being losing your account at a mail hosting service like Gmail, you now have to worry about losing your domain.
The big difference is that a domain registration is a lot more passive. With a Gmail or other mail hosting account it is something you are actively using. Content you generate goes through it. Content other people generate goes through it to you. That gives all kinds of opportunities to trigger false positives on their automated anti-abuse systems.
With a domain you register it and designate name servers and periodically pay to keep it from expiring. Most registrars include basic name service so you don't have to deal with finding a name service provider. Once you've set up name service to designate your email host as handling your domain, or set up forwarding if that's what you are doing, you pretty much don't have to touch anything there and content to/from you doesn't go through those systems so there is simply much less opportunity for something to trigger some sort of automated anti-abuse systems.
Pick you domain and registrar carefully. Don't pick a domain name that is close to some trademark. Pick a top level of .com or .net or maybe your country's top level if you are going to want to send email from that domain [note 2]. Pick a registrar that is not in some country likely to do things that get your country to put sanctions on it.
[note 1] You might not have enough control over the headers on outgoing mail to be able to send a mail that doesn't look like a forgery attempt. For email addresses that you will just need for receiving things the forward approach should be fine, which will cover email needed for account recovery in most cases.
[note 2] The newer top level domains that are available for general use have been pounced upon by large numbers of spammers, to the point that having an email address in them can make it very difficult to get through spam filters. Spammers are all over .com and .net too of course, but that's also where most of the non-spammers are too. With the newer top levels the spammers jump on in large numbers from the start and so from the point of view of a random email receiver those domains are mostly spam.
I use Namecheap and they have been fine. A lot of others on HN also use them. Some people didn't like it that they kicked off their Russian customers when Russia invaded Ukraine, but Namecheap has a lot of employees in Ukraine and it doesn't seem unreasonable to not provide service to places that are at war with where your employees are.
I've seen a lot of mention of Gandi on HN, mostly favorable.
nor used social sign in, so it was not life altering, just a bit of work
For most users, it’s not a bit of work, but a life changer (as in this case, right). Most sites only allow G and f SSI, and that’s it. Quick registration is a killer feature and it’s a shame that it is not a part of the tech stack at much lower level than google/site integration. It’s almost 20 years of mass-internet and it still sucks at account registration.
I don't want to nitpick but if they believe that most people only really learn through pain then they would likely also believe exacerbating pain is indeed helping.
And if ChargeBee bans you, you are still dead because that's a single point of failure. No, you should have several payment processors, and rotate them regularly to check they work.
Besides being a single point of failure, we tried to switch to ChargeBee and found them to be pretty lacking (to put it mildly). The platform looks nice and has lots of options, but under the hood things seem pretty fragile. Horrible docs, random 500 errors that weren't showing on the status page (and support ignored until more customers reported it), our Stripe gateway disconnected and the system still appeared to be working (partly, partly failing) with no alerts, plus lots of other odd behaviour. To be fair, all of this was on the test system, but we didn't feel confident to go live so we put the migration on hold. YMMV of course.
Under ChargeBee's terms, they must provide you with your data for up to 120 days following any termination. So there's that at least.
> 7.2.3. Data Export Following termination or expiration of a Subscription, We will retain that Account’s Service Data for one hundred twenty (120) days from such date of termination or expiration (“Data Retention Period”).
I mean, ideally we need an open source PCI compliant equivalent of ChargeBee so that you can 100% own your customers payment information.
That's the way this problem really gets solved, but the security surface for that open source project is going to be a challenge.
SLAs only entitle you to a refund, not compensation for lost income. If you’re not making at least four times as much off a service as you pay for it, you really need to think about why you use that service.
Power can go out. Promises from the power company don’t fix that. Only backup power does.
Point here was that you’d hypothetically be able to get all of your data to setup an alternative if you had to, rather than just being shut down and waiting for them to fix it.
Once you trust your vendors absolutely, your company becomes their company, because they can do whatever they want with it.
What always confuses me about this is that it seems like many owners trust their vendors over their own employees and I don't even know where to start unpacking that sentence.
The problem with that idea is that PCI compliance doesn't just include the software you're running, but the infrastructure you run it on, various elements of organisational security and, of course, certification costs.
It's been a while since I dealt with this side of ecommerce - how can you have several payment processors, and rotate them, without having to handle card data yourself? (Most folks aren't really equipped to do that.)
You use several API, attach one provider per customer to divide the risks. When one provider bails out, you onboard new customers and new payment on the other payment provider.
Then you only loose the recurring payments on the lost provider that are on hold, and you are not dying, so you can resolve that problem using a lawyer.
This is crisis management, not technical perfection that you need for those situations.
display_cc_form_that_handles_cc_data_so_we_do_not_have_to() {
which_one = random_number(3)
switch which_one {
case 1:
display_authorizedotnet_form()
break
case 2:
display_stripe_form()
break
default:
display_paypal_form()
}
}
Plus the same integration work for each one that you'd have to do anyway (which may be little or none if you're using a platform that integrates all of them via plugins or settings or whatever)
Like maybe don't literally randomize it request-by-request, but that's how you'd be ready to use multiple processors, and you could do something a little more complex to, say, rotate which one you're on every Wednesday, or whatever. Or just have it ready so a one-line code change or config toggle switches which one you're on (that's only worse because if something's not used frequently in prod, there's a good chance it doesn't actually work, even if it once did)
It's been a long time since I've worked in eCommerce but at my last ecom role we used two payment processors and simply stored the card data with both for every customer, and the relevant IDs in the customer record in the database. Whenever anything got charged we'd check which processor we were supposed to use and off we went.
Yes this has an increased cost if your processor charges by number of customers, but I don't think that's particularly common - these two were just revenue + monthly fee.
Great solution, I wouldn't have thought of this. Did you ever get complaints about the charge description looking different month to month, or did both processors pass the same description to the customer's credit card?
The problem is with recurring payments. If you used this approach and 1/3 of your customers were initially billed through Stripe, then if Stripe bans you then you can't charge the next month's bill through something else because you don't have the stored data for it, you have to ask them to re-enter data in another processor's system.
Another wrinkle, in practice, is that you can often negotiate significant discounts on fees, based on volume, if you've got enough of it. Yes, including with Stripe and other places that have fairly-transparent public pricing—the big-boys don't pay those rates, they pay lower ones negotiated with a sales rep.
Splitting up your payments reduces your volume with each one, which can mean you're paying higher rates overall. Or, if you go the "keep an unused alternative on standby" route, you'll likely at least have some initial traffic that pays higher public-pricing rates until you can convince them to give you a better rate, and put it in effect.
Still might be worth it as a kind of insurance premium, but it's something to consider.
This isn't "rotating payment providers", though, this is sharding customers across them. Which may be a good idea, insofar as it could reduce your blast radius, but it doesn't allow for portable customers--which seemed to be what the GGP was implying.
'pc86 has an interesting solution in a sibling comment, but I don't think you can do this across the high-touch providers, eg Stripe+Paypal.
Ethereum isn't supposed to be money (though it can be), it's fuel you use for doing other things. Do people use less oil because it's deflationary and gets consumed when used? No, because it's useful now.
The most likely end game for Ethereum is being a replacement for all backend financial systems. Instead of having to hire teams of people to verify things or integrate various legacy systems together, everyone can build on one neutral platform and pay a little ETH as the fee for using it.
Banks would never switch to a system that makes all transactions publicly traceable, and they shouldn't.
The industry has investigated blockchains for many years, since distributed consensus for transactions is a problem they actually have. They might run their own private chains. But it won't be ETH.
Conceptually, a service provider utilizing Ethereum could create or aggregate on-chain services and package them in a similar format to what a bank is today with very little overhead.
I heard exactly the same said about AWS in 2009, now almost every major bank uses it. Once something is shown to be more efficient those banks are going to have to adopt it or justify their inneficiency to their shareholders.
Lots of companies released blockchains and coins. It's called FOMO, or "Metoo-ism". Interpreting this (or IBM's blockchain) as signs of a significant market shift is a triumph of hope over realism.
It won't be public and it won't be distributed - it would quickly revert to some form of centralized piece, hopefully one at each bank, but will probably end up with one huge central point. They will still call it blockchain to attract gen z to work there, but behind the scenes it will work just as badly as the current mess. It's in the bank's/banking industry's blood and regulations to centralize. Whatever gets thrown their way will get locked down and centralized. I can just imagine the huge audit systems that will spring up to audit the blockchain (where ideally you wouldn't need to audit it to begin with, just look at it cause all the same info is in front of all parties, unmodified). Nightmare fuel actually. Better just to start from scratch (new banks, new core banking software, different kinds of audits and regulations).
Do those banks use AWS now? Did they fight it with many justifications of why bare metal is better and cheaper and more efficient before finally realising it's holding them back? Because that's what happened in every company I worked in and that same thing is going to happen to every company working in finance.
In a capitalistic world efficiency comes before pride or your shareholders replace you.
The only problem with this analogy is that “cloud” was able to quickly produce numerous examples of material cost savings. You’re right insomuch as the banks were all over it as soon as the business case was proven. But there’s nothing comparable in the crypto space.
Who is using crypto to deliver mainstream financial products (banking, insurance, credit cards, loans, mortgages) at lower cost?
AWS came out in 2007 and most companies barely started exploring it until at least 5 years later. All of the same arguments I heard about AWS back then I hear about Ethereum right now (it's more expensive, bare metal is more flexible, we have to recode things in the AWS way) but people have selective memories and think things that are obvious now were always obvious.
Most banks in Australia are working on crypto related products, Visa is too. Eventually once a few have a network together, especially internationally, the snowball accelerates because of Metcalfs law and soon it's more costly to not integrate.
The way I think of it is "if we had everything running on crypto rails, would companies want to switch back to what they have now" and the answer is obviously no, so it's just a matter of time until it happens.
It’s really non-obvious to me that there is any advantage of crypto that makes its use inevitable in financial products. Those Australian banks - are they crypto-related products in the sense that they appeal to crypto people (maybe a way to buy or trade crypto?), or are they actually more efficient versions of mainstream products? The idea that banks will inevitably adopt crypto because their crypto-using competitors will be more cost-efficient seems implausible to me. I just don’t see the mechanism for crypto being a cheaper way of doing things.
The merge won’t affect gas fees, which makes Eth unsuitable for small purchases when the network is busy. Apparently Eth will do other work in future to fix that though.
I never use stable coins for payment, and I don't know anybody who does despite being in crypto since btc was at $8. I do pay stuff in BTc and get paid in BTC once in a while and see people in my bubble do the same. We use stable coins to limit taxe exposure, mainly.
It's true eth has never been a mean of exchange for any of us and more a platform for smart contract (my friends at kryll.io use it for that).
The majority who trade crypto use stablecoins for payment all the time. It's the default on most exchanges, and for a lot of the biggest pairs on DEXs.
If you are talking about payments of non-crypto products, I was exploring the hiring for small jobs subs on reddit yesterday and the two main accepted means of payment I saw seemed to be PayPal and stablecoins.
ETH as cryptocurrency mainnet still has the same high gas fee when it was PoW. Some layer 2 solutions will have the utility to use their token as cryptocurrency because low gas fees.
Most python programmer use 10% of the language, the same 10% that is described in most tutorial, because that's enough, and they don't even know the rest exist.
This makes for a very smooth, but long learning curve which allow you to enjoy python in the early years, yet keep getting a kick out of it after 15 years.
I hear a lot of people raising the same kind of concern you do in comments, but in the field, I never do with people actually using the language.