thisnow.be

@cossssmin I did some patch on css nesting for pseudo selectors. Cool. Cool Cool cool.

@_this_now Yeah it was behind on modern CSS like with :has or nesting, mentioned in the PR 👍

Spent this afternoon rewriting the Juice CSS inlining library so that it works with modern CSS, is more secure, and uses a modern dev stack. `juice@​next` is the new v12 beta, check it out if you need to inline CSS in HTML like we do for emails: github.com/Automattic/jui…

@cossssmin Nice. I've been using aspect ratio with cloudinary and generally bind for width.

Added aspect ratio support for the <Img /> component in Maizzle 6. Use a prop or a Tailwind utility, it just works and handles everything for you, including Outlook 👌

I just published Welcome to Gas City medium.com/p/welcome-to-g… In a nutshell, some actually good engineers came along and rewrote Gas Town into an enterprise grade SDK for building your own orchestrators. It uses the original Gas Town MEOW stack, based on Beads and Dolt. MIT-licensed. It has been out for a few weeks, just launched to v1.0.0, and is ready for use. Check out Discord at gastownhall.ai for more info.

@Holochain Praise the Claude. Every day I am holo clauding...

Developers: The landscape is shifting fast. Which AI coding assistant is doing the most heavy lifting for you right now?👇 Claude Code, Codex, Cursor, Copilot, or something else? Let us know in the replies. #DevTools #SoftwareEngineering #AI

@EricDoriean By alternative to centralised global identity. So... props to you

@EricDoriean Especially since, if we want an alternative, we are going to have to build it.

I watched this World ID 4.0 presentation Sam Altman & co put on the other day. A few people have asked what I think, given the work I do on identity and proof of humanity. Honestly, my reaction is more layered than I thought it might be. At face value, it actually does a lot right. Open protocol. Zero-Knowledge proofs. Biometric data that stays on the user's device. These are genuinely good design choices. There are scenarios where what they've built could useful. Iris biometrics are strong. Hardware attested verification has anti-Sybil properties that pure software can't easily match. But proof of humanity is too important to leave to any single scheme. There are some structural concerns I keep coming back to. The trust chain has unverifiable links. The orb hardware and firmware are open source in design, but you can't verify the orb in front of you actually runs that source. Same shape problem as voting machines. The app is its own version of this. The thing actually handling your biometric data on your phone isn't open source, as far as I can tell. It could be — and if it were, that would be a real step forward. Without it, you're trusting a closed binary the same way you're trusting a closed orb. And even where biometric algorithms are published openly somewhere, that doesn't help on its own. What matters is the binary you're running. Without reproducible builds and published checksums, there's no way to verify the code you can read on GitHub is the code actually executing on your device. "The algorithm is open source" is not the same as "I can verify what's running." Issuance is centralised. Only World ID orbs issue credentials. One organisation gates humanity-as-a-credential globally. For something this load-bearing, that's a very big single point of trust - even if the team holding it has the best intentions today. The proof is device-bound, which makes recovery brittle. Lose your phone, lose your humanity. There's no graceful path back - you have to find another orb and start over. For a system meant to be permanent identity infrastructure, that's a serious failure mode for normal users. And one global ID creates correlation pressure even with zero-knowledge proofs. The fact that two pseudonyms share the same World ID is itself revealing. A single credential presented across services is structurally different from per-context identifiers backed by the same underlying verifications. What I think matters more than any specific scheme is the principles. No single party should gate humanity globally, including any company, including any government, including what I do with @Holochain and @WeAreFlowsta . The user, not the issuer, should control what's revealed to whom. Recovery should be graceful, not "find another orb." And hardware attestation is a useful input, but it shouldn't be the answer. So, where does this point? For me, proof of humanity probably shouldn't be one credential at all. It's a portfolio of signed attestations a person assembles over time from sources they trust. Peers who know them, groups they're part of, third-party verifiers, even hardware attested proofs where those make sense, and present selectively to whoever is asking. No single issuer. No centralised global ID. Recovery happens through your social graph if you lose everything. That shape solves things a single issuer system can't. It also lets schemes like World ID slot in as one valid input among many, rather than positioning any one of them as the answer. "Who is a human?" is one of the most important infrastructure questions of the next decade. It's too important to be answered by any one source.

Amen

@EricDoriean @WeAreFlowsta I am very much enjoying digging in to flowsta. Ive finding out what crashes my conductor the hardest is too many DNAs. My claude reffered to a wasm storm. Turned out my problems were elsewhere but it was a great but exhausting learning experience.

I think this is a great question, and for me, the answer is very personal. I only work with the released versions. (no dev, betas, release candidates). But we need stable for Flowsta as we are live now. If you are building something larger with a longer runway before launch then maybe 0.7.0 makes sense. But for me, always the latest stable version is what I use.

WOW, what a read!! The Holochain ecosystem is going next level. Holochain 0.6.1 is imminent. $hot to HoloFuel is in progress. Plus so much more. Honoured to have @WeAreFlowsta mentioned here too. So much happening. Got another core tech piece to announce very soon too.

@cossssmin Thats bananas 🍌, but cool, with a tiny bit more script you can save as a png :)

Added a <QrCode> component to Maizzle 6 👀

@sankimoski @Holochain @RoetersPro @soushi888 Have you tried making a holochain app? We are the ones we are waiting for.

@Holochain @RoetersPro @soushi888 When #Holofuel

AI coding assistants are moving fast. Whether you're riding the Claude Code wave or shifting over to Codex, you can now vibe-code your Holochain apps. 🤖💻 Huge shoutout to @soushi888 for building the Holochain agent skill. It works with Claude, Codex, and others to get you from an empty folder to a working P2P app. Check out the repo and start building: github.com/Soushi888/holo… #Codex #ClaudeCode #AI #Holochain #RustLang

@Hessu357 What do you think about googles changes? keepandroidopen.org/en/ This might hurt

#Weavernetworks #Kudofuel #Holochain #Holo #Unyt #Web3 #Dweb #RWA Future belongs to the people, we will build it together.

Too predictable, too too predictable.

@cossssmin Define or default sounds great

I think this one's more for the email geeks out there: open/close props for wrapping content passed to the <Outlook> component. Worth it?

@cossssmin I was dipping back into first and last child styling on push stack. If only I could point claude at your twitter page....

Was writing Maizzle 6 docs and just realized: because of how and when Tailwind CSS runs, you can have components like this that normally wouldn't work 🤩

@cossssmin 🧙‍♂️

@cossssmin You finally went ghost table. Now i won't have any defence. 😄

Updated components in Maizzle 6 so you can just use Tailwind for parent widths. Or inline CSS if you prefer. Or a `width` attribute. This makes it super easy to create layouts now, you just style things as you'd expect and it handles everything for you, including Outlook 👍️

@Holochain Some 404s on the project links, but great to check out and read about whats happ ening.

Sam and Anita, the fantastic team at hAppenings, have published a list of updates from around the Holochain ecosystem. Some light springtime reading. Catch up on the latest Holochain community news, events, and releases in the hAppenings newsletter. Grab a coffee and read it here: happeningscommunity.substack.com/p/spring-break… #Holochain #Web3Community #OpenSource