Wilya

They don't really work at the same scale.

Kimchi is for managing a single host. Ovirt is aimed at managing datacenters, so it handles things like network, clusters, etc.

I know at least one large ISP that does exactly that, so I guess there's not much preventing everyone from doing it.

Apple considers that all sales across Europe actually happen in Ireland, so taxes on profit on sales in the whole EU are paid in Ireland. That part is perfectly legal within the EU.

The issue is that the normal tax rate in Ireland is around 12%, and Apple uses accounting tricks and tax exceptions to lower their effective tax rate there to 0.005%. That is the part that the the European Commission ruled illegal.

It's pretty easy (at least on Linux) to firewall all inbound/outbound traffic on your physical network interfaces, allowing only the bare minimum necessary to connect to the VPN server (DHCP to get a local ip + an udp/tcp connection to a single ip:port).

Last I checked, it was a bit more difficult to do on Windows, because it didn't allow interface-specific rules, and because software installers had a habit of opening holes for themselves in the firewall without asking you.

The article has the name of one particular website repeated fourteen times, and it paints its marginal niche (sugar daddies) as something that everybody is doing, and as something normal and empowering for women. And, coincidentally, this website needs to attract women.

Everything about this screams "Bullshit marketing/PR piece". Is it only me?

I think you are overestimating how functional real world bluetooth is...

Even without going into performance concerns, it's just harder to understand than the <= form.

Example in this thread: half of the commenters consider that it means 1 <= len(vals) <= 5 and the other half consider that it means 1 <= len(vals) < 5...

The dashboard is gorgeous, one of the prettiest I've ever seen.

But I wish it were a Riemann/Graphite/whatever dashboard instead of reimplementing its own data collection system.

There is a need for great dashboards, but I don't feel any need for yet another format of data collection plugins.

The recommended ASGI server seems to be Daphne[0]. Nginx doesn't need to speak ASGI natively (as it doesn't speak WSGI natively), more likely Daphne would replace the WSGI server (gunicorn, etc) running behind nginx.

[0] https://github.com/andrewgodwin/daphne/

Have you used both jails and Docker? Saying docker is a much more polished option doesn't match my experience. Yes, it has more features, but with these features come more bugs. Some of them are minor annoyances. Some are of the "our infrastructure is fucked until we switch our storage driver" kind.

Sometimes, stability is a gain.

People are talking about the cost of Heroku, but it doesn't seem that outrageous to me.

I mean, $180/month for a running app, that is making money, isn't that much. Once the traffic grows, and you're spending $500 or $1000 per month, yes, it becomes worth it to look into alternatives (because $1000 on Heroku can probably be replaced by $150-200 on more powerful hardware). But moving from Heroku to a less managed option just to save $80/month doesn't seem particularly worth it.

Unless it has changed recently, it's opt-out. The instructions are mostly for re-adding the key if you have removed it.

> As opposed to plain text files, which magically survive having random blocks overwritten by hypothetical filesystem bugs or hardware issues without losing a single line of log content?

Neither system will protect you from losing a single line of log. The problem with journald is that a simple corruption can make you lose the entire log file.

We use it to run a bunch of periodic report-building tasks. Compute internal metrics, archive support tickets, that sort of things. Compared to plain cron, we get proper tracking and history of the runs that failed, and a web UI to access the results (generated reports, for us).

I wouldn't use it for production-sensitive crons, but for administrative stuff, it works fine.

Scaling storage? The highest public plan Github allows 125 repositories. Unless you have a lot of huge repositories, 125 repositories fit into a single smallish hard drive. Even with 10x redundancy, that's still cheaper than github.

Frankly, there are hard problems in internal IT, but hosting a bunch of git repositories is a non-issue.

That's not how it works on a decent VPN system.

If you try to do that, the VPN client will notice that the spoofed server isn't presenting a valid certificate or doesn't use a valid key, and refuse to connect. Same reason you can't "just" middleman an HTTPS connection.

Besides, there's no need to spoof. The point of the VPN connection is to protect against the wifi router (even the legitimate one!) reading the traffic. By spoofing, you're just replacing a dodgy wifi router with another dodgy router.

Reading the bugs and threads linked, the biggest issue seems to be that some people from the debian installer team decided to write their own live cd and declared that Debian Live was obsolete, without ever speaking to the people from Debian Live.

So, it is probable that a live-cd will still exist, but it won't be the one called "Debian Live".

Last spring, France passed a quite intrusive bill that pretty much legalized mass-interception of communications. The general public didn't really care much.

In theory, the point of Google Fonts is that it does user-agent sniffing to adapt the font and css to the user's browser, to get the best rendering. You would lose that advantage by hosting the fonts yourself.

Everything related to Glacier is ridiculously complicated.

The pricing is tricky (the per-GB price is cheap, but the retrieval can get horribly expensive). There's the fixed 4-hour delay for all actions (including listing stored files), which makes any interaction a pain. And there aren't really any good clients or high-level libraries that abstract away this complexity.

For a disaster recovery, I would certainly go for something simpler and easier to use. When everything is one fire, the last thing I need is dealing with a tricky API to restore the company files.

Compared to VPS, you give up some flexibility (bare metal servers are generally only available for a month), but, at equivalent price, the specs are better on bare metal servers.

Colo can be even cheaper, but it needs additional skills, and more upfront money investment. It's a whole different world.

A whois on the domain serving the offending javascript leads to White Ops[0], who seems to sell tools to protect against Ad Fraud. So I'm guessing this is part of their fingerprinting system, to determine whether I am a human or a bot.

[0] http://www.whiteops.com/

In most cases, this shouldn't pose any issues (though some games doing crazy things with networking could be affected).

These rules restrict the ports listening directly on the internet. The average gaming PC is behind a home router, has no ports reachable from the internet, and network games still work fine.

If your college was like mine, what they did was filtering outbound connections, which is different. Outbound traffic is unfiltered by default on EC2, and it's fine to leave it that way.

The guide advocates an EC2 security group that allows everything, plus disabling the Windows firewall. That's quite insecure, and unnecessary.

It's probably better, and not more work, to create a security group that only allows:

* UDP on port 1194 (Openvpn server) * TCP on port 3389 (Remote Desktop) * ICMP (for ping)

Oh, come on.

If your business model is "bypass the law and hope you can get big enough before anyone notices", this kind of setbacks are bound to happen. It happened in France, it could have happened anywhere.

On the other hand, there are thousands of people creating startups without trying to hack the law, and they are doing just fine in France.

Unless you have all the details and you have compared the price of both options, you don't know that it's cheaper.

That seems unlikely to me, for an entity of the size of UT Austin. They probably have enough jobs to run to keep their clusters busy.

Is anyone running Marathon in production? Real production. The kind where any downtime means lost money.

I see a lot of intro-level tutorials, but almost nothing on the more advanced side.

My (completely casual) experience with Marathon is pretty bad, with the main process crashing quite regularly even under no load, so I'm wondering if people who write about these systems have actually used them for non-trivial tasks. And for something as critical as Marathon, which is supposed to handle... well... all my services, I'd rather be sure that the system is rock solid.

(This is specifically about Marathon. Mesos itself has proven more reliable)

He could, except this quote predates Bitcoin by at least five years. Oldest reference for this page in the wayback machine is in 2003. The quote may be even older than that.

A classic filesystem associate each path with a content.

A content-addressable filesystem associate each path to the hash of its content, and then keeps a separate mapping of each hash to a content. Which means that if two files are identical (= have the same hash), then the content is only stored once.

A union filesystem is a filesystem that is organised as a set of "layers". You have a normal filesystem at the bottom, above it you have a set of layers, where each layer only stores the files that have changed (each time you create a snapshot, the filesystem creates a new layer).

In practical terms, you have a filesystem where taking snapshots and reverting to older snapshots is very efficient.

Or, in other words, a filesystem that behaves like a git repository.

It's pretty common for 3D/rendering companies to use company desktops at night or when they are idle for rendering, and most renderfarm managers support this kind of setup. However, this is only worth it because the graphists already have powerful workstations to do their job. I doubt using underpowered laptops would make sense.