u/sockstream

Really cool! Safari is the odd one out that doesn't do ogg vorbis unfortunately. I wonder if that's the only thing stopping it from working there.

Glad you mentioned this! It’s rather gory, but has good story and amazing buildup and acting. I do think the ending was a bit cliche, though.

Did you finish Discovery? I thought the first half was okayish, but it REALLY picks up the second half of the season. Actually enjoyed it a lot!

• Sort the Court
• The Reigns series

Needs more... MPEG?

It's almost like the camera couldn't keep up with the water splashing.

I released a crate to simulate a RISC-V CPU: https://github.com/stephank/rvsim

This has been spare time project of several months. I want to try and build little simulations of fictional machines with it. Kinda like Pico8 or ye olde RoboWar.

Surprised that works! I was trying to run a node on a Pi3, (having no experience). Importing the recent torrent, it was at .75GB RAM (out of the 1GB on the Pi) with only 30% of the import complete. So I was expecting to need at least 4GB of RAM.

Small bummer. Guess I have to find some other purpose for it. :)

Check! Ik had dus totaal geen idee dat dat zo'n eiland is. :D

Stromae?

Oh, I imagine cryptography is a fun field in maths on its own, but webdevs don’t do that. We just see boxes that need to be glued together. And we patch holes. We have, like, a checklist of holes to patch in every project. We also get it wrong all the time. Ah, such is life. ;-)

The other responses are mostly correct, but actually assume webserver features that are entirely optional.

The path (and query string) of a URL is what's sent to a webserver. The webserver can then respond however it wants. There's nothing in the HTTP protocol that says you can browse the server like a filesystem.

Most popular webservers like Apache and nginx allow you to specify a directory index, a file to look for when a directory is requested like index.html, and can also optionally generate a directory listing if that file is not found.

Especially the latter is what allows browsing and snooping around. You typically disable that for public facing stuff.

Lots of sensitive stuff is hidden all around the web behind public, but secret URLs, that are pretty much impossible to guess. This is a fairly common technique, usually combined with a hash or random part.

I imagine they may have chosen to do things this way to reuse (and dogfood) the existing update mechanism, where internal builds are just different release channels.

Braavos, King's Landing and Mereen are fictional. The others are places you should absolutely visit, even if you're not a fan. Coming from someone who's in Dubrovnik right now, and having visited the others last week.

Oh, and also: binge GoT.

And Mereen is in the Klis Fortress near Split.

Gaat dit niet alleen om diensten in America, of daar gehost? Dat zijn er uiteraard wel heul heul veel.

Mijn insteek is altijd een beetje geweest: data die door Nederlandse exchanges en diensten gaat moet veilig en privé zijn, omdat wij juist altijd zo'n groot knooppunt zijn geweest. Dat is onze sterkte.

I'll be that guy and say: relying on a monospace font to align stuff in your code is evil, and programming in a proportional font is actually super comfy.

Als de politie de voornaam van de bestuurder bekend had gemaakt „dan gelooft helemaal niemand meer dat het géén aanslag was”, aldus GeenStijl, ...

Fucking WAT?

Ik weet dat links en rechts dit soort dingen als slechte grap gezegd worden, maar wat ben je voor achterlijke kloothommel als je dit in een artikel zet?

Gebruikersnaam klopt helemaal :p

Voor de luiaards, 'met twee woorden spreken' gaat over 'ja, meneer', e.d. https://nl.wikipedia.org/wiki/Beleefdheid

Ik zou mezelf niet onder de jonkies tellen, en zelfs ik moest even spieken. Verder wel een 'oh ja' momentje, want het is mij zeker geleerd.

Omg, I'm just subbed here, didn't know this was a thing! I'll have to investigate. 😮

But but but... Hyper 0.11? 😇

I guess you have a bunch of stuff that uses TCP-proxying in haproxy, rather than HTTP?

For a lot of our apps, I do feel more comfortable with a proven proxy in between. In production, I usually just have to expose nginx, which then proxies vhosts to containers. Nginx also does TLS and caching, which I've found is a lot easier and more performant than doing it in our apps.

But it absolutely depends on the setup.

I worry the IPv6 options Docker itself currently provides are not very well thought out, are not mature enough, and not enough people are trying it out in practice. Not sure if Rancher can bypass things, or needs to work with Docker on this, but it's probably some ways off, given the current interest.

It's useful in a small number of areas, for example when you're trying to make available services on an office or home network.

For hosting public stuff, it seems easy for a cloud provider to just assign you a v4 address, from the outside, but I'm not sure if and how they're feeling pressure. There's the recent news of Google buying a /12, for example. I also host some stuff at Scaleway, and they charge €1/month per v4 address, while v6 connectivity is free.

Convention in the cloud is also that your hosts get the public v6 directly assigned, while your v4 is some private address through DHCP, and the provider does NAT on your public address. I've found this has complicated our provisioning tools in a number of places.

I also feel like NAT in general is a bit of a hassle to set up. You follow a set bunch of rules, but there's often some warts. Especially combined with a DHCP address, something I ran into in the article as well.

Internationally, phonenumbers may be hard to distinguish from any other series of digits.