Loading video...

Video Failed to Load

Go Home

Nuxt Auth Utils v0.4 is out! ✨ New features include: - Passkeys (WebAuthn) support - Password hashing utilities - Dropbox OAuth provider Note: This release includes a few breaking changes ⚠️ Kudos to Gerben Mulder for the incredible work on passkeys support! 💚

18,519 views • 2 years ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

Oren Melamed

29,555 views • 8 months ago

What is XRP Ledger 3.3.0 Upgrade? The XRP Ledger is moving from version 3.2.1 to 3.3.0, bringing a substantial set of protocol changes. But there is an important distinction. The 3.3.0 software release does not mean every new feature is already active on the XRPL mainnet. The release gives validators the software needed to support new amendments, which must separately pass the XRPL's amendment process. Put simply, this upgrade is less about changing how the entire XRP Ledger works and more about giving it new tools for payments, tokenization, privacy and institutional use. Here are the major changes: (1) Batch Transactions Batch transactions allow multiple transactions to be packaged and executed as a single atomic unit. That means a group of related transactions can either succeed together or fail together. This could be particularly useful for institutional delivery versus payment, where an asset and payment need to settle together without leaving one side completed while the other fails. The XLS-56 standard defines the Batch design and allows multiple transactions to be processed as one atomic unit. (2) Permission Delegation Permission Delegation allows an account to grant specific transaction permissions without handing another party control of its main private key. That could make operational wallets easier to manage for institutions. For example, a business could delegate certain actions to another party while retaining control over the underlying account. The important point is that delegation is limited by the permissions granted, rather than becoming a transfer of complete account ownership. (3) Sponsor Sponsor tackles one of XRPL's less visible barriers for new users. Accounts and certain ledger objects require XRP reserves, while transactions also require fees. Sponsor allows another account to cover those costs on behalf of a user. That could be useful for neobanks, wallets and other applications that want customers to use XRPL without first acquiring XRP simply to satisfy network requirements. The XLS-68 proposal specifically covers sponsored fees and reserves while keeping the user's account control intact. (4) Confidential Transfers Confidential Transfers bring a limited form of privacy to Multi-Purpose Tokens, or MPTs. The feature is designed to hide certain balances and transfer amounts while preserving mechanisms for authorized parties to verify information when required. This is important for institutions handling tokenized assets because complete public visibility can create problems around commercially sensitive transactions. However, this is not full account anonymity. The feature is focused on MPTs. It does not suddenly make XRP transactions private across the entire XRP Ledger. (5) Dynamic MPT Dynamic Multi-Purpose Tokens make MPTs more flexible after issuance. Token issuers can designate certain properties as mutable when creating the token. Those permitted properties can then be changed later without making every part of the token freely editable. That could matter for tokenized real-world assets whose requirements may change over time. The XLS-94 proposal is designed specifically around this controlled flexibility. (6) Fixes And Protocol Improvements Not everything included in XRPL 3.3.0 is a headline feature. The release also contains software fixes, security improvements, performance work and other protocol changes. The official 3.3.0 release includes Batch V1.1, Confidential Transfer for MPTs, Sponsor and Dynamic MPT work, alongside numerous fixes and engineering changes. There is also an important history behind some of these features. Earlier versions of Batch and Permission Delegation encountered security issues before activation, leading developers to work on revised implementations. That means the new versions are not simply new features appearing overnight. They are also the result of the XRPL's amendment and security review process. And this is perhaps the most important thing to understand about XRPL 3.3.0. A software release is not the same thing as a network activation. Validators still need to support individual amendments through the XRP Ledger's governance process before those capabilities become active. So XRPL 3.3.0 should be viewed as an important infrastructure milestone rather than six new features suddenly switching on simultaneously. Together, these changes push the XRP Ledger further toward the infrastructure needed for tokenized finance and institutional blockchain applications.

BSCN

16,661 views • 1 month ago

Burn Session #001 for $HUB is here! 🔥 🌟 Today marks a special day for $HUB - our first-ever token burn session! Each like, retweet, and comment on this thread will burn 1 $HUB token + 1 $HUB burned per follower. Let’s burn! 🔥 💪 A massive shoutout to our developers working tirelessly behind the scenes. Your dedication and hard work are the backbone of $HUB ’s success. Thank youfor turning visions into reality! 🙏 To our advisors, thank you for your wisdom and guidance. Your insights have been invaluable in navigating the complex world of blockchain and #DRC20. 🎉 Cheers to our 3,000+ Twitter followers! Your support fuels our journey, and we're thrilled to have you with us. 🤝 A big thank you to our incredible community. Your enthusiasm and kindness make $HUB more than just a token; it's a family. We're proud of what we're building together. 🐕 Shoutout to $DOGI, the pioneer and standard-bearer of #DRC20. Your trailblazing spirit inspires us all. 🙌 Thanks to $DCEX for believing in us from day one and for your support in incubating our project. Your faith in us is a driving force. 👏 Kudos to for their fantastic marketplace and commitment to promoting #DRC20. Your efforts are shaping the future of decentralized trading. 🏗️ To all the builders of #DRC20, we're here to support your growth and help unleash the full potential of DRC20. Let's build a stronger ecosystem together. 🤝 A heartfelt thanks to the CEXs like AscendeX and Gate for trusting us and working towards integrating #DRC20. Your collaboration is key to our mutual success. And we don’t forget the ones currently implementing #DRC20, we’re here to help if needed ! 💚 Finally, to everyone who's given us strength and support - we're doing this for you, for $HUB, and for the #DRC20. Our story is just beginning, and the best is yet to come. Now, let’s burn 🔥. One comment, one $HUB burned. One repost, one $HUB burned. One like, one $HUB burned. Oh, and one $HUB burned/follower.

Doginals Hub

25,858 views • 2 years ago

⚡️INTRODUCING HARDSTAKE, BOOSTS AND SAFE LP TRANSFERS This very important update concerns creators, users, liquidity providers and integrators. Please read carefully and hang tight HARDSTAKE: A new router function that allows projects to implement any custom staking logic safely on any ERC20, adhering to the Ethervista Euler model. This opens up new possibilities for token economics, including locking LP tokens permanently while still earning rewards - effectively "burning" tokens without losing benefits. The $VISTA token will be the first to implement HARDSTAKE 👇 Ethervista will now offer BOOSTS, allowing new projects to advertise directly on for an ETH fee. This feature gives launched tokens instant exposure to our large user base. All BOOST fees go straight to $VISTA stakers. It's our way of ensuring supporters benefit directly from ETHERVISTA's growth. This system exemplifies our core idea: traders, creators, and providers working together to create value for everyone involved. To ensure a smooth rollout of these new features, we're implementing a phased approach: 1. One-week integration period: We're giving everyone time to adapt to these changes and build accordingly before deploying to mainnet. 2. Public audit: During this week, we're opening a public audit period. Any bugs found will be generously rewarded 3. Documentation: Comprehensive documentation is available at providing detailed information on HARDSTAKE and safe LP transfers. 4. Developer support: We've opened a dedicated developer chat on Discord to offer full support and answer any questions during the integration process.

Ethervista

40,145 views • 2 years ago