HackerLangs
トップ新着トレンドコメント過去質問紹介求人

spankalee

11,775 カルマ登録 15 年前

コメント

spankalee
·11 時間前·議論
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.
spankalee
·12 時間前·議論
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.

There's absolutely nothing misleading about that.
spankalee
·15 時間前·議論
There is no "AT Proto server" - https://overreacted.io/there-are-no-instances-in-atproto/
spankalee
·15 時間前·議論
And how does RSS let you move your data to a new host while preserving your identity like AT Proto does?
spankalee
·3 日前·議論
Yes, but no official builds yet that I know. This is a really important issue for online playgrounds and IDEs.
spankalee
·16 日前·議論
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?()`.
spankalee
·20 日前·議論
So don't use compilers at all?
spankalee
·23 日前·議論
Do you think that once GCC gets a working Wasm backend[1], that it might be possible to build Linux for Wasm directly and skip the RISC-V VM?

[1]: https://www.phoronix.com/news/GCC-Steering-WebAssembly
spankalee
·23 日前·議論
No, there are people who look at the better and cheaper housing the rest of world has and who want that for us too.
spankalee
·23 日前·議論
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.
spankalee
·23 日前·議論
We need people to be less racist and stop voting for politicians they hope will hurt the right people.
spankalee
·25 日前·議論
You're supporting a company that makes a model that has been intentionally directed to think that white genocide is a major problem today.

You do you, but that's a very morally implicating choice you're making.
spankalee
·25 日前·議論
Browser users. Pre Mv3 extensions were a huge vector for malware. My in-laws were hit by that.
spankalee
·25 日前·議論
[flagged]
spankalee
·25 日前·議論
Yeah, I think calling the Mv3 versions "secure adblockers" would be more accurate.
spankalee
·29 日前·議論
The speaker is right. Why should "system" interfaces and interfaces from other components ever be fundamentally different?
spankalee
·29 日前·議論
There is an issue open for instantiating modules at runtime: https://github.com/WebAssembly/component-model/issues/423
spankalee
·29 日前·議論
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.
spankalee
·29 日前·議論
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.
spankalee
·先月·議論
These should really be web components. Leaving out every framework other than React is really bad for the web.