quintu5

I think if I was going to look into code execution in Tachi Code, it’d probably as part of a transformation into some sort of remote development experience rather than pursue wasm and all its complexities.

That's pretty slick! I've avoided digging into project management and code execution so far in order to keep the scope manageable.

What does the process for adding support for additional wasm-capable languages look like?

It also gives them a hook apply a watermark to the shared image.

But do they still have an arbitrary 4mb max file size on extension assets?

This makes chunking for any sizable extension an absolute nightmare!

True. It just limits the utility of it being built on top of Astro.

This has been my initial experience as well. I was kind of disappointed to find that starlight is meant to be tore entire site instead of part of a larger Astro site, which would be so nice.

Regarding the author’s mention of starlight missing support for mermaid — shouldn’t they be able to just use mermaidjs to render those charts? Why the need for playwright or a plugin?

Banks are always facing a trade-off between security and regulatory accessibility requirements. A former employer offered ~10 different ways to perform step-up authentication for high risk activities to avoid getting slapped with fines.

Indeed.

This is also one of the use-cases I built the Tachi Code browser extension for. It injects a monaco-based editor into the current page when it detects you're viewing a raw file (i.e., the page's rendered body contains nothing other than a <pre> tag).

Tachi Code for Chrome: https://chromewebstore.google.com/detail/tachi-code/acoecgia...

Tachi Code for Firefox: https://addons.mozilla.org/en-US/firefox/addon/tachi-code/

Looks like Google's making some policy changes in response to the Honey drama. The new portion of the policy is item 2 in the updated Affiliate Ads policy.

Here's the full text of the email they sent out to extension developers:

---

Announcement: Strengthening Our Policies on Affiliate Programs in Chrome Extensions

Dear Developer,

As part of our ongoing efforts to improve the extension ecosystem, we are updating our Affiliate Ads Policy to further clarify how affiliate links, codes, and cookies can be used in Chrome extensions.

What’s Changing? The updated policy ensures that affiliate links are only included when they provide a direct and transparent benefit to users. This means that extensions cannot inject affiliate links when no actual value—such as a discount, cashback, or relevant offer—is being provided.

Under this policy, an extension must not add, modify, or replace affiliate links unless:

The affiliate program is clearly disclosed on the Chrome Web Store listing, in the user interface, and before installation. User action is required before any affiliate link, code, or cookie is applied. The affiliate link is tied to a direct benefit for the user at that moment. For example, an extension that finds and applies coupon codes must not insert an affiliate link if no coupon or discount is found. This prevents extensions from monetizing users without delivering a clear value in return.

Why This Matters This update helps maintain a healthy ecosystem by ensuring that affiliate monetization is aligned with user benefit. Users should always be in control of their browsing experience and understand how extensions interact with the websites they visit. By enforcing these requirements, we aim to protect users from deceptive practices while allowing high-quality, value-driven extensions to thrive.

What These Updates Mean for Developers Developers should review their extensions to ensure compliance with the updated policy. If your extension uses affiliate links, make sure they are only applied when they directly benefit users and that all required disclosures are in place.

We encourage developers to update their extensions as soon as possible. Enforcement of the new policy will begin June 10th 2025, and extensions found in violation may be subject to removal from the Chrome Web Store.

For more details on these updates and to access the revised policies, visit our Developer Policy Center.

Let us know your thoughts on these changes, and as always, thank you for being part of the Chrome Web Store community!

- The Google Chrome Web Store team

I’ve got a chrome extension sitting in the review queue right now that leans a bit more dev-centric in that it opens a Monaco-based editor (with markdown preview) whenever it detects you’ve opened a raw text file in the current tab.

It also supports creating new documents, but that’s more of an ancillary use case (for me anyhow).

The nice thing is that it’s 100% local.

You need to specifically go and install the plugin manually right now. If anyone doesn’t want to use it, they can just not install it.

Medium post? - check! Misleading chart with no labels in the header? - check!

Nothing to see here folks.

This is why I never touch new reddit or visit the site on mobile. It's old reddit + ublock origin on desktop and a third-party app on mobile every time.

Less time wasted commuting. More time sleeping. More leisure time.

I still spend the same real number of hours working (if not longer when I'm in the zone) and have a higher quality of life.

That all sounds good to me, so what's the problem?

Agreed. I get a rush from designing a system from the ground up and bringing it to life with all the infra, but only when that's necessary. If it's just a basic CRUD app without any major performance or resiliency requirements, I'm more than happy to do as little of that infra work as is necessary to get it into production and move on with my life.