I'm perplexed why they would use such a silly example in their demo video (rotating an image of a dog upside down and cropping). Surely they can find more compelling examples of where these skills could be used?
Why are flight bookings the go to example always? For most people, booking a flight happens infrequently, is a non-trivial expense (to your point), and is not that burdensome to do yourself.
I'm a big fan of ActiveJob in Rails. I was considering building a version inspired by it in Node but now it looks like I don't have to. Thank you for building this.
Screenshots on the website would be very helpful. This sounds interesting, but would like to see what the actual UI is before setting anything up. It would also be good to link to the Github repo for the CLI part - I'm skeptical of giving an unknown tool access to my database without understanding what it's actually doing.
We're using Github Copilot (the chat UI on github.com) to allow non-technical colleagues to ask questions of the code, "How does X business process work". It's deflected a lot of basic questions from engineers. Your product seems in this direction. Nice job
Ah yes. This seems to be something new and entirely optional. They’re saying that it might make sense to some to keep both network and application level authorization defined in one place. Personally, I’m with you in just using a normal SSO solution.
It’s at the network level. It will block clients from connecting to the destinations on the network. You don’t need to modify any applications at the destination.
This looks great - congrats. Would I be able to build an internal "Chat with your code" type product? I'm looking at the "code reranker" api docs and they require a list of files including the code itself. This would probably be infeasible to send all our code just to get relevancy. Are there any local ways of reducing the list of files and code we send?
We're using Github Copilot chat (the interface hosted at https://github.com/copilot) for this purpose today but I'm curious how one would build such a thing ourselves.
There is no settlement in Swift itself as it’s not network. Swift is messaging only. Bank settlements would happen later through networks like SEPA or Fedwire.
Ripple provides both messaging and settlement with XRP
Lieferando should spend more time building a good app instead of registering domains. In my experience, they are by far the worst delivery service in Berlin . They’ve also operated long before Uber Eats, Wolt, etc. The only thing they have going for them is some mindshare as the first in the market. I can't understand how they're still around.
I'm not so sure it can be a letterbox. When registering companies with the Handelsregister in Germany, I think there is a legal requirement to have a physical address. At least from my experience.