danfromberlin

I usually just submit www.notlinked.in and it has worked fairly well.

It's safe to say that any human capable of rotating that lego man, even just a single degree within his or her lifetime would cause the outer rim of the input gear to move at orders of magnitude beyond relativistic baseball[0].

[0] https://what-if.xkcd.com/1/

Why does this site with its focus on a video player need to know my browser's location?

This seems sketchy.

I quote from your website: "Don't worry if you don't know what GitHub is, you only need to create an account." You don't appear to make any assumptions that your users understand that their notes will be published and readable by anyone on the internet.

Furthermore, your clarification: "Currently, Kobble stores all user data in secret GitHub Gists, under your account. Secret gists are not private." does not help because it does not explicitly state the fact that notes will be readable by anyone on the internet.

Hi dozzie [edit: typo],

I can entirely sympathize with your comment here, but I'd like to try to quickly present a contrary perspective:

Indeed there are architectural trade-offs made by every monitoring system, and icinga2 makes some that we also have found to be frustrating: one such example that comes to mind for me personally is that icinga aims to maintain backwards compatibility with its historically-derived nagios configuration file syntax which is difficult to understand and hard to parse in an automated fashion.

On the other hand, there are exampls of architectural choices that I believe icinga gets right: It implements an approach to secure and authenticated metrics collection that virtually every other monitoring system leaves as an "exercise" for the user. It provides checks and alerts and notification thershholds by default, which many other monitoring systems don't.

We build monitor in a box to attempt to highlight one particular approach to using icinga 2 which we find works for us. We attempt to be systematic and through in our approach, aiming for a reproducible, Ansible based implementation that emphasizes modularity and code reuse. We invite everyone to try out our open source offering to decide for his or her self whether the benfits of running icinga 2 in this fashion outweigh the drawbacks.

Hi Kristopolous,

In a nutshell, Monitor in a box is a system/application monitoring solution based on Ansible, Icinga 2 and Grafana.

I would like to kindly point you to our demo to see what our software does.

We've also made our code available at github, and I invite you to check out our README to get an idea of how to begin using.

I hope that helps clarify what we're trying to do.

Hi sagichmal,

To be precise, Monitor in a box is a solution built in-part on Icinga 2.

Hi VA4FXP,

I'm sorry about that. We'll see what we can do to address this problem.

The free version doesn't provide any visualizations other than what you see in the icingaweb dashboards. The icinga demo (not grafana) should give you an idea of what I mean: https://solutions.stacktile.io/demo

In the spirit of shameless self-promotion, I invite you to clone our git repo and see for yourself! :-)

Hi zbjornson, regarding your question about "Wondering what the free version uses if it doesn't include graphite for dashboarding": the answer is that free version just includes the icingaweb dashboards and not those implemented with grafana.

Also I'd like to clarify a possible misunderstanding: Monitor in a Box does not require that ansible be installed on all the servers. We only require that ansible be installed on the one machine that orchestrates the setup of Monitor in a Box.

It would be nice to have some discussion of how vcspull compares to mr (http://myrepos.branchable.com/)

Who else feels a sense of horrible dread and frustration that every minutiae of my (and your) online activity is recorded for eternity and exploited to the fullest extent?

What are you going to do about it?

This quote doesn't inspire so much confidence:

“The thing we were terrified about when switching over to PC’s, was learning Windows, but it wasn’t as bad as we thought, especially because we spend the majority of our time in Adobe® Premier Pro and the interface is exactly the same.”

What evidence do you have that IRC is already used more widely than Slack? Also, what's your metric, number of users?

If you care at all about maintaining control over this kind of data, consider abstaining from facebook and running your own service e.g. owncloud or nextcloud.

Hi, Dan from stacktile again, we've prepared a short screencast video for anyone who can't get a free slot but doesn't feel like signing up:

https://vimeo.com/174582090

Hi, Dan here again, some of our visitors will hit our waiting queue today.

If it's any consolation, I can certainly appreciate the frustration some will experience due to this, but we're just bound by the reality of our wallet at the moment. We also mean no harm by inviting those in the queue to provide an email.

Sorry about the choice of wording. What we're trying to communicate is, "You're welcome to leave an email if you'd like to be notified."

we certainly didn't mean it to come off as being arrogant

Hi, point taken: we can explain on the signup page in more detail why we can't accommodate every user.

Thanks for the feedback.

Since the purpose of our product is to give each user his or her own execution environment to freely explore the software that stacktile is helping to demonstrate, we need to give that user access to his or her own container.

Perhaps the confusion is coming from the fact that a stacktile workflow is more than "pre-known" static content -- it is markdown coupled to a an interactive, running shell process in which code can be executed.

I hope that helps clarify

thanks for the kind words

I think the explanation that might be missing here is that every user that hits "Run" gets his or her own linux container in which they will be working.

The process of provisioning a new container (especially under high load that we're seeing today) is what takes a few moments. We however do a fair amount of pre-allocation and other tricks to speed this process up.

Maybe I can also share a bit more insight into what's actually going on behind the scenes. When a user on stacktile creates a workflow, we are also executing a linux container environment on their behalf. This container provides the interactive environment to run the code in the workflow, but it's also a resource (and operational cost) which need to limit at the moment.

Hi, Dan from stacktile here,

I might be misunderstanding your feedback, but I think you're asking why we enable the user to edit markdown in our "try it now" demo -- and thus "interrupt the pitch".

Our rationale with our live demo is to show what the content creation process looks like for our prospective customer. The visitors to a completed workflow won't have the ability to edit the markdown.

again -- I'm sorry about the limited number of users we can support at the moment (and thus the redirect to our signup page).

Thank you for the screenshot.

We allow html to be embedded into one of our workflows, but you can also stick to pure markdown.

I wholeheartedly invite you to create a workflow on stacktile.io that demonstrates how to do it! :-)

Hi, Dan from stacktile.io

we're giving people the option to sign up to be notified when we have a free slot, but you're not required to sign up to try us out. It's just that we have many more people coming to try us than we expected.

Sorry about that!