nasso_dev

you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled)

this is true today only because nobody has made an alternative "frontend". but the data is there, public, for anybody to see. they can't take it from you even if they really wanted to. in fact, tangled has been working on making it easier for such third-party "frontends" to exist: https://blog.tangled.org/bobbin/

and Bluesky for your login to keep working

you seem to be misinformed. "your login" is handled by your PDS, whichever it is. self-hosting a PDS doesn't require you to host anything beyond a sqlite database and a websocket connection. they are easy and very cheap to host, nothing like a "complex constellation of social media components"

today you can already 100% use atproto apps without having any ties whatsoever to bluesky:

- data: non-bluesky-hosted pds (either your own or some other host) for your data

- identity: the did:plc directory is managed by an independent swiss association, but you can even use did:web if you really want to

- relays/apps: blacksky is an example of a fully independent stack

im not even thinking about "sign in with google" here tbh im just thinking about how if google decides to block your access to gmail you won't be able to receive emails for things like verification codes, account recovery etc..

this is like complaining that you can't login anywhere because google banned your gmail account...

"being on tangled" really just means "publishing sh.tangled.* atproto records"

the beauty of atproto means that you are in no way tied to the VC funded company behind the web app available at tangled.org. you merely publish your git repository using a protocol that this app will pick up and present with a nice UI

any other app that speaks atproto and looks at those same sh.tangled.* records will be able to access everything in the same way

and even the git repository itself doesn't need to be hosted by tangled the company, you can host your repository yourself. all you need is a server that can speak git, ssh, http and websocket

uh oh... does anybody here have a divergence meter?

On the Valve side, Rubikon continues to evolve and Dirk has developed optimizations (similar to those in Box3D) in a new engine called Ragnarok. Look for that in future Valve games.

wait....

or, maybe, as a form of protest? many people are actively against AI for ethical/moral/personal reasons, so they want to avoid using software made with it

you can see it sort of like making a list of vegan restaurants. you might not see anything wrong with other restaurants (they might even have vegan dishes) but to some people it makes all the difference because they get to choose who they support

french radio "France Musique" aired it the other day, i don't know if its available outside of france though

it's a bit of a shame that TFA does not mention that this is a non-standard API pushed by google only (all three editors of the draft are google engineers)

both Mozilla[1] and Apple[2] are opposed to it

encouraging people to build apps that only work in google web browsers actively harms the web and sends a signal to google that they can in fact keep doing this

[1] https://mozilla.github.io/standards-positions/#native-file-s...

[2] https://webkit.org/standards-positions/#position-28

stopped reading when i saw the AI illustration. wholly unnecessary, and it feels insulting to be fed slop like this...

if you really want a fun drawing get a human artist to do it. it doesn't need to be complicated, for example https://www.code-cartoons.com/ is mostly just stick figures and does an excellent job

but you don't even need any of that, a mermaid diagram would have worked perfectly fine too. instead you chose to use a technology that is known to be harmful

interestingly, french speakers just have to pronounce "wero" as "nouro" for the same pun to work ("eux-ro" vs "nous-ro")

titling "Building for the Future" the announcement of a mass lay-off is disgusting and makes me sick to be honest

is this really the future we want to build?

are you saying c++ can be used as a basis for other projects whereas rust cannot? ...why?

it is indeed pretty weird. clippy has a lint against this iirc. it's recommended to just create a custom error type, even if its just an empty struct or a single-variant enum

this lets you implement `std::error::Error`, which you really should to make it less painful when you want to erase the type (`std::error::Error` is `dyn`-compatible)

wow we're at ffmpeg 101 already? ffmpeg 8 felt like yesterday

check out https://margin.at !

im not an expert on a11y best practices, but id say an <img> tag with alt text is enough

for inline SVG, i read somewhere you can use <title> and <desc> to describe the SVG document, but i don't know how they work in practice

this is super cool as an art form but ASCII art is an accessibility nightmare so please don't use it for docs unless you know what you're doing and have made it accessible in some other way

they definitely are. im not sure why they did that, still pictures are okay too and much greener

Aren't procedural macros amd build.rs arbitrary code being executed at build time?

i like the points the article makes, but i really wish it used looping videos instead of actual GIFs

i don't really see any reason to use GIFs here; any widely available video codec like H.264, VP8/VP9 or AV1 will result in significantly smaller file sizes, look better, and will allow enabling controls for seeking and play/pause

See also: https://vert.sh/

Judging by the comments: was this project built by an LLM, posted here by an LLM, the replies to comments written by an LLM?

Is there even a human at any step or is this an agent running in the background with "go to HN front page" as its ultimate goal?

It's a bit sad that this is using Svelte 3 instead of Svelte 5, which changed its reactivity model to signals!

Displaying comments is cheap because the AppView (the "cache" layer that consumes the aggregated feed of records from the relay) can maintain a relational database of the social web/graph.

When it receives a post, it creates a row in the Post table. When it receives a comment, it creates a row in the Comment table, which has a column pointing to the Post it's replying to. Then, getting all comments under a post is easy SQL.

About your second question: yes, you're correct. What handle you use and where your data is hosted are completely separate matters.

used to be, in the early days, but nowadays runtimes optimized the function call overhead between WASM and JS to near zero

https://hacks.mozilla.org/2018/10/calls-between-javascript-a...

I don't know if it's just me but in my case the problem isn't really the crypto bs, but rather Brendan Eich himself.

As much as Mozilla and Firefox can be criticized for both technical and non-technical reasons, at least I share the same core values. I don't seem to share any core value with Brave or its creator. Plus, yeah, still smells like Google :)

I agree, it feels like it should be how you describe it.

But if Evan Wallace didn't obsess over performance when building Figma, it wouldn't be what it is today. Sometimes, performance is a feature.

Seems like passkeys use a very simple model where you are using a single device with a single browser or are somehow syncing across devices with some cloud service - and from your description it sounds like that doesn't even work.

Unlike passwords, you can have multiple passkeys per account. You can have 5 passkeys for your amazon account if you use your amazon account on 5 different devices. If you lose device 4, or if it gets stolen, you can just delete passkey 4. The other ones are safe.

Or, you can use a syncing service like a password manager. Both solutions work!

Note that having a unique fingerprint becomes actually great if it's so unique that even after a page refresh you get a different one.

Most browsers with fingerprint protections will for example introduce random noise in graphics and audio APIs.