bebop

90 days moving to 45 but you can and should renew earlier than that. Automating this process means that you should be request a new certificates roughly 60 days (or 30 soon) after the issuance of the previous certificate. That way you would have plenty of time to deal with renewal issues. The process for renewal should have back off and retries built in. This prevents a situation where a down time for the issuer means that your production environments are non-functional.

They don’t have the cult of personality to hold on to power in the same way djt does.

This is a very accurate take. There is a ton of collection that the government is explicitly not allowed to do. However, the ability to purchase this data is much less regulated. So the work around is, get contractors to do the data collection and then purchase that data.

We used https://www.coderabbit.ai/ at my work to do reviews and I was a pretty impressed with it. Might be worth a look. Not affiliated in any way.

This is an interesting idea. One thing that might help targeting is to have some sort of chemical that attracts the mosquitoes. In that way you can bring your target to you.

Planes did not exists.

I work for a company that is open source and has a large community. I blows my mind (and often aggravates me) how rude some people can be.

For some reason people feel that it is appropriate to throw barbs in their issue reports. Please to everyone out there, if you find an issue and want to report it (hurray open source!) please be kind with your words. There are real people on the other side of the issue.

Always remember, you catch more flies with honey than vinegar.

A friend of mine who is good at these things recommended https://mantine.dev/

I worry that vision is not going to become reality if the large observability vendors don't want to support the standard.

Own up to it and give a healthy severance as quickly as you can.

That has already begun. Saw stop technology is already working it's way into regulations. A decent non saw stop table saw will cost you ~500 USD. A saw stop saw will be 1200.

To reinforce this point, it is around 375 atmospheres at the titanic. The deep sea is a crazy place.

Super excited to see Airbyte finally make 1.0. Tons of great features in the release that represents a lot of hard work from the Airbyte team over a number of years.

Congratulations Airbyte!

You can still use local users, you just have to work a little harder to do so.

Yes, this is the trade off. If you are working in an industry where you need to be highly sensitive for data access even for short periods of times then oauth/oidc/jwts are probably not for you. If you really need an emergency escape hatch you can always rotate your singing keys and jwks and invalidate all of your tokens and force everyone to sign back in.

I have not seen an authorization server that makes it easy to configure no signing algorithm or even one that might be considered insecure. Most of the client authentication providers I have used (I.e frameworks) have also forced a secure algorithm, usually starting with rsa 256. So while technically you can use a no algorithm signer, I have never seen this happen.

I would add two pros of jwts (I guess oauth 2 and oidc more specifically)

1. It standardizes your auth system. While sessions auth is mostly implemented in the same way across systems, learning oauth and oidc gives you a standard across the industry.

2. Jwts give an easy path to make “front end” applications and api authentication work in the same way. This in theory reduces your security surface area as all of your authnz code can be shared across your offerings.

I have been building this on and off for a number of years. Mostly focused on the document management side of things: https://github.com/bgroff/kala-app

For those that might not follow the link: “[ai code] is presumed to be tainted (i.e. of unclear copyright, not fitting NetBSD's licensing goals) and cannot be committed to NetBSD”.

So more of a provenance issue w.r.t licensing than an ideological one.

Depending on how you game and what games you play, steam + proton works really well on Linux.

Basically. The first part is creating a certificate request for a developer certificate, then apple creates a signing certificate for you. Then each executable part of your distribution needs to be signed with that signing certificate.

The second part is the notarization. This is where you upload a .zip, .pkg, or .dmg to apple and they build a hash of your distribution and serve that to folks through gatekeeper. You can also staple the notarization to the package and then you don’t need to talk to the apple servers.

This way apple can revoke your notarization and users will get warnings about your software being maleware.

Not the parent, but C# and Java are very similar in their feature set. One thing that I find interesting about the respective communities is, Java tends to develop JSR's where a standard is worked on by multiple vendors and published essentially as an interface. Many vendors then provide an implementation of the interface.

In C# Microsoft often provides the most popular tooling for common problems. For instance, in web development, Microsoft publishes ASP.net and Entity Framework. In Java there is Jax-rs (JSR 339) and JPA (JSR 317).

So depending on your preference for a strong centralized environment provided by a single vendor, or a decentralized standards based solution with many vendors, you might lean towards Java or C#.

Not disagreeing with your points. One thing mocks can be good at is to simulate errors that would be difficult to reproduce in an actual stack. For example, maybe you want to try and handle transient network issues or db connection failures, a mock could throw the correct exception easily, making your full stack do this would be challenging.

https://github.com/cartobucket/auth

Cartobucket Auth is an OIDC/OAuth 2.1 system that is meant to be easy to extend and embed into your existing infrastructure. To that end, if you are using Java, you can use the built in auth-data package, you can also use the generated SDK's for the API. Cartobucket Auth is also built to be extended or parts replaced using the Quarkus DI system easily, should you need the system to do something else that is specific to your application.

You can view a system diagram here: https://s.icepanel.io/sCSXIaaJOAsrpe/qAMx

As a padres fan it was fantastic. I could finally legally watch padres games without dealing with blackouts.

I generally agree, I have however always found CORS issues easier to understand in the Firefox DevTools.

That may have been a reference to that fact that many computers of the early 80’s had a basic rom that would be booted into if no operating system was found.

Haiku-os originally used NewOS as the basis for its kernel. NewOS as far as I know has not received updates in many years and is in archive mode.

Thank you for the feedback. Custom connectors are now available in Cloud! We are also actively working on improving all the points you raised, speed and stability in particular. A lot of this work is very much in the guts of the platform and does not often make for particularly flashy blog posts.

One more feature that I think is really interesting is the Connector Builder, which is a no code solution that works for many different API use cases. We at Airbyte hope that this makes it easier for folks to build out the custom connectors they might need.

A point of clarification: angularjs is officially deprecated. Angular is very much still being developed and used for new projects.