bullcitydev

It had to be done: https://glizzy.cam/

Caffeinate stays on until you stop it.

Vigil subscribes to agent harness hooks to know when the agents are working, when they are waiting, when they are done. It keeps your mac from sleeping until all agents are done or blocked waiting.

Vigil shows you summaries of what all agents are doing, even subagents. Click on the summary in the top bar, get taken to the terminal where that agent is working.

"RSS just needed people to reject the big-company hype" is why Im building my own reader. RSS was never the problem; it's the stuff around it: feeds truncated to a teaser, blogs dying and taking their archives with them, cloud readers logging everything you open.

I'm building Cove (https://covereader.app), a native Mac app that works as a permanent local archive. Excerpt-only feeds get the full article fetched and extracted on-device in an offline WebView, stored LZFSE-compressed. It can also read articles aloud with streaming TTS that runs entirely locally, so nothing that you read leaves the machine. No account, no servers.

Caveats: Mac-only, no sync yet, will be one-time purchase at 1.0 (beta is free now).

Speaking as an open-source feature flag 'vendor' (https://github.com/flipt-io/flipt), the OpenFeature organization has been a joy to work with. They are very welcoming of new contributors (e.g., implementing a provider SDK in a new language).

If you're interested in this space I'd recommend lurking in their CNCF Slack Channel https://cloud-native.slack.com/archives/C0344AANLA1 or joining the bi-weekly community calls https://community.cncf.io/openfeature/.

Thank you!! Very much appreciated

Thats a cool idea! Feel free to put something in our community on Discourse (https://community.flipt.io/c/flipt-cloud/6) or Discord (https://www.flipt.io/discord) so we can talk through how this could work.

We've been thinking a lot recently about supporting 'edge' k/v stores like vercel/cloudflare and having the client side evaluation SDKs pull from there, which wouldn't require a server at all. This seems very similar just with using GitHub. We could even use GitHub Container Registry as the store as its OCI compliant.

Thank you for using Flipt btw!!

Thats great to hear! Would love to learn more about your usecase or what else you'd like it to do.

Feel free to send me an email at mark <at> flipt.io, or drop into our Discord to say hi at https://flipt.io/discord

Hey! thanks for the reply. We are loving Kite, great product!

Will send over the project file now, very much appreciated!

Approvals are coming next btw. With the ability to lock down envs like production and optionally require all state changes to go through a proposal/approval process

I tried to answer your first question below, hope I did!

Re: GitHub outage, each org gets their own instance in our cluster and maintains a checkout of the git state, so you can still write/read from your environments, they just wont be synched to GitHub until they recover.

We're also thinking about adding other 'sinks' like S3/object stores and OCI as backup sinks.

This! 100% All the same benefits of config as code, infra as code. And with feature flags if something goes wrong its a simple `git revert` to get back into the previous state.

Another benefit is you can easily replicate the current (or previous) state of production/staging/etc flags locally just by doing a `git clone` and then run our self-hosted version locally. Its a single binary, can be installed with curl or homebrew and can read the flag state from your local filesytem.

This allows you to test your code locally or in CI with the same state in production

Yeah the context only supports a map/JSON object of k/v string values for evaluation at the moment.

We could definitely look into supporting other types and making this simpler. The constraints that are matched can be of several types, which we try to parse at evaluation time https://docs.flipt.io/concepts#constraint-types.

Also thank you for the feedback about not being able to change the organization name. Currently we use the 'slug' of the organization (based on the name) when we setup the routes for your environment, so it was just simpler to make it a one time thing.

But I think we could support renaming your org, it would just make the previous URLs invalid, or we could maybe handle redirects on our end too.

One thing to note is that we currently only support GitHub organization accounts.

We're working on personal accounts next, but due to GitHub API/apps permissions, we have to request a different set of creds to get that to work.

The voice volume seems to get quieter in certain spots, even when its set at a constant level.. I'll reach out to the Kite team

yeah sorry, I will fix that! It was bothering me too. I put the music to the lowest setting.. I used https://kite.video/

We at https://flipt.io are putting on a buy vs build webinar in a couple of weeks to discuss this very thing as it's a common question that engineering teams seem to have.

If you're interested in attending its taking place on LinkedIn on April 17: https://www.linkedin.com/events/buildvs-buy-pickingafeaturef...

We're currently evaluating OPA for adding RBAC to our open-source application [0]. We plan on using the Go API [1] and doing the policy eval directly in our app since our app is also written in Go.

The thinking is we'll have some basic built-in policies (like admins can do X, editors can do Y, etc) but also allow users to configure their own policies if they want by writing rego and loading their policy rules at startup time (via config). We'd document the inputs that we pass to the evaluation call such as request headers, IP, role, etc.

I'm curious if anyone has ever tried something like this or similar?

[0] https://github.com/flipt-io/flipt

[1] https://www.openpolicyagent.org/docs/latest/integration/#int...

Hey thanks for giving Flipt a look! I'm the creator of Flipt so would love to chat more about your needs to see how we could make it work for your use case! We're actively looking into providing local caching for all our SDKs btw and would love to learn more about what your requirements are for remote configuration as it's also on our radar! Feel free to send me an email at: mark (at) flipt.io.

haha for sure. but still better than code generation IMO ;)

Just fixed it. Thanks again!

thanks! I'll check it out!

Author here. I just removed the previous section I had around using build tags because I realized I was using `// +build 1.18` instead of the correct `// +build go1.18`. Oops.

Interesting.. I've never heard of licensezero. Will check it out this weekend. Thanks for the tip!

Thank you!

That is a very good question and something I have been struggling with. Do you have any ideas?

I know that it has been done (ex: Sidekiq has OSS, Pro and Enterprise versions).

My thought was to maintain a private fork for the pro version and continuously merge in changes from the OSS version, as well as add back any features into the OSS version that could be beneficial to everyone from the pro version.

But this does sound messy.. would love to know how others have done this in the past.

Thanks! I have heard the feedback from others as well. I think that will be the next thing I do with Flipt, as well as support more traditional RDBMS'.

May I ask what specifically you found frustration with LaunchDarkly?

Thank you! Yeah I rebased my git commits to clean things up and get rid of some silly mistakes.. although now I kind of wish I hadn't so the commit history told the full story.

I agree I need some better examples/documentation on how to do A/B/n segmentation. Will work on that ASAP.

Thanks again for the feedback!

Thanks! Glad you liked it. I think I may do that this week!

Not to hijack the OPs post, Fire CI looks like a great tool! I recently released my open source feature toggle project, Flipt (https://github.com/markphelps/flipt), that allows you to implement feature flags in your existing environment.

Would love for you to check it out and give any feedback that you can!

Just wanted to say that I really enjoyed your presentation. Definitely inspired me to think hard about what I actually like doing instead of just trying to build something that I think I can sell for a few bucks.

I've created multiple web apps/plugins that I wasn't really passionate about, and after the initial rush of launching something wore off my interest in the project waned. I found that when a new bug or feature request popped up, I became less and less motivated to actually fix the issue or implement that new feature.