• 0 Posts
  • 11 Comments
Joined 6 months ago
cake
Cake day: January 5th, 2024

help-circle




  • I have been utilizing BunkerWeb for some of my selfhost sites since it was bunkerized-nginx. It is indeed powerful and flexible, allowing multi-site proxying, hosting while allowing semi-flexible per-site security tweaks (some security options are forcibly global still, a limitation).

    I use it on podman myself, and while it is generally great for having OWasp CRS, general traffic filtering targets and more built on top of nginx in a Docker container, the way Bunkerweb needs to be run hasn’t really remained stable between versions. Throughout several version upgrades, there have been be severe breaking changes that will require reading the setup documentation again to get the new version functional.


  • Before going any further to adjust your Z offset and other factors to tune for better bed adhesion, you should probably adjust your bed to actually be level as well as ensure (seeing that you only have one z lead screw?) that the X axis frame isn’t sagging on the side not containing your Z lead screw. Once you’ve got those factors sorted out, you should check your probe repeatability and then set your Z offset accordingly.

    Bed adhesion even with proper, clean first layers can be a pain depending on the bed surface, material being printed, how clean the bed is of oils and other contaminants, how hot the material is being extruded, and how hot the bed is among other factors. While using a bed mesh will greatly help to account for off-zero unevenness in your bed surface, you really shouldn’t use it to compensate for uneven bed leveling (especially when it looks like you are nearing more than 0.5 mm in unevenness).

    To diagnose other print issues, it will be helpful to see a picture showcasing the problems described in a failed print.


    As a side note, it is somewhat difficult to read your Klipper config file without using view source as it is being markdown formatted. You can negate it by using three graves on the lines above and below it so that it is wrapped in a ‘code block’ and isn’t formatted.

    ```
    Some code
      eeeee
      fffff
    ```

    Turns into

    Some code
      eeeee
      fffff
    

  • jrgd@lemm.eetoAndroid@lemdro.idIntroducing the OnePlus Watch 2 - Your Partner in Time!
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    4 months ago

    User-Centric Innovation: Unveiling the Industry-Leading Battery Life

    We know how a smartwatch becomes integral to its wearer’s life, and battery life can’t be a concern. That’s why we went back to the drawing board, driven by community feedback, to ensure the OnePlus Watch 2 delivers an exceptional user experience. With up to 100-hour battery life in full Smart Mode, it sets a new industry standard, ensuring that your watch keeps pace with your life, uninterrupted.

    Really impressive how OnePlus is touting a relatively mediocre 4-day (at best) battery life on a smartwatch as something exceptional or something that they (falsely) claim as industry-leading. Maybe it is good by typical WearOS device standards, but is by no means top of the line for the smartwatch industry.



  • jrgd@lemm.eetoAndroid@lemdro.idFossil is quitting smartwatches
    link
    fedilink
    English
    arrow-up
    18
    ·
    5 months ago

    Not the same person, but I greatly enjoy my (now second) Pebble classic for several reasons, which I imagine some are shared between Starayo.

    • Always-on Display
    • Week-long battery life
    • High contrast display that can be read easily in low light as well as in direct sunlight
    • Simple notifications support, with quick canned replies
    • physical button navigation that make the watch easy to use without needing to look at it
    • Isn’t obscenely large
    • quick launch application shortcuts from holding side buttons
    • simple media playback control that is responsive
    • Doesn’t attempt to be another smartphone, but rather as a local companion to your existing smartphone (doesn’t thrive on individual apps, but rather companion apps to complement smartphone usage)
    • Customizable and relatively simple to write applications and watchfaces for.

    Unfortunately for me, fossil’s watches do not match up. Looking at the gen 6, still uses an ill-suited AMOLED display that is bound to have poor contrast in direct sunlight unless the brightness is cranked so far that it will blow through the battery. Even then, the average battery life on the gen 6 is atrocious compared to most Pebble models as many reports say it can make it through one day. I’m sure by now, WearOS devices have worked out some of the kinks to make them easier and faster to use, though I am not sold on needing a personal assistant in order to do basic tasks (as Fossil markets their gen 6 smartwatch; I do doubt that this is necessary for general function).

    Also, this might be controversial, but I personally feel that a device that has Bluetooth and is intended to communicate with a device that is often within ten feet of it really doesn’t need to waste resources and probably become more of a privacy nightmare by including Wi-Fi, LTE, and other data communication methods (beside NFC). Furthermore, pretty much every WearOS device I have seen has had a struggle to keep battery life for more than a couple days, and everyone deems that devices that can should be praised for whatever reason. Seeing as my ancient smartwatch that does most of what these newer watches do yet can effortlessly hold a six day battery life at worst, I seriously question why newer watches that have so much compromise and are incredibly misguided as to what a complementary wearable should be are what are being developed. Not to mention that the Pebble classic on launch was $99 USD whereas one can easily find $400+ smartwatches that still have way too much compromise in comparison.