code_research

unfortunately even vagrant is buggy and very slow and I would like to see a better alternative.

consul and vault are very nice for devops.

Oh, they have a Linux versios, too, did not know that. Then it makes sense to audit this software.

Does anybody have any real life experiences and performance benchmarks for VeraCrypt on Linux?

Also a feature and performance comparison to LUKS would be very interesting!

Linux Magazin authors, please consider... Thanks!

Hey, all you makers of chart libraries!

First a big thank you for your fantastic efforts and for letting the world participate by open sourcing all that stuff!

But one thing: Please make it easy to generate VIDEO OUTPUT with your libraries!

This is an artificial limitation that I hit with many charting libraries - output generation is html (js) only and people who would like to create moving images have unnecessary problems shoehorning that nice chart library into outputting to a high resolution video.

Please do not limit your designs to one output medium.

Think video, too, THANKS!

really great, thank you very much for open sourcing, can't wait to dig into this!

Is the machine learning goodness included in this? Also a 'vagrant up' would be very nice... Thanks, anyway!

what events? It would be great if he spoke openly, so people not following tor very intensively would know what is so concerning. Yes, I am living under a rock.

would you like to describe the problems you had with the existing solutions?

In the config.rc file you could call that folder however you want.

I personally do not like ".meta", because it is not clear what kind of information it may contain. "Meta" might be anything, documentation, description, website, design papers, everything is meta. It is a bit like using "Information" as a menu entry for a website.

beefsack is right, please do NOT make it a github specific thing. Just one config folder. All config files for services, integration, etc. should go there.

Thanks again!

This is a very interesting service, thank you!

May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root".

I would like to suggest to call that folder simply "config" - all the projects and tools out there should have no problem with that. Optionally there could be one top level config file called "config.rc" - this file points to the actual config dir if it is not "config".

It would be verrry nice if one service just starts with that and hopefully all the others will follow and it will become a defacto standard. The pollution of the top level project directories really must stop.

Thank you!

can I sync this with data in a postgresql db?

> but there is a reason no one wants to do that these days

The reason is, that JS is enabled by default, nothing else.

If users had the possibility to actively decide before any remote code will execute on their computer, how many would like to enable it?

We are just one default checkbox setting away from what you call "utopia" here - a word that should be used for much bigger things.

Of utopic naivity in deed is the expectation that such powerful features will not be misused - delivering browsers with code execution enabled by default will be looked at as one of the most funny things of the first internet in a few decades.

Web application development paradigms that enforce JavaScript usage as an absolute necessity are examples of "naive utopian deadends". It is totally anti-avantgarde and anti-progressive, we should not waste so many young talents on that.

"remote-execution-by-default": web browsers execute code that was loaded from an untrusted source somewhere on the internet. Every (ok, most) browsers by default allow any website you visit to execute JavaScript code in your browser.

"same origin" is about the source of that code, only of minor relevance here as long as no working signed code distribution mechanism and infrastructure exists - why not, btw, after all these years?

For communications and general information transmission we do not need remote code execution.

Yes, browsers try to do that in a "safe way" - the "sandboxing" approach has been exercised for many years now, mostly without success. Maybe Qubes OS can be a successful approach to this problem, but we still have too many non-technical problems to solve, as reality shows, so enough time to do more research. Until then: css only should be the default.

CSS gives us a very good way to stop going on with that inacceptable defaults while we fix the first version of the internet.