• 0 Posts
  • 11 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle

  • I find it telling that AGI people seem to assume that AGI will spontaneously appear as a distinct entity with its own agency rather than being a product that will be owned and sold.

    People who have hundreds of billions of dollars can get mid-single-digit percent ROI by making very safe investments with that money, but instead they are pouring it into relatively risky AI investments. What do you think that says about their expectations of returns?







  • RegalPotoo@lemmy.worldtoTechnology@lemmy.worldGet your new PebbleOS watch
    link
    fedilink
    English
    arrow-up
    80
    arrow-down
    1
    ·
    1 month ago

    I’m pretty excited about this; my Pebble Time was the best watch I’ve even owned - smart or otherwise.

    That said, I don’t think I’m going to be preordering this given how badly the last Pebble Kickstarter went. For those who weren’t around at the time, Pebble (whose CEO is behind this venture) built his whole business around Kickstarter. The first 2 generations were wildly successful, but for the third generation they massively overextended themselves trying to get hardware into mainstream retailers, prioritised building stock for retail channels (because contracts) and ran out of cash before shipping for the majority of backers who had bankrolled this whole thing. Eventually everyone who hadn’t had their orders fulfilled got a refund, but that was only because FitBit decided to buy them. Eric seems like a nice guy and great at the technology - and I’m not saying that I could run a business any better - but I think I’ll wait until there is stock on hand for me to buy outright before I hand over my cash


  • Disclosure to the company is only half of responsible disclosure.

    1. Report bug to company privately, and specify a date where the details will be made public. 90 days is a good starting point, but there is room for negotiation up or down depending on how complex the bug is (more complex = harder for someone else to discover = less urgency to patch) and how much impact there is (more impact = more risk if someone malicious discovers it = more urgency)
    2. While you wait, apply for a CVE number and determine a CVSS score - this helps signal how critical the bug is
    3. Once the company publishes a patch (or the embargo date is reached, which ever comes first), publish details of the research

    The point of responsible disclosure is to balance the vendors need to have time to fix security bugs before the details are publicly known against the customers right to know that there are unpatched bugs so they can take measures to mitigate their risks. It isn’t a free pass for vendors to never patch things


  • Don’t know about US law, but where I live we have a “Preventative Detention Order” - the threshold for it is very high, but it essentially works as a sentence of “until rehabilitated”, you are incarcerated until the court decides that you are no longer a threat to the community, even in cases where a life without parole sentence wouldn’t be possible. In a world where I am supreme ruler, it’d automatically apply in cases where someone who has a conviction for a violent crime commits another violent crime.

    Also, how the hell does an 8 year old get a gun? Surely whoever failed to secure it - or even worse gave it to a minor - would be looking at an accessory change?


  • Kubernetes is awesome for self hosting, but tbh is superpower isn’t multi-node/scalability/clustering shenanigans, it’s that because every bit of configuration is just an object in the API, you can really easily version control everything - charts and config in git, tools like Helm make applying changes super easy, use Renovate to do automatic updates, use your CI tool of choice to deploy on commit, leverage your hobby into a DevOps role, profit