Recently, there's a lot of talk about AI allegedly finding security flaws in software. That is an unsubstantiated claim. As such, it would need to be verified by a non-machine, and arguably, the verification process would require the same amount of effort or more than would be required to find the issue to begin with.
Once a security issue is found, it is often far less effort to verify it. Digging through millions of lines of codes to find high-probability vulnerabilities is the hard part.
Yes, this works if your RSS server has its own DNS record that you control, and is essentially what the Domain Handle -> DID indirection gives you in AT Proto.
What Bluesky and AT Proto in general do is make it easy for people to either get a domain (a *.bsky.social subdomain) or use their own as their handle.
And AT Proto also lets you change your domain while preserving your identity, since the actual identity is a DID.
That makes it very easy to move your data and your handle around and not lose followers. If you change your RSS server's domain name, your subscribers don't come with you.
I don't think it's misleading at all, the comment you're looking to is.
People really do ask where "The AT Proto server is" as evidenced by this thread, and the really is no "AT Proto server" or "instance". AT Proto and BlueSky are a collection of services with no 1-1 relationship to a Mastodon or RSS server.
They shouldn't add the ternary operator, it keeps `?` from being usable on it's own for safe navigation and requires the ugly `?.` operator, like `a?.[b]` or `f?.()` instead of `a?[b]` or `f?()`.
Being against bad housing regulations is not "anti-regulatory sentiment". Some regulations just aren't good. We shouldn't valorize rules for the sake of rules.
I'm using it for a secure, language agnostic workflow orchestrator. Components have very finely-grained and controller permissions and access to data. They don't even get clocks by default (to mitigate against Spectre-style attacks) and credentials and tainted data are sequestered.
The component model is what unlocks relatively type-safe interop between modules written in different languages. Given that Wasm is a runtime target for many languages, this is an entirely appropriate and useful goal.
If you have a host system where you want to expose APIs in an language-agnostic way, IDLs are the best way to do that.
You're also conflating the core WebAssembly work with the WASI work. There is some overlap in people, but WASI is developed separately.
I don't use Apple Music, so opening their music player only wastes my attention and time. It happens if you accidentally press play on your headphones too. Then you need to quit Apple Music, for no good reason. And you can't uninstall it!
Angular should ditch the compiler altogether - it really hinders them in so many ways, especially now with AI-codegen where tools have to specifically choose to do the work to integrate the Angular toolchain instead of using plain TypeScript and HTML.
It will be really great if this becomes a second popular runtime with both GC and WASI component model support. Wasmtime being the only runtime with that combo is a bit concerning. Node supporting the component model will help a lot too.
That really isn't true. I know people who run their own PDSes, and who've moved their accounts from Bluesky's to their own and back. You can't do that kind of thing with Mastodon. Blacksky also runs their own PDS, relay, and app view.
And that's just the Bluesky-like apps. Other non-microblog atproto apps use their own PDS, or store data on yours.