josephernest

Please stop this.

How did we collectively accept that it's ok that a private company can forever change how our sky looks like (especially at night) for the generations to come?

This is so dystopian but it seems nobody cares. The most important thing is to have fast internet to watch cool AI-generated videos.

So depressing.

In a webring, do you usually always have the same fixed webring neighbours?

Back in the days, how did it usually work about this : If your neighbour has only 7 visitor/day but you do have 100/day, can you ask to change and have this other 10000 visitor/day-site as neighbour?

As a webring admin, how do you manage these member requests?

You can use this small Python script to display an histogram of `reasoning_output_tokens` in your past Codex sessions. I do see a spike at 516 indeed.

  import os, glob, re
  import matplotlib.pyplot as plt
  vals = []
  for f in glob.glob(os.path.expanduser(r"~\.codex") + r"\**\*", recursive=True):
      if os.path.isfile(f):
          try:
              s = open(f, "r", encoding="utf-8", errors="ignore").read()
              vals += [int(x) for x in re.findall(r'"reasoning_output_tokens"\s*:\s*(\d+)', s)]
          except Exception:
              pass
  plt.hist(vals, bins=200, range=(0, 5000), weights=[100 / len(vals)] * len(vals))
  plt.xlabel("reasoning_output_tokens")
  plt.ylabel("%")
  plt.show()

This gives a 77 MB folder, not containing the browser (we're now using the OS' webview).

I wouldn't call this "Small by default".

I used this main.ts file: `Deno.serve(() => new Response("<h1>Hello, desktop</h1>", { headers: { "content-type": "text/html" }, }));`

and `deno desktop --backend webview main.ts`.

Unfortunately, launching `deno-test.bat` opens an empty white window, freezed (with waiting cursor...) on my Windows 10.

IIRC Electron hello world is ~ 100-150 MB because it bundles a browser/Chromium runtime.

So I hoped we could have a <= 20 MB solution by reusing the OS webview or similar. Having more than 400 MB is a bit deceptive for me. (Again: maybe I just did something wrong in the config: should I do something else than `deno desktop test.ts`?)

I just tried `deno desktop helloworld.ts` and the result is 442 MB. So it's not any lighter than Electron (see my toplevel comment)

> deno desktop is opinionated about those tradeoffs:

> Small by default, full Node compatibility

I tried `deno desktop index.ts` with the 5-line Hello world in the article.

Result (Windows 10): 442 MB. Ouch.

I thought it would be smaller than an Electron build, but it's far worse. Did I do something wrong?

(libcef.dll: 247 MB) (deno-test.dll: 78 MB <- contains the hello world)

Let's say I want to compile a helloworld.cpp with no build tools installed yet.

What is the minimal winget command to get everything installed, ready for : cl main.cpp ?

Ps: I mean a winget command which does not ask anything, neither in command line, nor GUI ? Totally unattenfed.

In France (and probably everywhere) there is currently massive deployment of FTTH (fiber to the home) and removal of copper lines, since a decade.

Does this mean we could have kept the good old copper lines from 60 years ago and still enjoy 1 Gbit internet in residential areas?

Out of curiosity, any other example without redirect, in which the URL stays https://<ip> in the browser?

Do I understand correctly: would someone have a concrete example of URL which is both an IP address and HTTPS, widely accessible from global internet? e.g. https://<ipv4-address>/ ?

Related: for some hardware project, I have a backend server (either C++ or python) receiving frames from an industrial camera, uncompressed.

And I need these frames displayed in a web browser client but on the same computer (instead of network trip like in this article).

How would you do this ?

I eventually did more or less like OP with uncompressed frames.

My goal is to minimize CPU usage on the computer. Would h264 compression be a good thing here given source and destination are the same machine?

Other ideas?

NB: this camera cannot be directly accessed by the browser.

Why would it be limited to ~ 100 connections on a 1-4 GB RAM server? Out of curiosity if we fork() httpd and exec() the cgi handler, it doesn't take the same RAM as the parent process and it could just take a few KB or MB, is that right? So I guess 1000+ concurrent connections even on a small server is possible.