Mogzol

You can return a 451 error with a descriptive page, same as how sites have custom 404 pages

Yeah, I think it's pretty stupid, especially considering the F91-W is one of the most common and best selling watches in the world.

The F-91W has long been associated with terrorism for it's use in improvised time-bombs: https://en.wikipedia.org/wiki/Casio_F-91W#Usage_in_terrorism

I would assume the detections would need to come from a larger area than that to trigger it, like city sized.

Nobody is arguing against that. I fully agree that most people don't. The point was only that you can.

Yes, but you can replace that with your own unit they don't have control over.

Sure, but you still can use your own hardware if you choose to. And that's all that the original comment you replied to was saying. If you choose to use your own hardware, then Comcast won't have control over it and cannot do this wifi motion detection.

Of course, most people won't do this, but that's besides the point.

They're talking about MTP, which is supported by every modern (and old) Android device AFAIK. It's not exactly a USB Mass Storage device, but as long as you're not on a Mac, it behaves basically the same as one.

The first line on the page says

> Click the disk that's a different color. Use your eyes only!

Inspecting the color is cheating.

And even if you are using a "regular" video format like mp4, browsers will still use range requests [1] to fetch chunks of the file in separate requests, assuming the server supports it (which most do).

[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Ran...

I used winaero tweaker [1] to disable web search, the search is infinitely better now.

You can do the same tweak by editing the registry [2] if you don't want to download an app for it (though the app includes a lot of additional useful tweaks).

[1] https://winaerotweaker.com/

[2] https://www.tomshardware.com/how-to/disable-windows-web-sear...

No generation was raised like the previous one ever in history

So a public variable error should follow different naming conventions then a local variable? That doesn't seem right, the go wiki says you should use the 'err' prefix for both (capitalized for public variables though, obviously)

And I'm only asking about when you are giving an error a distinct name, not just naming it 'err'.

The link in the "Error variable naming" section seems to directly contradict what the section says.

The link (https://go.dev/talks/2014/names.slide#14) says:

  Error values should be of the form ErrFoo:
  
  var ErrFormat = errors.New("image: unknown format")

But the page says:

  // But if you want to give it a longer name, use "somethingError".
  var specificError error
  result, specificError = doSpecificThing()

And also says:

  Don't do this:
  [...]
  var errSpecific error
  result, errSpecific = doSpecificThing()

So should error variables written like `errSpecific` or `specificError`? The go wiki says they should be written starting with `err`: https://go.dev/wiki/Errors#naming

It blows my mind that somebody would get an answer from ChatGPT and post it here as a fact without doing the bare minimum to verify that it is actually true. It's insane, thanks for correcting them.

I think it would have been interesting to send two down, one oil-filled and one not and see at what depths they break (or don't). The watches are cheap enough that destroying one isn't much of a loss.

I use an esim.me card in my phone and once you program the card with the esim.me app, it shows up as a normal physical sim card on the phone with whatever plan the esim was for. I believe you can even move it to another device and it will still show up with the same plan, though I haven't tried that.

The only issue I've had with it is that some esim provider apps refuse to work on a phone that doesn't have esim capabilities, and since the phone sees the card as a normal sim card, the apps don't work. I assume that will be an issue for any of these cards. Not a huge issue though, most esim apps/websites will still let you get the QR code or download the profile even if your phone doesn't natively support esim, and you just enter that into the esim.me app to program the card.

It's just an example async call, it could be anything. It's not the important part of that code example, it's only purpose is to show that an async call is happening. It could be written as a try/catch, or it could be written how they wrote it. I guess they chose that way because it's short and to the point.

I think it is meant to be a generic phone, the edges and front camera are wrong for an iphone, but then the home button is very distinctly an iphone. It is weird.

True, I think it's more accurate to say that the video can be shown in only black & white while still remaining mostly true to the original content, which isn't the case for most videos. So you can play bad apple on two-color display and still easily be able to recognize it as bad apple, which definitely contributes to its "hello world for video" status.

I doubt it is due to legal concerns if Ubuntu, Fedora, and FreeBSD are all distributing their own builds.

Pretty cool, though seems very similar to explainshell.com.

Also noticed that it breaks with single quotes, for example, this works:

    curl -H "Some-Header: value" http://example.com

But this causes it to error:

    curl -H 'Some-Header: value' http://example.com

Speaking of large batch files, if anyone has ever softmodded a Wii, there is a good chance you used ModMii, which is by far the largest batch program I've seen. The main script [1] is a batch file that clocks in at over a megabyte. I used to be pretty into the Wii modding scene and remember talking with the author of that script about random batch things a few times. I can't imagine maintaining a file that big.

[1] https://github.com/modmii/modmii.github.io/blob/master/Suppo...

The point of this project is more about squeezing the Wii into the smallest possible footprint rather than making it convenient to use. If you wanted something similar with ports integrated though, check out the GC Nano (which despite looking like a Gamecube has Wii internals), or Short Stack.

GC Nano: https://bitbuilt.net/forums/index.php?threads/gc-nano-the-wo...

Short Stack: https://bitbuilt.net/forums/index.php?threads/short-stack-th...

All that really matters is how much power (watts, i.e. voltage * current) the device draws compared with how much power the laptop was designed to output. Shifting the voltage doesn't really affect anything other than losing some power to conversion inefficiencies.

Interestingly, the author's blog post [1] mentions that this is due to technical limitations and not specifically done by choice, although I do like the effect.

> When we zoom in, we discard the information of the largest meta-metapixel, so it is not always possible to reconstruct the same scene when we zoom out again.

> Since zooming in and out can be continued indefinitely, we also realize that we need infinite information to accurately represent "our current position".

[1] https://blog.oimo.io/2023/04/10/life-universe-en/

How large are the files you're formatting? I have prettier set to format on save in vscode and even for the largest files in my codebase (>1000 lines) it formats near-instantaneously on my 2019 macbook pro. Definitely well under a second.

The difference is that it is actually valid according to the HTML spec. Browsers will render lots of invalid HTML which is shorter than that, but if you put such HTML in a validator such as [1], it will have errors.

Putting <!DOCTYPE html><title>.</title> in that validator returns no errors (it does have a warning though).

Although in response to OP's question, no, I don't think it is related.

[1] https://validator.w3.org/nu/#textarea

Maybe I'm misreading the original article, but it sounds like it would also apply to apps distributed only through the regular App Store:

> Core Technology Fee — iOS apps distributed from the App Store and/or an alternative app marketplace will pay €0.50 for each first annual install per year over a 1 million threshold.

I think you are underestimating how many apps get over 1M downloads. According to [1], the Google Play Store has over 34000 apps with 1M+ installs, I assume the number is similar for the App Store.

So if you have a popular free app, there is a good chance you will hit the 1M install threshold. This change is basically forcing you to monetize your app. Plenty of people can afford losing $99/year for having a free app that isn't monetized. Not many can afford losing several thousand per month.

[1] https://www.androidrank.org/categorystats?category=&price=al...