The biggest downside is that it looks like you can only use a single display from your Mac. If I could run 3+ screens from my mac, this would become a no-brainer.
It attempts to do what you're essentially describing. It was built by the MetaMask team, where supply chain attacks are an obviously huge risk.
I've spent some time trying to get it working in an app, but haven't been able to get it all the way working. It's still pretty beta and not well documented.
A kind of "web3 substack" app just launched their NFTs, doing exactly what it sounds like you're interested in doing. Their NFTs will provide utility (premium features) in their app - no equity or future token or anything.
Are you sure your target customer would be interested in buying your NFT? From a quick glance, there doesn't seem to be much overlap between crypto/NFTs and your startup. The space for new NFT drops is so saturated - there are new projects every single day, often with 10,000 NFTs for sale. Most of them do not sell out. To execute on this well, you need to build community around your NFTs and create hype, and then deliver a good result. It's not easy, even though it might look like "easy money".
Blockstack is working on a new version of our blockchain with smart contracting capabilities. We've created a new language, called Clarity, for smart contract development on our platform. It's lisp-based and is _not_ Turing complete. We believe that decidability is quite important for smart contracts. Algorand has joined our efforts, and they will support Clarity on their blockchain.
I am not involved with the development of Clarity, but I really enjoy writing smart contracts with it!
https://defipulse.com/ is a good dashboard that highlights the amount of money "locked" (i.e. as collateral) in various DeFi protocols. It currently indicates $8 billion USD worth of locked funds.
In reality, the number is lower, because folks use "yield farming". You can put some collateral in one protocol, use that to mint some funds, and then collateralize that in another protocol. And rinse and repeat. There was a Twitter post[0] recently where someone analyzed this, and they found that the "true" TLV was more like ~3.5 billion out of $6.7b.
The space is growing quite quickly. A month ago, the TLV was 50% of what is was right now.
As a non-paying user, this seems to be mostly fair. I used to do pretty remote trail running, and the route building feature was great for putting together a route and exporting it to my watch. If I get back into that type of running, then I'd probably be willing to pay just for that feature.
Hiding the "friends only" leaderboard seems like a bad idea on their part. That feature definitely drove engagement and friendly rivalries. It's not the same if it's only amongst your paid subscriber friends, which is not many.
I appreciate them doing more to get users to pay. I've never paid for Strava, despite having been a very active user in the past. I generally like them as a network, and wouldn't want them to go away.
The immediately breaking API changes are pretty bad. I wonder what the impetus was behind that move. Too complicated to have it act as a transition? Maybe they could have announced these changes, but have them start in 30 days, with a small discount for users if you subscribe before then.
While it is harder to actually do something, node helped me understand how web development "really" works. I started with Rails - I could put a simple app together, but I had no idea how it worked. It wasn't until I worked with node, where I had to do my own routing, controllers, models, database connections, etc, until I finally could understand what was happening under the hood in Rails.
No, it's not tied to a specific device. You can of course log back in, and keys are not "destroyed". We ask users to store a 12-word seed phrase, from which all other keys are derived from.
I'm an engineer at a platform that makes it easier to build privacy-friendly apps. This means that all apps on our platform have app-specific private keys stored on the client side (in localStorage), and they never touch a server.
With this change, you're essentially "logged out" after 7 days of inactivity.
This is pretty a bad user experience. I honestly am not sure how to mitigate this. MacOS Safari might not be a massive market, but iOS Safari is.
Any thoughts about how we should address this change?
Hey! This is a really interesting tool. We have a product already set up with Playwright/Jest, so this may come in pretty handy.
I see you have docs for converting a generated test to Typescript by hand, but it would be even better to pass a CLI flag to generate the TS test automatically. This would also lead to better types - i.e. `let browser: Browser;` vs. just `let browser`. Oh - looks like you're already tracking that! https://github.com/qawolf/qawolf/issues/353
Another request would be to specify the output location of the generated test. We already have integration tests at `/tests/integration/*`, and I'd prefer to keep them all in there.
When I was starting my engineering career, it was right around when the first DARPA challenges had started. The hype was beginning, and my optimism towards technology was strong. I thought the predictions and timelines would be correct, and I still feel strongly that self-driving will be safer than humans in the long term.
Recently, I bought a newer Subaru, with EyeSight. It has adaptive cruise and lane keep assist. The LKA is fine - it'll beep if you sway outside of a lane, and automatically adjusts the steering, but it won't keep you centered. It's more of a safety thing, and it works well from that perspective.
The adaptive cruise is really good. It's camera based, and I have had zero problems with it. It works well at night and in pouring rain. It'll even stay pretty close to the car ahead of you if you turn the "tolerance" all the way down. I'm always impressed.
Since I've had this car, I've thought a lot more about the practical implementation details of actual self-driving. I more often notice situations when driving that are seriously complex.
The more I think about it while I'm driving, the more I realize how fucking hard self-driving would be.
He dives into "podcast promoters" that are pretty effective at getting into the top charts. I mention this not because I think you should use these services, but because he actually gets some evidence around what the charts are based off of.
> absolute pitch, the rare ability to identify a musical note like F# just by hearing it, can be a massive benefit to a musician. you can learn the skill in a matter of weeks, but it can only be acquired before the age of 7. only 0.01% of people end up learning it in time!
I find it dubious that you can only learn this by age 7 - although I'm sure it's easier if you're younger. Is there science behind this claim?
I am not a musician, but I have recently started learning to play piano, and training my ear is something I'd really like to learn. I've used some apps to practice ear training, and I'm able to discern intervals decently, but I can't recognize and identify a single note on its own. I do hope I can get there with more deliberate practice.
Yes, totally understood. I am just thinking in line with a different response that this could be an easy way to prove if they’re still snooping - not a guarantee that they aren’t.
Couldn't you sort of test this by enabling E2E, sending a link that was previously blocked, and seeing if it is still blocked? That would at least show some sign if it's all a sham or not.
It gives you SSR with React out of the box. It's really nice to work with, and flexible enough that we haven't had issues with more customized situations.
The biggest downside is that it looks like you can only use a single display from your Mac. If I could run 3+ screens from my mac, this would become a no-brainer.