snug

I still use Google Workspace for personal and work stuff, but for solo agent workflows, I think I have some use cases that would help me personally. I can let agents spin up working documents that I can review, comment on, and iterate over asynchronously.

For example, I’ve spent the last few weeks building an internal ticketing setup for my agents so they stop trying to fix every tangential issue they encounter. I wrote a skill where subagents bubble out-of-scope issues up to a parent orchestrator, which decides whether to log a ticket.

Currently, that setup mirrors between a local SQLite database and an Obsidian vault: agents write to SQLite, which syncs to Obsidian; when I edit notes in Obsidian, it syncs back. Native Claude docs mean I could ditch the Obsidian middleman for remote review—editing tickets from anywhere while keeping the core SQLite state local to where the agents execute.

Really excited to try the gsuite replacements, which seems like the bigger announcement than the title suggest

All the gauges on the top right except the RPMs move

I'd wager a motorbike is much safer traveling at the same speed

I think this can be great as additional layer of security. Where you can have a non llm layer do some analysis with some static rules and then if something might seem phishy run it through the llm judge so that you don’t have to run every request through it, which would be very expensive.

Edit: actually looks like it has two policy engines embedded

Pretty common to call something that isn't ready a preview

I've generally chosen these tools when I am creating a project. Though I generally use firebase hosting vs other front-end hosting. They have a much more generous free plan.

I'd suggest making some changes to how some of these things are categorized. You have database section with postgres at the top and then with supabase as number 2, but that's also a hosted postgres.

Overall, great job to the creators of this, I enjoyed seeing this analysis

I've also dove into all of those, and have mostly stuck to OpenSCAD now. I'm not amazing at it, but I've been able to get a few things done that I needed for 3D printing. What has really made much better at OpenSCAD is ClaudeCode or Antigravity in VSCode, with BSOL2 library. The documentation is just bad enough that it takes me forever to figure out on my own, but just good enough with lots of examples out there that an LLM can get mostly what I want with little fuss.

When I was in Italy, it took me far too long to realize on Google Maps that all the restaurants I was visiting started with "Il" and not the roman numeral two "II"

I've been able to get this same issue when I am laying in bed and lay on my side where my APP rub against the pillow. I've been able to reliably make the screeching sound by putting one airpod in my hand and tumbling it around or opening and closing my hands.

I still love my APP3, and still have my APP2, but have not made a change back to them. I think they feel so much better in my hear with the new tips, and sound way better.

The paid for feature seems to show the number of dislikes that have the extension installed, however what is shown is the estimated number of dislikes based on the actual number of likes youtube shows, so if the extension users have a like/dislike ratio of 50%, and there youtube shows 1000 likes, the extension estimates that there are also a 1000 users that disliked the video, even though there may only be 1 like and 1 dislike from the extension users, which would be very obvious that the estimate is very off.

You can downvote youtube videos without the extension, the extension just shows how many people downvoted a video since youtube took that visibility away a few years ago. It does help when there are shitty video recommendations and can ignore videos that have a bad ratio

The way the plugin works (in my simplified understanding) is that it guesses how many dislikes there are based on the like/dislike ratio of the people that have the plugin installed. So if 100 people that have the plugin installed and there is a 90/10 like/dislike ratio, and the actual video has 1000 likes, it will say that there are 100 dislikes. Youtube not only took away the dislike UI, but stopped publicly giving the number of dislikes even behind the API.

But even then, the database could not get that big, you'd only need a few simple tables, one that tracks every plugin users like/dislike on the video they stored it on, and then a table that does the aggregations. 15TB sounds crazy.

I'm not a youtuber so idk what content creators could see, but it would have been smarter for them to go after the content creators that have the plugin installed instead of youtube users, not sure why we would care about those kinds of analytics

Update from the dev:

> Unfortunately the extension requires quite a large database (~15TB) - and it costs money.

> The ad\changelog was supposed to show only on browser restart - i.e. be much less intrusive

> The idea behind paid features was also to cover the costs (since donations became smaller than the hosting costs).

> I messed up with implementation though.

> Sorry.

I do feel for the developer, and I am not anti asking for donations, and the full page pop up on browser restart I don't think is terrible, but it would have been better to maybe have a changelog and have a donation button. The ads injected directly into youtube make me lose a lot of trust

Yeah, seems like it just got pushed today, given all the reviews just popped up today too