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.
I am expecting a lot of apps to be able to cast a window directly to visionOS devices by the time this thing actually launches or possibly a way to split out spaces into their own screens by the time this launches.
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.
Thanks, I'm super interested in anything that tackles this problem.
Deno's approach seems most promising so far since it's really ideal to have this built in to the core runtime, but it's not really very useful yet as implemented and I don't know whether taking it further is a priority for them.
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".
Definitely not easy, we are going to be building the community with our strategy starting this weekend. We are also not releasing an NFT until there is a community around the app. Good points though and definitely something I will think about. Thanks!
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.
The route builder has improved a great deal in recent times; they leverage the data they have to pick common routes for runners/riders. Have discovered several interesting places to run locally that I wasn't aware of, and its also fantastic for planning a commute (i.e. bike riders tend to on aggregate, avoid dangerous/unfriendly routes, so the planner ends up doing so as well).
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.
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?
Being logged out after 7 days of inactivity could be a little bit annoying but I can live with that, as long as I can log in again.
I could be misinterpreting your comment but are you saying your keys are simply destroyed upon this “log out”? Then I’m not really sure why your platform was considered working in the first place, if it’s tied to a specific browser of a specific device and won’t survive a clearing of storage which any user can do at any time for a variety of reasons?
What if someone accidentally erases everything because that’s what they’re told when something doesn’t work right? Answer: it’s volatile storage in the first place, and a tiny one at that. Heck some browsers can be configured to erase everything when closed (when operating in non-incognito/private mode).
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.
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.