Hacker Newsnew | past | comments | ask | show | jobs | submit | vince14's commentslogin

Isn't the jitterBufferTarget [0] the latency vs. quality knob?

[0] https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpRecei...


Close, but that's a minimum latency. We want a maximum latency knob.


That is not the case. There are LCOLC, LFSCOE and others which land on renewables being way more expensive. Even without your made up claim about "assuming cheap and fast to build nuclear power".


Which are extremely simplified metrics.

Like the LFSCOE study is only using one source of renewables through all weather together with 2020 data on battery costs.

Which is why I linked a recent full system analysis. With Danish data so a vastly harder problem than a place with abundant solar. So tell me what they missed.

They even tilted the study heavily towards nuclear power and assumed that the nuclear costs are 40% lower than Flamanville 3 and 70% lower than Hinkley Point C while modeling solar as 20% more expensive.

Still finding that renewables are vastly cheaper when it comes to meeting a real grid load.


you should be very careful with 'papers' written by people that stayed at the core of Danish antinuclear movement like Henrik Lund (famous “for me, nuclear power is not a dream. It’s a nightmare. My dream is renewable energy”, but there are more interesting turns there, including EnergyPLAN which was criticized a lot for it's nonsense assumptions which I can bet is used here too. It was so severe that the issue was addressed in a peer reviewed publication https://www.sciencedirect.com/science/article/pii/S030626192... ) and a paper that includes frauds like jacobson in citations. These two are famous for citation rings and both are public antinuclear activists.

I can bet they have very "optimistic" estimations for Hydrogen and gas firming on top of the most evident issues adressed in peer review


I do notice that you are talking about past papers rather than this current one.

You also link another of the typical studies desperately trying to shove new built nuclear power into contention.

It looks like this: ”If we assume nuclear power is cheap and fast to build”.

Do the same for renewables and storage and the comparison becomes even more lopsided.


I talked about current one too.

I've linked not a "typical studie" but a peer reviewed correction to the mistakes of the original paper.

Ironically we already know the answer about speed. Check out how TWh/y of clean power evolved in Denmark vs UAE with Barakah built by Korea


In which the peer review presents numbers that’s a fraction of all modern western nuclear power while not giving renewables the same benefit.

> Check out how TWh/y of clean power evolved in Denmark vs UAE with Barakah built by Korea

This tells me you are entirely out of your depth.

You do realize that what we care about are cumulative emissions? You also have to compare it by grid size.

The shining beacon in UAE you lift have a horrendous gCO2/kWh of 468 while Denmark sits at 114. Starting at 650.

Calling that what UAE achieved a success means you don’t care about decarbonization, only trillions in handouts to your pet technology.


You can inspect how that paper was peer reviewed by pointing out what was wrong with it) To me it's wild how people are defending nonsense written by frauds like Lund and Jacobson, both heavy antinuclear proponents that treat hydrogen as some dirt cheap power firming option

The discussion was about speed anyway. UAE achieved higher TWh of clean power than both Denmark and Portugal in less time, as simple as that - this is undeniable

The statement about "handouts of trillions to pet technology" shows you just don't care about emissions, you hate nuclear. Per IPEX nuclear gets 15x less subsidies vs renewables in EU. Germany spent on EEG alone double the cost of entire french nuclear fleet, the gap getting wider. From this year transmission will be subsidized too because DE households have highest prices in EU, close to Denmark. But i guess subsidies for your favorite technology are fine and for the rest it's absolute evil.

Saying that UAE didn't achieve success with it's Barakah is either delusion or willingness to ignore reality.


You do realize that you went completely off the rails here?

I still haven't seen you levy a single factual criticism to the methodology in the paper I linked. It is just you lashing out.

Again you don't care about cumulative emissions, or the grid size.

https://imgur.com/a/09DMS72

And this is the graphs if you assume that renewables never become perfect:

https://imgur.com/a/WrLUrwK

You do realize based on these graphs that every investment in nuclear power just leads to more emissions?

Now lets talk about your TWh per year figure, comparing apples to oranges. UAEs grid is 184 TWh. Why didnt UAE do like Germany and deployed 196 TWh renewabels in that time and completely decarbonize their grid?

Are you realize how absolutely stupid you sound trying to compare TWh per year figures without referencing the grid size?


Storage is not just 'a problem', it doesn't exist and won't for many many decades.

The planned solution is hydrogen power plants, but no one wants to build them because the infrastructure, including electrolysers, is way too economically unfeasible.

Therefore, Germany is and will continue to be dependent on coal and gas, as these are the main producers every night. That's your 'grid backup fee' for you.


Long term storage is a problem. Nightly will be solved soon by batteries. California is well on the way, down to 25% fossil in 2025 from 45% in 2022, due to batteries. And they just keep getting built. Australia is on the same track.

If we have to burn some gas to cover the occasional long term weather issue, I’m ok with that , if we’re at 90+% decarbonized at that point it’s still a huge win.


Their fetch call is missing `keepalive: true`.

    When set to true, the browser will not abort the associated request if the page that initiated it is unloaded before the request is complete. This enables a fetch() request to send analytics at the end of a session even if the user navigates away from or closes the page.
https://developer.mozilla.org/en-US/docs/Web/API/RequestInit...


Because projects like these were missing back then, I got creative with nginx and do not need any config changes to serve new projects:

  server {
    listen 80;
    server_name ~^(?<sub>\w+)(\.|-)(?<port>\d+).*; # projectx-20201-127-0-0-1.nip.io
    root sites/$sub/public_html;
    try_files $uri @backend;
    location @backend {
      proxy_pass http://127.0.0.1:$port;
      access_log logs/$sub.access;
    }
  }
Configuration is done via the domain name like projectx-20205-127-0-0-1.nip.io which specifies the directory and port.

All you need to do is create a junction (mklink /J domain folder_path). This maps the domain to a folder.


Am I reading this wrong or does this almost open up any server bound to localhost to the outside?

I think proxy_pass will forward traffic even when the root and try_files directives fail because the junction/symlink don't exist? And "listen 80" binds on all interfaces doesn't it, not just on localhost?

Is this clever? Sure. But this is also the thing you forget about in 6 months and then when you install any app that has a localhost web management interface (like syncthing) you've accidentally exposed your entire computer including your ssh keys to the internet.


Nothing is preventing you to add an IP whitelist and/or basic auth to same configuration. That is what I do to all my nginx configurations to be extra careful, so nothing slips by accident.


Will just any request even pass the host matching?


I got something similar running with nginx myself with purpose of getting access to my internal services from outside. The main idea here is that internal services are not on same machine this nginx is running on, so it will pass around to needed server in internal network. It goes like this:

  server_name ~^(?<service>(?:lubelogger|wiki|kibana|zabbix|mail|grafana|git|books|zm))\.domain\.example$;
  location / {
        resolver 127.0.0.1;
        include proxy.conf;
        proxy_set_header Authorization "";
        proxy_set_header Host $service.internal;
        proxy_set_header Origin http://$service.internal;
        proxy_redirect http://$proxy_host/ /;
        proxy_pass http://$service.internal;
  }
Basically any regex matched subdomain is extracted and resolved as $service.internal and proxy passed to it. For this to work, of course any new service has to be registered in internal DNS. Adding whitelisted IPs and basic auth is also a good idea ( which I have, just removed from example ).


That's why I switched to Caddy for most of my needs. I create one Caddy server template, and then instantiate it as a new host with one line per server.


I'm having the same issue.

https://securitytrails.com/ also had my "secret" staging subdomain.

I made a catch-all certificate, so the subdomain didn't show up in CT logs.

It's still a secret to me how my subdomain ended up in their database.


They could be purchasing DNS query logs from ISPs.


Serious question: Do you really think that Cloudflare is trying to keep these kinds of thing private? If so, I'd suggest that's not a reasonable expectation.


Related question (not rhetorical). If you do DNS for subdomains yourself (and just use Cloudflare to point dns.example.com at your box) will the subdomain queries leak and show up in aggregate datasets? What I'm asking is if query recursion is always handled locally or if any of the reasonably common software stacks resolve it remotely.


If you just use Cloudflare as a registrar, then they can't see what resolution happens on your servers.

If you delegate a subdomain through Cloudflare to your own DNS servers, from what I remember from the animal book, the recursive server should ask Cloudflare for the address of the machine to which the delegation has been made (yours), and while any further resolutions would be answered by your machine, Cloudflare would at very least know of every query to that subdomain.

If you delegate a subdomain and have subdomains under that subdomain, then Cloudflare would only see resolutions to that subdomain and not to the sub-subdomains.

In other words, for most things, they'd have full insight.


As well as assuming Cloudflare sells DNS lists, it's probably safe to assume the operators of public resolvers like 8.8.8.8, 9.9.9.9 and 1.1.1.1 (that is Google, Quad9 and Cloudflare again) are looking at their logs and either selling them or using them internally.


maybe your server responded to a plain ip addressed request with the real name...


Host header is a request header, not a response one, isn't it?


He said he used a wildcard cert though. So what part of the response would contain the subdomain in that case?


Fire-and-forget?


https://gdpr-info.eu/recitals/no-49/

> Network and Information Security as Overriding Legitimate Interest

> stopping ‘denial of service’ attacks

Storing logs with IPs is no problem at all.


Storing the log files (or IP addresses in general) is not a problem IF you're using them only with a legitimate interest basis.

For instance, you can use this stored IP address to help identify whether your user has had their account breached, and prompt for extra verification before letting them log in. You can also do a full browser fingerprint for this purpose, this is all covered under legitimate basis.

However, once you use any of this data to market to the user then you are in breach of the GDPR as you did not have a consent basis for it. The storage was never a problem, it's the use of it that becomes a problem.


You're mostly right, but legitimate interest also require balance. Fingerprinting may be considered to be too intrusive if logs are enough.


Depends on the product, payments products generally use fingerprinting and present extra prompts if you're using an unknown device – that is kind of one of the main problems of the GDPR though, there are nuances and it's usually not white and black what can be done without specialised legal counsel (and sometimes, even then...)


Sounds like there could be an opportunity here for a GDPR noncompliant analytics product. Personally, my customers are in the United States and I don't want ambiguity in my analytics because of Lawyers who reside outside of my jurisdiction.


If your customers are of a European nationality you will need to comply as well.


Technically correct, but arguable... There are lots of UK and EU-based companies that blatantly breach the GDPR and get away with it as the regulatory bodies don't have the resources to chase after every breach at home, let alone abroad.

Unless you are a huge company or have a significant amount of customers in the UK/EU it's probably okay to ignore the GDPR.


Your interpretation is incorrect.

You have the right to log IP addresses only if they are used for the two purposes you listed, otherwise you will need explicit consent.


Creating clips from tv recordings:

    ffmpeg -ss 01:59:00.000 -i "interlaced.ts" -ss 00:00:12.000 -t 26 -max_muxing_queue_size 1024 -c:a libopus -b:a 96k -c:v libx264 -crf 20 -vf "yadif=1" -profile:v baseline -level 3.0 -pix_fmt yuv420p -movflags +faststart -y clip.mp4
Make clip compatible with WhatsApp:

    ffmpeg -i in.mp4 -map 0:v:0 -map 0:a:0 -map_metadata -1 -map_chapters -1 -c:v libx264 -preset slow -tune film -crf 32 -c:a aac -b:a 128k -profile:v baseline -level 3.0 -pix_fmt yuv420p -movflags +faststart out.mp4
Copying in various terminals:

    PuTTY: select
    tmux: Shift + select
    cmd: select + Enter in quick edit mode
    Windows Terminal: select + Right Click


Most streaming sites break a video into many small fragments, which are listed in a m4mu file. I have a script to download the fragments one by one using curl. To merge the video fragments back into one file, I do the following.

  Merge video files with ffmpeg
  - Make a file listing all the videos in sequence. E.g.
     file 'video01.ts'
     file 'video02.ts'
     file 'video03.ts'
     ...
  - Generate the file list for files in the current directory.
      (for %i in (*.ts) do @echo file '%i') > filelist.txt
  - ffmpeg command to combine videos
     ffmpeg -f concat -safe 0 -i filelist.txt -c copy output.mp4


For anyone needing this youtube-dl (and ffmpeg if you need post-dl conversion) can do this for you if it's any easier, point it at the index file and let it do its thing


Youtube-dl is great. I just wanted to build it from scratch, and it was very simple once the underlying streaming tech was understood.


I find -vf bwdif much smoother than yadif for action sport replays.


whoami


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: