41–50 of 59 posts
First thing I do when evaluating products: checking their imprint and data policy. I didn't find them. You guys are https://automat.berlin/contact/ , right? A GmbH. For credibility, legal, and fine reasons, get a product-specific imprint and data policy up and available as soon as possible.
google didn't return any hits
Earlier quoted context omitted.
We spent some time to research about licenses. AGPL allows us to keep it open source and also build a business around it as you said.
Is technically open source the best kind of open source? It is open source according to the OSI, but many including myself are interested in open source for specific reasons that the AGPL doesn't satisfy.
If the license doesn't work for your use case, the license seems to have done its job successfully.
First thing I do when evaluating products: checking their imprint and data policy. I didn't find them. You guys are https://automat.berlin/contact/ , right? A GmbH. For credibility, legal, and fine reasons, get a product-specific imprint and data policy up and available as soon as possible.
Would you be able to share what common policies are for software projects or any examples? google didn't return any hits
First thing I do when evaluating products: checking their imprint and data policy. I didn't find them. You guys are https://automat.berlin/contact/ , right? A GmbH. For credibility, legal, and fine reasons, get a product-specific imprint and data policy up and available as soon as possible.
Earlier quoted context omitted.
Thank you so much! We have actually put so much effort into developer experience, especially for building new integrations. You can check examples using oauth authentication: https://automatisch.io/docs/build-integrations/examples If you want to check out all documentation for building integrations, you can use this page: https://automatisch.io/docs/build-integrations/folder-struct... My suggestion would be that you…
Great stuff! FWIW I've been looking for a "some code" platform, that removes the overhead and plumbing requirements for automation, but still allows arbitrary code to run in the automations. Basically, I can code, but there are loads of things about web development I have no interest in or want to think about. What would be amazing to me would be a way in which APIs can be abstracted away and a low code API for vario…
This looks very cool and I'm excited to try it out later today. In the past I've tried Huginn but I have always found Ruby to be particularly unapproachable and the first integration I tried was broken (the weather integration) and despite submitting a PR to fix it, the PR has languished for years. Here's some questions: - How does this differ from Huginn? - How easy is it to install integrations from outside the mai…
Thanks a lot! - It may not differ in the sense of integrations and general functionality. However, the most significant difference is that we aim not only for developers but also general users who may not have programming knowledge. - At the moment, it's only possible if we merge the integration into the source code, but we're thinking about possible ways to have external integrations and also private integrations. -…
Earlier quoted context omitted.
We spent some time to research about licenses. AGPL allows us to keep it open source and also build a business around it as you said.
Is technically open source the best kind of open source? It is open source according to the OSI, but many including myself are interested in open source for specific reasons that the AGPL doesn't satisfy.
Earlier quoted context omitted.
Is technically open source the best kind of open source? It is open source according to the OSI, but many including myself are interested in open source for specific reasons that the AGPL doesn't satisfy.
Isn't the use of AGPL specifically to stop many including yourself's specific reasons? They want to build a business off it, not build your business off it. If the license doesn't work for your use case, the license seems to have done its job successfully.
First thing I do when evaluating products: checking their imprint and data policy. I didn't find them. You guys are https://automat.berlin/contact/ , right? A GmbH. For credibility, legal, and fine reasons, get a product-specific imprint and data policy up and available as soon as possible.
You look for the data policies before looking at the actual product? Why?
The regulatory requirements to build software are extremely low. If someone can’t even comply with the basics, it’s a bad signal.
I currently use n8n, but always great to see more alternatives in this space. One thing that has surprised me is that no one has tried to standardize on the Zapier or IFTTT APIs / SDK implementation to allow for faster deployment of integrations. Seems like there could be a movement here that is akin to how many services use S3 compatible APIs.