HN user

NAR8789

474 karma
Posts9
Comments81
View on HN

Try from inside the signal app itself instead of system settings? On android Signal has an option at hamburger menu > Settings > Notifications > Notifications (toggle switch)

Oh... hmm, two toggles actually. One at Settings > Notifications > Calls > Notifications toggle, and the other at Settings > Notifications > Messages > Notifications toggle

I'm curious why you didn't do something like generate new tiles one at a time, but just expand the input area on the sides with already-generated neighbors. Looks like your infill model doesn't really care about tile sizes, and I doubt it really needs full adjacent tiles to match style. Why 2x2 tile inputs rather than say... generate new tiles one at a time, but add 50px of bordering tile on each side that already has a pixel art neighbor?

I think the core idea in "masking" is to provide adjacent pixel art tiles as part of the input when rendering a new tile from photo reference. So part of the input is literal boundary conditions on the output for the new tile.

Reference image from the article: https://cannoneyed.com/img/projects/isometric-nyc/training_d...

You have to zoom in, but here the inputs on the left are mixed pixel art / photo textures. The outputs on the right are seamless pixel art.

Later on he talks about 2x2 squares of four tiles each as input and having trouble automating input selection to avoid seams. So with his 512x512 tiles, he's actually sending in 1024x1024 inputs. You can avoid seams if every new tile can "see" all its already-generated neighbors.

You get a seam if you generate a new tile next to an old tile but that old tile is not input to the infill agorithm. The new tile can't see that boundary, and the style will probably not match.

I don't know why California's electricity costs so much, but the gas prices are high due to regulation distorting the market. California has special California gas produced only at in-state refineries. It's for a good cause--California's gas, "CARB gas" is cleaner. But the gas market in California is segregated from the wider US market

When cats walk or climb on your keyboard, they can enter random commands and data, damage your files, and even crash your computer.

And they might turn you into the Freakazoid

My Truck Desk 9 months ago

Import one from Australia or the UK? Someplace where they drive on the left?

RFC 3339 vs. ISO 8601 11 months ago

This sounds like a footgun.

At some point some application developer will introduce a bug where they're not sending utc.

Without the time zone, the wrong times will end up in the database, bad data mixed in with good. This will be a nightmare to fix.

With the time zone, I don't think this class of bugs is possible. Most application developers will wrap the time in an object that allows them to do time operations without needing to directly handle time zone in most cases.

Wait, how common is it to not know touch typing?

Honest question, maybe a blind spot of mine. Touch typing is so integrated into my daily experience it feels like driving or riding a bike. I mostly learned to touch type in the 90s just chatting with friends on AOL instant messenger. I think of touch typing as something nearly everyone picks up just as a side effect of living with computers.

I think with proper cycling posture you can take the pressure off of your wrists.

Use your back and shoulder muscles to support your upper body and arms, so that you can ride with elbows bent. If you can bend your elbows, you can avoid pushing on the handlebars for support. That will make for more comfortable wrists with or without a keyboard.

Reference: Sheldon "Ouch!" Brown https://sheldonbrown.com/pain.html#wrists

I once called Sonic on a weekend because my modem kept rebooting. They answered immediately, and the debugging felt like magic.

"My modem keeps rebooting."

"Put the modem to your ear. Is it hissing?"

"Um...? Yes. Yes, it's hissing."

"Bad capacitors. We'll send you a new one."

This was during the Capacitor Plague https://en.wikipedia.org/wiki/Capacitor_plague , so clearly he'd seen this before. Still, fastest support resolution I've ever experienced.

Infinite Craft 2 years ago

I think you can reduce state. Rather than tracking maxElementReached per-element, maintain a single maxElementReached for the first n elements. March the first n elements forward in lockstep, and grow n by 1 whenever you exhaust all available combinations for that set

  1. Combine the first element with every next element until exhausted.
  2. Catch up the second element to where the first element got to.
  3. Combine the first two elements with every next element, until exhausted.
  4. Catch up the third element.
  5. Combine the first three elements with every next element
  6. etc.
In pseudocode...
  n = 1
  maxElementReached = -1
  
  while(n < totalElements()) {
    while(maxElementReached + 1 < totalElements()) {
      maxElementReached = maxElementReached + 1
      Combine each of the first n elements with element[maxElementReached]
    }

    // we've exhausted all possible combinations for the first n elements.
    // increase n by 1 and catch up the new element to keep going
    Combine element[n] with each element from n to maxElementReached
    n = n + 1
  }

Because it only takes log(n) digits to represent n.

9 is 1 digit, takes 9 steps.

99 is 2 digits, takes 99 steps.

999 is 3 digits, takes 999 steps.

An input d decimal digits long takes O(10^d) steps.

The runtime is exponential in the "size of the input", because the size of the input is usually taken to be the length of the binary or decimal representation of the number rather than the magnitude of the number.

This is sloppy summarizing by ars. In a real attack tampered logins need not show up as failures.

From the original article https://mega-awry.io/ (emphasis mine):

Since the server code is not published, we cannot implement a Proof-of-Concept (PoC) in which the adversary actually controls MEGA. Instead, we implemented a MitM attack by installing a bogus TLS root certificate on the victim.

...

The log in attempt fails, which is only a limitation of the MitM setting. A malicious cloud provider can perform this attack without the user noticing.