[–] 3 points 5 months ago

Twine is a tool for writing nonlinear, choose-your-own-adventure type stories. Outputs to html, so it super-portable. It might fit your needs, depending upon what you had in mind for game play outside the dialog. Still might be useful for story-boarding, and mapping out the narrative.

  • source
  • [–] [S] 2 points 5 months ago

    Sure, that's possible of course, but that doesn't really change the status quo. The government has always had far more ability to create fake content than individuals. However, this type of system would allow individuals to prove veracity of their content, which is where the real value comes in my opinion. If you have a professional photographer then they can prove that their camera took a particular picture. If you trust that photographer then you can know that a picture came from that individual. I think that's going to be the dynamic going forward. People will decide on what sources they trust, and the technology will provide a way to tell what the source for the media is.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (1 child)

    DRM has this same problem that I was referring to. Because Blu-ray players need to have a secret key to decode movies, attackers have been able to extract the keys. Same with DRM streaming 4K from video streaming sites like Netflix to phones. Attackers have rooted phones and extracted keys so that there is now software to download from Netflix in full 4K. I don't know of a DRM that hasn't been cracked.

    What I meant with my second paragraph is that a government could secretly compel a respected camera company to hand over the keys. Then that government could deep fake photos to provide justification for actions and the photos would appear genuine due to the keys signing them.

  • source
  • parent
  • context
  • [–] [S] 1 point 5 months ago

    You'd need a pretty high resolution source image plotted for that to work well, modern digital cameras have 20+ megapixels, and if you take a picture of a low resolution image it'll be very obvious. I'm sure it's possible, but definitely not that easy to do.

  • source
  • parent
  • context
  • [–] [S] 1 point 5 months ago (2 children)

    In a similar way to the way DRM works in stuff like consoles today. And I'm not sure I follow the second problem here. Anybody could create this type of system going forward. But you have to produce hardware to take a picture in the first place, so obviously hardware manufacturers would be the ones to apply this process. The key simply links a photo back to a manufacturer. It doesn't give companies monopoly on anything.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (3 children)

    How can a camera have access to the signing key and prevent an attacker gaining access to that key?

    Also, this would give camera companies (and any entity with leverage over the camera company, including their government) the power to decide what images are 'true' in the public's eye. Companies that control the keys would need to be good at securing the keys.

  • source
  • [–] [S] 1 point 5 months ago

    This concept describes a hardware anchored proof system for proving the originality of and the precise sensor origin of photographic media. The camera hardware would use a combination of secure enclaves and asymmetric cryptography like RSA to digitally sign images at the moment of capture making it possible to verify the physical origin of the file. The camera manufacturer could operate a Certificate Authority where users can validate the embedded signature against the registered public key of the specific device. This architecture would allow verifying that an image is an actual sensor derived photograph.

    The neat part here is that the algorithm survives retouching of the photo, so you can still do typical things like cleaning up contrast, color balance, etc., without destroying the authenticity of the image. Given how good generated images are getting, it seems to me that deepfake detection approach is dead in the water, and something like this would establish a proactive foundation for cryptographic provenance of real photographs.

  • source
  • [–] 12 points 5 months ago

    Jira is just part of Atlassian's offerings. You've got the second-rate Wikipedia knock-off that is Confluence, the will-it-won't-it play video hosting of Loom, and BitBucket with its bizarrely awful API performance and rate limits for a Git host. Admittedly, I used to think that BB presented pull requests in a more reviewable way than eg. GitHub, but they're abandoned the things that made it distinctive in exchange for the follow-the-leader approach, so now it's just a less-good GH. And I don't say that lightly, it's a low bar to limbo under.

    In fact, I kind of prefer managing tickets via post-its on a whiteboard then using Jira, as it actually allows you to see everything important at a glance, and micromanaging middle management don't get to set up bizarre and wonky workflows and rules, and a thousand bullshit fields to fill in on every ticket.

  • source
  • parent
  • context
  • [–] 11 points 5 months ago* (1 child)

    Um is there anything to know? Jira is a basic CRUD app that's backed by reasonably good deployment, operations, marketing, sales, and low enough prices for smaller plans that people don't bother to self-host their own alternative. But it doesn't seem mysterious how it works.

  • source
  • [–] [S] 11 points 5 months ago

    I was curious about the NDA bit as well, but I guess it's the sort of stuff you'd talk about in a tech interview as well. He's not revealing any deep secrets there. And while none of this stuff is necessarily rocket science, it is always interesting to see how big companies structure stuff that needs to run at scale. A lot of this stuff gets figured out through trial and error, and you can save some time by learning what worked for others.

  • source
  • parent
  • context
  • [–] 11 points 5 months ago* (1 child)

    I haven't watched the video, but two things I wonder:

    • Surely he signed an agreement when he was hired promising they could hit him with an enormous lawsuit if he ever spilled "muh trade secrits." I'm wondering how he got away with this unless all he's sharing is public info.
    • Is anything Atlassian has done really that non-obvious that anyone couldn't just reproduce (or improve on) it from scratch just given some thinking and elbow grease? (Like, Confluence is a glorified WYSIWIG editor. Bamboo is Jenkins slightly spiffed up so it doesn't still feel like something straight out of 1991. And another Jira can be easily procured by anyone willing to travel to hell and request the next steaming shit Satan takes.)
  • source
  • view more: ‹ prev next ›