If you work for one month and you are at the mercy of the other party to decide if they need to pay you, it's not any more easy money than the lottery.
I've definitely been there! Finding P1s for full read/write access and then seeing the report downgraded to a P3, and having to have the platform arbitrate and bump it back to P1.
However, it was this experience of mine as a part-time security researcher that actually led to us creating the bug bounty program for TigerBeetle's consensus.
For example, if you're looking at another database and find a correctness bug, there might not be a bounty program at all. Whereas with TigerBeetle, there hasn't been a single valid report that we haven't awarded, at least so far.
It's also why we were careful to rather be upfront and explicit about scope, than disappoint anyone after the fact.
And we recognize that consensus is hard and takes time to learn, hence the $8192 award for correctness finds.
That said, I hope you can see from the leaderboard that we've been generous. For example, Alex Miller found a bug in Apple's O_DSYNC and we nevertheless awarded $1024 because it was such a great find (Apple thought so too!).
I think they are pretty open about what they can afford to pay. If you have self selected to be worth $2000 a day due to expertise or necessity, then you know that you're not a good fit for them.
However many people are willing to put in the work, so why are you so critical of their program.
Do you think they are taking advantage of people who should charge more? Or do you think they will not get anyone good for such a low rate, and thus fool themselves into thinking they are secure?
Even before talking about the typing system itself, annotations existed by themselves and are not attached to any behavior in Python: they simply hold metadata.
When Python 3 came out, annotations were indeed added to the language, but no use case was decided for them. It was an experiment to see what the community would do with them instead of forcing a use case base on what the core devs would think would be useful.
In order to allow this, annotations where permitted to be any legal python expression.
Nowadays, type hints have won: annotations are widely used to add static type checking in Python. But the way the language treat them have not changed much appart from becomming lazy. While mypy cannot understand dynamic Python expressions in them, those are nevertheless legal syntax, and will result in correct metadata at runtime.
Therefore, were the typing system not turing complete, the annotations would have been anyway by nature of being basically an exec().
That’s not at all what’s going on here. While the Python interpreter permits and executes arbitrary expressions as annotations, Python static type checkers (mypy, Pytype, Pyre, Pyright) do not. This isn’t just an implementation limitation; the typing specifications (PEP 484 and successors) don’t allow it. For example, although these two definitions evaluate to the same result at runtime:
only the first is correctly typed by PEP 484. mypy rejects the second with “error: Invalid type comment or annotation”.
That’s the whole idea of static type checking: in return for restricting yourself to a controlled subset of the language that isn’t “too dynamic”, you gain the ability to type-check your code without running it.
The result of this paper is that one can nonetheless abuse subtyping to perform Turing-complete computation in the type checker. The computation doesn’t happen when your code is executed (annotations have no effect on the Python interpreter at runtime unless your program chooses to inspect them), it happens when you run mypy on it.
This is generally considered undesirable, because we want type checking to be decidable, and Turing-complete computation is not.
> That’s the whole idea of static type checking: in return for restricting yourself to a controlled subset of the language that isn’t “too dynamic”, you gain the ability to type-check your code without running it.
Eh, you are mixing up distinctions.
All that's required of _static_ typing is that your static type specification finishes running before you start your program.
Whether that static type specification language is Turing complete or not is a completely separate issue. And, yes, you are right that it's generally useful for that language to be decidable. But see eg Haskell's UndecidableInstances.
I’m sure that you understood the important differences, but there are likely many readers who didn’t (many more programmers are familiar with Python than with mypy). When you write “even if we don’t have P, we’d have Q anyway”, the reader is left with the impression that P and Q are somehow interchangeable or equivalent or comparable—that P is unimportant in the presence of Q. I think it’s instructive to point out that this impression would be mistaken, and the paper’s result of P is interesting and consequential.
Dependency injections, foreign-language bridges, data validation and parsing, etc.
But thanks to how we can introspect annotations, we could have a specialized syntax for types that would be also usable for those things, while the other way around would be harder.
So it's nice we went the type hints road, because you can now define types, and yet have wonderful libs like pydantic, fastapi, typer, taichi and so on.
Pydantic typing differs from mypy typing. Optional[T] means something different under the two.
I designed typedload before pydantic was a thing and I made it with mypy in mind already, and with the idea of using the standard library, not defining my own dataclass.
Unfortunately mypy has a limitation so you can't make a function that takes Type[T] and returns T. You can define it but it won't work for all types. There is still discussion on how to provide this feature.
django-ninja and fastapi does dep injection, parsing and validation based on annotations.
taichi does ffi with their own dsl, cython with c.
I you haven't tried pydantic or sister projects (django-ninja, fastapi and typer), this is a good place to start. They bring a breath of fresh air and are quite fun to use.
The dep injection is fastapi and typer code though, and quite tied to it. So it's worth mentioning that somebody is attempting (quite successfully from the look of it) to create a generic lib of dep injection using annotation named DI, inspired by those libs: https://github.com/adriangb/di
It's not one of those that you listed, but the @dataclass decorator uses type hints to auto-generate classes and class constructors (__init__ method) for you.
An example:
@dataclass
class HackerNewsPost:
title: str
author: str
votes: int = 0
This will generate a constructor that looks like this:
def __init__(title: str, author: str, votes: int = 0):
self.title = title
self.author = author
self.votes = votes
This is pretty useful, writing __init__ boilerplate has been a common thing in my experience using Python, and it makes code more compact and readable.
Combined with the cog (https://nedbatchelder.com/code/cog) to have the c declaration in a proper separate c file, but included in the docstring, you could have the best of both worlds.
There's a library for simulating the Excel calculation engine in Python. It uses annotations to hint functions, but according to Excel's type system, not Python's. Then at runtime, those hints are used to do conversion and promotion based on how Excel does it, so you can do e.g. the equivalent of "1" + 1 and get 2.
It's either xlcalculator or pycel, one of the two. I forgot which one does it that way.
Does this still work with Python 3.10 changes removing runtime evaluation of type annotations? I seem to recall this screwed me when I was writing something for runtime usage of types.
we still don't know what's going to happen with type hints in future though, but I'm sure things won't break as they might have broken if they changed the default behaviour
Yes, and very few people use that because most users can't tell an app from a website, spell URL correctly or tell you what "" does in google.
When I need those features I use the operators directly in the search field anyway.
The single omniscient search field is an amazing interface, it's incredible at what it does, which is understanding what our idiodic human brain is attempting to express with sausage fingers a monday morning.
That's impossiboe by design. There are different cuaracters that look identical, foreign alphabets and special characters. Then there are GUids and queries in url
Hiring economists into tech has also been going on for many years at this point. I roomed with a PhD candidate years ago who described fairly established hiring pipelines from Economics PhD programs into industry.
It's 98% for the condom itself, but if you couple it with the fact that the 2% failure rate has to correspond with an ejaculation in an ovulating female's vagina, the actual effectiveness is much higher.
That's not accurate (if it were, we wouldn't have efficacy rates for coitus interruptus and the rhythm method that this can be directly compared to, which we do); but the rate is per year, not per act. From the link:
>When used correctly every time you have sex, male condoms are 98% effective. This means 2 out of 100 people will become pregnant in 1 year when male condoms are used as contraception.
On the other hand, over 20 years, that translates to an efficacy rate of only 67%.
Its amazing to me how easily people are willing to give Apple their data compared to Google, Facebook or Microsoft. Specially looking at how Apple was to willing to put its servers in countries that want control of the data. I think people seem to forget the privacy fight was not about privacy from advertisers but from government over reach. People are looking at Google for building skynet but Apple seems to be successfully building it and people are enthusiastically adopting it.
Apple has a really strong track record of resisting Government intrusion, within the bounds of the law, not selling customer data to third parties, and holding app developers to account for the privacy of their apps. The others have business models based entirely on selling user data.
The contentious element is the "within the bounds of the law" bit. In the US and Europe that means a lot, because Apple can use the courts to block government overreach and they have done so. In China they can't do that, so they don't just as nobody else operating within China can.
Google does deserve credit for refusing to operate their search services within China, while Apple and many other companies decided they were willing to do business there on Chinese government terms.
I'm genuinely getting pretty annoyed by this increasingly prevalent style of know-it-all neo-ludditism that manifests as middlebrow, pithy dismissals of entire technologies with obvious benefits.
If you have a viewpoint on the relative risks of these technologies, the I genuinely wish you'd use your time to talk productively about what you think the risks are to help others make an informed choice – instead of sarcastically assuming that anybody who doesn't have the exact same set of priorities as you is a fucking idiot. It's making the quality of discussion on this site totally unbearable.
Well, asbestos has obvious benefits. It's an amazing, cheap way to insulate things, and it's very resistant to fire.
We knew abestos was dangerous even before the WW2, and kept using it because it was so convenient.
That's the thing about know-it-all neo-ludditism pithy dismissals. They started 30 years ago witha much more soft tone. But since not only people ignored the warnings, but eventually even came to insult the people performing said warning (even after the warning proved to be true), the same people turned kinda sarcarstics.
Poor you to have to read a rational argument in a comment using history and logic to underline our societies shit where they eat and ignore the asymetry of risk.
Sacarstic people are mean and don't understand how to have quality discussions. They should always stay perfectly calm and neutral while they feel like half of the population is setting us up for troubles.
>Poor you to have to read a rational argument in a comment using history and logic
Your comment above didn't actually contain any such thing. It contained a vestigial semblance of them too trivialised by vitriol to land a persuasive point.
>Sacarstic people are mean and don't understand how to have quality discussions.
Not always for sure, but yes that's often the case.
Because 3 letters agencies never, ever had backdoors in popular systems. It's not like the US had an illegal massive secret cabale dedicated to mass spying on its own population after all.
Luckily, Apple plateforms are notoriously open so it will be easy to check. It's great that we don't have to take their word for it after they lied about not being part of any PRISM-like program.
Anyways, all that doesn't matter much. Why would it be a problem when the economy, climate, international politics and the democracy are so stable these days? I can't see any reason why history would repeat and powerful entities would abuse any power they get.
Somebody who thinks like that would be a crazy tin hat conspirationist, and not at all a concerned citizen.
No, only the part of the population ready to spend hundred of dollars on an upgrade to get copy/paste must be capable of rational thinking. Anybody else is biased.
Unless it was built with this in mind, you absolutely don't have access to this.
Full data lineage is a complex task.
A very simple example would just be that a database is destructively updated by some script at some time. What's the log here? What ran? Can you actually replicate it? Do you have full backup of the data before?
As someone who's arguably professionally employed to do things like tell people where money is in the financial system, no, you can't.
In the same way you can't enumerate the atoms or molecules in a human body. sure, you can come up with good estimates and summaries that are useful, but not the actual full and truthful state of affairs.
In addition, you are a self-referential participant in the system: so acting in an attempt to observe such likely immediately makes your information at least partially incorrect.
Additionally, if we can't get full/transparency or introspection into machine learning models or neural networks (and we can't because i don't believe we even possess the theoretical knowledge of how to do so), it should also be wilfully apparent that we can't actually know the true lineage or dependencies of systems that implement such in production.
Not to mention the difficulties as the inputs/outputs of such pass in and out of the notional entity or system being observed.
You can follow the chains to a degree, but that assumes you have access. At work, you can follow things until it gets to a spool file, but you won’t have access to the system/code that reads the file.
The project looks nice, and I will certainly follow it.
But the author expresses way too much confidence in the description of the project. It has no test, no type hints, no pluggable error handling, not fall back when the redis instance dies, and has been used in prod by apparently a single entity.
Stating "WakaQ is stable and ready to use in production" is irresponsible, as a task queue is critical infrastructure and this could lure devs into thinking this code is way more mature than it is.
Of course, one should do due diligences when evaluation a new part of the stack. I also appreciate the enthousiasm of the article, and I'm sure the code already procudes many benefits for the author.
But no, a asynchronous execution system dealing with priority, resiliance and network messages, that have existed for a month, is in no way stable and ready. It's nascent and promising.