dominis

Sorry, English is my second language. When I wrote "won't work", probably what I meant was: won't scale.

I am certain we are going to end up using these tools like we do with CI in the near future. With this, you'll get full observability, RBAC, sandboxing, and reproducible benchmarking.

I assume as an enterprise you will want all of these when you spend a big chunk of your budget on tokens.

If you think about the evolution of AI coding, companies (who will eventually pay for these tools) will realize they want to run the coding tasks in a remote, controlled environment. Every engineer typing on their machine and burning tokens (money) won't work in an enterprise setting.

I wouldn’t be surprised if in most cases it’s $100 in $1 out.

on individual level for basic things I found hooks pretty good, you can block tool executions easily.

I think here the question will be how to scale rules on team level.

Obviously sandboxing will be needed if we want proper gates.

I had the same problem, browser extensions weren't enough, and I wanted something system-wide. So I built Sinkzone [1], a DNS tool that blocks everything unless allowlisted. It’s open-source and works across OSs. Thought it might be helpful if you're looking beyond NextDNS.

[1] https://github.com/berbyte/sinkzone

Thank you for the idea, I've created an issue: https://github.com/berbyte/sinkzone/issues/1

<3

I'm not familiar with this project, just checked their GitHub Readme and if I understand correctly they block what you want them to block. Sinkzone does the opposite, it allows what you want to allow, and blocks everything else.

I'm planning to address the issue for phones as well in the future.

I've used https://github.com/StevenBlack/hosts myself for a few years, I think this is a fantastic collection for hosts based blocking.

You can configure your upstream resolvers in the config, so I think Sinkzone can be placed in front of your VPN's resolver. I never tested this to be honest.

It's on my list :)

Hey Eszpee, Thanks for checking Sinkzone out. I'm thinking about building custom schedules in the next iteration, that would support some basic pomodoro style scheduling for sure.

I wanted to build my tool because eventually I want to support multi-tenancy. Custom allowlists and schedules for all family members.

This is not "Technical deep dive"

test

test

- test

- test

- test

https://google.com

  test code
  test code

Cloud Infrastructure Autopilot.

https://ber.sh

Were there any salespeople on the team?

Hungary already solved this, it's harder to cheat in a bath in swimsuit: https://www.awl-images.com/cache/pcache2/00042940.jpg

Let's reverse this notion: if your company is a remote(-friendly) company the place your employees are living is their decision. Since your company allows them to work wherever they want, they don't necessarily have to live in the Bay Area. This becomes a personal preference and I don't see why a personal preference is your business, moreover why you need to reward it with extra money.

Also it's worth considering that in this business your employees are hired to think. It is nice companies starting to realize that it's not needed to be present 100% in the time in an office to be able to deliver the thinking, but they also need to realize that my brain produces the same output no matter where I live.

use the api (which is also not perfect)

you don't need the `-X POST`, because `-d` will do a post by default :)

http://cl.ly/2h2K2B3M2p0H2i1z2O2c http://cl.ly/3z28333n3w230e2S1U0Z http://cl.ly/2T232H1r2M3g2w0g1G0N http://cl.ly/140F2R1U291J3v2m1y0Z

Kudos, I've started the same project a few months ago, but I had no time to finish. The only question is what are you going to do if amazon integrates the bounce handling into the ses api?

BTW, is there any Hungarian folks here?

dns.he.net