482 karma · joined December 30, 2014
Edit: And god forbid you end up working on a core curriculum product that needs to be reviewed by each state's board of education. In that case you end up building a product that appeals to state-level bureaucrats, just to get get the privilege of selling to administrators, with little thought left for the actual students.
The N+1 query used as an example in the post could have just been a single query.
5.6.1 (2024-03-09)
IMPORTANT: This fixed bugs in the backdoor (CVE-2024-3094) (someone
had forgot to run Valgrind).is-number was first published 9 years ago, when these kind of micro-packages were in vogue. braces was added as a dependency to chokidar over 6 years ago [1]. And if it ain't broke, don't fix it. I don't think the average JS dev today is going out and pulling in these deps.
[1] https://github.com/paulmillr/chokidar/commit/cbdf25563cfff7f...
[1] https://money.cnn.com/2014/12/19/news/companies/government-b...
[1] https://www.tesla.com/ownersmanual/model3/en_us/GUID-F907200...
That's a lot more broad than "Chinese controlling interest".
Edit: and "controlling interest" as defined in the bill means "a holding with the power, whether direct or indirect and whether exercised or not exercised, to determine, direct, or decide important matters affecting an entity." which is much more broad than the commonly understood 51% equity stake.
[1] https://www.theguardian.com/business/2023/mar/11/silicon-val...
Edit: Interestingly enough, the demo site is listed in 1Password's own directory: https://passkeys.directory/details/web-authn-io/
As an example, given:
const sales = [ {month: "Jan", day: 1, total: 120 }, ... ]
You could determine, say, the highest sales day of a given month as follows: const highestSalesDayByMonth = _.chain(sales)
.groupBy("month")
.mapValues((salesForMonth) => _.maxBy(salesForMonth, "total"))
.mapValues("total")
.value()
// highestSalesDayByMonth = { Jan: 140, Feb: 90, ... }
Naturally, minimizing the complexity of the iteratee functions and carefully naming of their arguments is very important to ease debuggability. 1. You have 100 ETH in original ETH chain in wallet A.
2. Merge occurs, and a forked POW chain appears
3. You now have 100 ETH in wallet A, and 100 ETH-POW in wallet A.
4. Generate a new wallet B (note that because the protocol for ETH and ETH-POW is identical, wallet B is valid for both ETH and ETH-POW).
5. Transfer 100 ETH from wallet A to wallet B (on POS chain).
6. Observe both wallets on both chains:
Scenario A: There is no replay in ETH-POW:
- You have 100 ETH in Wallet B
- You have 100 ETH-POW in Wallet A
Scenario B: Your ETH transaction is replayed on ETH-POW
- You have 100 ETH in Wallet B
- You have 100 ETH-POW in Wallet B
In scenario A, you are free to do whatever you want with the 100 ETH-POW in wallet A -- either move it to an exchange that supports the ETH-POW chain, or continue using the ETH-POW chain. There is no risk of replay because wallet A on the POS chain is already empty.In scenario B, you still have both 100 ETH and 100 ETH-POW in wallet B which you control. Write off the 100 ETH-POW because the risk of interacting with it is likely much greater than any value the coins in that chain have.
In both scenarios, your 100 ETH is safe and controlled by you.
If the POS wallet address is empty (post split) there is no chance of replay because the address is already empty.
Of course, just as possible is a replay of the POS transaction on the POW chain, so the POS wallet chosen for the initial emptying should be 100% controlled by you as well (ie- not an exchange wallet).