[–] 17 points 2 days ago (1 child)

Fine print. Probably didn't work out well.

Special eMachines™ Upgrade for $99 to eMachines™Network Members Only

Subscribe to the eMachines™ Network for 24 consecutive months and we’ll upgrade your eMachines™ for only $99 (plus shipping)!

Here’s how it works: If you live in the contiguous U.S. or Canada, we’ll contact you after you’ve subscribed to The eMachines™ Network for 24 months and offer to upgrade your eMachines™ PC to whatever processor technology is built into whatever eMachines™ PC you can buy at the time of the upgrade for whatever you paid for your original machine. For example, let’s say your eTower* PC was priced at $399 (not including promotional discount) and runs a 366 MHz processor, but at the time of the upgrade $399 would buy an 800MHz eTower. We’ll upgrade your eTower* to 800MHz.

All you have to do is ship us your PC within 90 days, plus $99 (or Canadian equivalent), proof of purchase and payment for return shipping. We’ll promptly upgrade it and return it. Note: you’ll have to back-up your data to avoid accidental loss, and use the original packaging (we have replacement packaging available). See more detailed information"

  • source
  • parent
  • context
  •  

    I am looking for a self hosted bookmark manager. Does anyone have any experience to share?

    Ideally I'd like:

    • Self hosted with FOSS license
    • Firefox integration (ideally on android, too)
    • ideally no AI features or at least opt-in
    • ideally human driven development (as little AI code as possible)

    Linkwarden, Karakeep, Nextcloud/bookmarks seems to be the main ones.

    [–] 8 points 6 days ago (1 child)

    So far so good. I've been running regular speed tests to compare with mullvad, while I had both. Speed wise ivpn is slightly slower on average (5% or so), but also seen occasional large slowdown on ivpn which I didn't see on mullvad. Especially some locations seem very inconsistent on ivpn.

    It's good, but some improvements on consistency would be welcome.

  • source
  • [–] 1 point 1 month ago* (last edited 1 month ago) (1 child)

    Oh okay, I just assumed the main method to redirect the vendor cloud connections to the local valetudo was based on the patch DNS parts in dustbuilder that seems present on most models, but if you say more is required elsewhere to block vendor cloud connections I'm sure that's true.

    In any case your work is highly appreciated! And i didn't mean to suggest that it hasn't taken a massive amount of work overall to make valetudo work as well as it does.

  • source
  • parent
  • context
  • [–] 5 points 1 month ago (4 children)

    It's just DNS based, and iirc dont require any major effort other than patching the hosts file. Of course it is possible it is not enough, but I have high confidence in the authors after also having watched various talks at I.e DEFCON, that i would be surprised if they missed the firmware doing other nasty things.

    Patching DNS is specifically possible to enable/disable on the firmware build tool: I.e https://builder.dontvacuum.me/_dreame_r2416.html and the source for that is here https://github.com/dgiese/dustbuilder-script-public/blob/7afed16999711833a8ac0b3b482e935c3ef77219/modifys8image.sh#L169

  • source
  • parent
  • context
  • [–] 4 points 1 month ago (10 children)

    Valetudo actively blocks the cloud connections. Also, only firmware versions specifically installed with Valetudo is supported (so no chance an update to the original device firmware happens, and does new things).

    I think there's a very low chance something escapes to the vendor cloud.

    None the less, I personally run these on a separate VLAN without internet access.

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

    That sucks, a good company would instead work with QBZ to ensure it's resolved properly.

    I didn't see any other reports of people being banned. I'll just keep using QBZ but better keep the subscription monthly in case...

  • source
  • parent
  • context
  • [–] 1 point 4 months ago*

    The counterpoint is that if you indicate at a point when it's unsafe to change lanes to communicate your intention to, for example change lane after a car passes, then the other car might think you missed them and therefore might take potentially risky corrective actions.

    Personally I indicate when it's safe, but don't aggressively change lanes right away, waiting a few seconds. Seems like a good approach to me.

  • source
  • parent
  • context
  • view more: next ›