Профиль

The ATProto hammer is in full swing. Beware if you look like a nail, even in the distance in foggy weather 😂

Thanks, I didn't even know this one was NSFW. All the desktop screenshots need to be updated anyway, will try to do that later today.

@servo.org way ahead of all the other browser engines with a perfect score on WebCrypto tests: wpt.fyi/results/WebC... Remember that when you think that "the web can't change". It can, it's just being held back by incumbents.

hm, which screenshot? You're the second person noticing that, but this is not a default bookmark, it's a search result from a "top sites" list. The default bookmarks are servo.org, wikipedia, the article www.noemamag.com/we-need-to-r..., a PWA app store and the mediacenter remote control.

These are the default bookmarks, yes. (note that the homescreen is in dire need of being more functional, lol) What does that tell you?

We started to implement hardware APIs: so far we have screen control (brighness and on/off), as well as device shutdown & reboot. Next on the list is power source status and a idle detection API. Very happy with how closer to a BeaverPhone / BeaverDesk this starts to look like!

We can now build Beaver packages for @alpinelinux.bsky.social , both for x86_64 and aarch64 targets. The package offers both a regular desktop app mode, and a full session mode, with cage being used as a kiosk wayland compositor. Works pretty well when installed on a @postmarketos.org device!

Yes we want to re-wild your web!!

Ha ha... well I think they will have to fix at:// URIs to be actual URIs, and that <link> is the right semantics.

Why not a <link rel="at-comment" href="at://..."> element?

This probably won't happen in one of the "big 3" browser runtimes. This should take about 2-3 years with a project like Beaver. The work happening in the "mobile linux" is very important for the low level layer but the web is the only user space available with an established dev community.

I think most of the required parts are more or less available. In Beaver (tangled.org/me.webbeef.o...), we have: - p2p comms (backed by @iroh.computer !) leveraging the SOP. - Web Tiles + Tasks (~ intents) should enable distribution and composability. - Durable storage is a browser impl policy.

Important things first: what's wrong with the name? 🦫🤟🦫

I was using iroh-ssh (github.com/rustonbsd/ir...) that works well too, but the petnames support in pigeons is very nice!

Hey @tangled.org are email notifications supposed to work? I never receive any even though I have a verified email address and the "email notifications" option checked. Help!

But do you need an explicit channel with the host? That's what I'm not convinced about. This also makes the threat model harder to reason about because how open ended this looks.

Do you have concrete use cases? I can't think of any I could not implement with an intents-like system. Unless this is to accommodate the limitations of current web hosts?

🦫 Beaver's internal pages for networking error and directory listing now use the design tokens from the current theme. Pretty happy with how nice they look!

"Without this API developers are forced into splitting the application into separate ones which complicates distribution or bundle everything into a single huge application that can potentially confuse users." I would argue that their envisioned distribution model is the problem.

good signal