needanke

joined 1 year ago
MODERATOR OF
[–] needanke@feddit.org 4 points 1 day ago (1 children)

You can have mine, I'm done with it.

[–] needanke@feddit.org 1 points 4 days ago

Then that is not what the article is about..

[–] needanke@feddit.org 11 points 4 days ago* (last edited 4 days ago)

How do you currently store your passwords? I would also consider that a third party with an adittional atack surface if you are considering the passkey location one.

Also your argument

(if you ignore the operating system, web browser, network protocols, etc., but that's part of using the tech).

is faulty. That is because passkeys exist in part to mitigate those atack vectors. Mitm, a compromised browser or client, etc. is less of an issue with passkeys. The information transmitted during an authentication can not be reused on another authentication attempt.

I don't agree on passkeys complicating things either. For me the authentication-flow is not more complicated then KeePasses autofill.

Assuming one can be 'tech savy' enough to not fall for fishing is bad. There are quite advanced attacks or you might even just be tired one day and do something stupid by accident.

What's that now? The weak point is the user's ability to implement MFA and biometrics? The same users who couldn't be bothered to create different passwords for different sites?

You don't expext the user to 'implement' mfa or biometrics. You expect them to use it. And most places where a novice would store passkeys don't just expect but enforce it. It is also way simpler to set up biometrics on one device compared to keeping with a good password strategy.

[–] needanke@feddit.org 3 points 4 days ago

You can set a pin on most passkey devices so that it doesn't serve the authentication without it.

[–] needanke@feddit.org 3 points 4 days ago* (last edited 4 days ago) (1 children)

Mostly yeah. Maybe not, if you bloodlucose is too high allready but usually you should be fine.

[–] needanke@feddit.org 3 points 4 days ago (4 children)

You can stlii eat cake if you're a diabetic.

[–] needanke@feddit.org 6 points 4 days ago (1 children)

Assistant District Attorney Michael Mattson said Woeltz and Duplessie allegedly lured the man to New York from Italy by threatening to have his family killed.

Really a stretch of the word lured...

[–] needanke@feddit.org 4 points 6 days ago* (last edited 6 days ago)

Bombengeschichte !

[–] needanke@feddit.org 29 points 1 week ago

Claim: He’s 34.

True: It’s time to get your shit together.

Wow ...

[–] needanke@feddit.org 51 points 2 weeks ago (12 children)

The baker profession actually immensly suffered from increased automation...

[–] needanke@feddit.org 8 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Kein Plan, wo genau die Pfütze jetzt ist, aber sie ist nicht mehr mein Problem.

Bitte schau nach, hat mein Nachbar sich auch Mitte des Jahres gedacht und jetzt kann ich seit drei Monaten nicht mehr zu Hause wohnen...

[–] needanke@feddit.org 1 points 2 weeks ago

Was war der altet Titel denn?

 
57
Turtleshell (feddit.org)
submitted 3 months ago* (last edited 3 months ago) by needanke@feddit.org to c/microblogmemes@lemmy.world
 

Fors off: I am a total beginner when it comes to docker. I do have some self hosting experience, but run pretty much everything in its on lxc and treat it like a full linux system.

Recently I installed immich in a container and was surprised to see how well it worked.

This lead my to finally tackle something I have been putting off for way to long; installing nightscout (a self hosten glucose monitoring&reporting utility).

For that I followed their guide. Everything worked well up untill the point where I wanted to connect to the web interface. I started of by entering my domain into the nightscout containers arguments (in the form subdomain.domain.tld). Then I used my reverse proxy (nginx, not inside docker) to forward the subdomain to the docker IP on Ports 443, then 80 and lastly the one displayed at the container when listing them with docker ps. None of those worked (I was not able to get a certificate using letsEncrypt and got a 404 when connecting without tls).

I then entered nighscout.[docker-IP] and tried to access it dkrectly which did not work either.

When googling I only find comparisons on how to set up nginx in Docker, or comparisons between the two.

docker-compose file

  GNU nano 7.2                                                                                                 docker-compose.yml                                                                                                          
version: '3'

x-logging:
  &default-logging
  options:
    max-size: '10m'
    max-file: '5'
  driver: json-file

services:
  mongo:
    image: mongo:4.4
    volumes:
      - ${NS_MONGO_DATA_DIR:-./mongo-data}:/data/db:cached
    logging: *default-logging

  nightscout:
    image: nightscout/cgm-remote-monitor:latest
    container_name: nightscout
    restart: always
    depends_on:
      - mongo
    labels:
      - 'traefik.enable=true'
      # Change the below Host from `localhost` to be the web address where Nightscout is running.
      # Also change the email address in the `traefik` service below.
      - 'traefik.http.routers.nightscout.rule=Host(`localhost`)'
      - 'traefik.http.routers.nightscout.entrypoints=websecure'
      - 'traefik.http.routers.nightscout.tls.certresolver=le'
    logging: *default-logging
    environment:
      ### Variables for the container
      NODE_ENV: production
      TZ: [removed]

      ### Overridden variables for Docker Compose setup
      # The `nightscout` service can use HTTP, because we use `traefik` to serve the HTTPS
      # and manage TLS certificates
      INSECURE_USE_HTTP: 'true'

      # For all other settings, please refer to the Environment section of the README
      ### Required variables
      # MONGO_CONNECTION - The connection string for your Mongo database.
      # Something like mongodb://sally:sallypass@ds099999.mongolab.com:99999/nightscout
      # The default connects to the `mongo` included in this docker-compose file.
      # If you change it, you probably also want to comment out the entire `mongo` service block
      # and `depends_on` block above.
      MONGO_CONNECTION: mongodb://mongo:27017/nightscout

      # API_SECRET - A secret passphrase that must be at least 12 characters long.
      API_SECRET: [removed]

      ### Features
      # ENABLE - Used to enable optional features, expects a space delimited list, such as: careportal rawbg iob
      # See https://github.com/nightscout/cgm-remote-monitor#plugins for details
      ENABLE: careportal rawbg iob

      # AUTH_DEFAULT_ROLES (readable) - possible values readable, denied, or any valid role name.
      # When readable, anyone can view Nightscout without a token. Setting it to denied will require
      # a token from every visit, using status-only will enable api-secret based login.
      AUTH_DEFAULT_ROLES: denied

      # For all other settings, please refer to the Environment section of the README
      # https://github.com/nightscout/cgm-remote-monitor#environment

  traefik:
    image: traefik:latest
    container_name: 'traefik'
    command:
      - '--providers.docker=true'
      - '--providers.docker.exposedbydefault=false'
      - '--entrypoints.web.address=:80'
      - '--entrypoints.web.http.redirections.entrypoint.to=websecure'
      - '--entrypoints.websecure.address=:443'
      - "--certificatesresolvers.le.acme.httpchallenge=true"
      - "--certificatesresolvers.le.acme.httpchallenge.entrypoint=web"
      - '--certificatesresolvers.le.acme.storage=/letsencrypt/acme.json'
      # Change the below to match your email address
      - '--certificatesresolvers.le.acme.email=[removed]'
    ports:
      - '443:443'
      - '80:80'
    volumes:
      - './letsencrypt:/letsencrypt'
      - '/var/run/docker.sock:/var/run/docker.sock:ro'
    logging: *default-logging

 

The sensor is located on the case (not near the exhaust) of the server. With the structure of my appartment this is the only place I can realistically put my Server but sadly also the hottest place in my appartment.

The outside temperature is supposed to reach 36°C today so I expect the ambient temp for the server to rise another 2-3 degrees.

 
 

cross-posted from: https://feddit.org/post/13428701

This year I did my first bike packing trip. For starting out I had rented some equipment, but with the goal of doing more trips in the future, getting some bags of my own was clearly on the list. With the idea of using panniers for my main storage, I wanted to add some fork bags to balance out the weight a little. Also they are the least obstructive (other than frame bag maybe) from my POV. Somewhat enjoying DIY, the idea of designing the cages myself grew on me.

What this is

Some insights and thoughts on the process of designing and making some aluminum cargo cages for a bike.

What this isn't

A guide on how to design and make aluminum cargo cages for a bike. I have no professional training on anything I did here. This is my first time doing something like this.

Designing

Sketch

After making some sketches on paper, I quickly jumped into 3D modelling on the PC.

The software

The software I choose was OpenSCAD. Reasoning was that I like open source software and I don't know any CAD software anyway. With it being a non-interactive tool, I hoped to somewhat make use of my coding knowledge/background. You write a script and the tool compiles it into a 3D model.

This however, did not work out very well. Going into it without much of a plan, I ended up with a very confusing file with loads of duplicate code and lots of guessing when trying to figure out dimensions. This was not the fault of the tool, but only my own. Not saying I'll never go back to it, but for the next job I will try some more interactive tooling. Some more structure and thought out process would benefit any tool however, so that's a learning I'll take with me.

The looks

Hard requirements were the screw positions for mounting to the fork and space for some straps where the bag is attached. In the middle of designing I noticed, that I might want some material running from the screw attachment points across the whole width of the piece (this might not have been required since the 3mm aluminum I used was plenty strong).

The whole design evolved around these requirements and some hexagons I wanted to add. Everything was kept symmetric and I tried to pick up the angles from the hexagons in the other angled pieces.

For sizing, I tested my dimensions on some cardboard cutouts and went with what felt right.

Finished cage design

The issues

  • The lower part was meant to be bent around and then welded at the seams. However I failed to provide additional material for the bending, therefor it was cut of and completely welded in the final product.
  • The lower part is too wide. Instead of taking a second to think about it, I just kept the lower piece wide with the idea of grinding of the excess. I should have made the diagonal piece of the notch the same length as the vertical line it will get welded to.
  • The straps of my chosen bags do not line up perfectly with the cutouts on the cage. There is enough space to make it work and not look super off, but it would be smarter to get the 'target bag' first.

Also I think it turned out a little like any cage you can buy in a shop. Wish I had made it a little more unique, maybe carry the hexagon idea along the edges...

Fabricating

Having access to at least some of the tools required for fabrication made the project seem somewhat reasonable in the first place. I would not know how to go about this, if you don't have a welder (other than designing a part that does not require welding).

Laser cutting

The whole idea heavily evolved around the idea of using a laser to cut my model from some aluminum sheet. However the laser I planned to use was not available anymore by the time the design was finished. No big deal I thought, there are ordering services for just about anything online. Which there are. But many of them ask a heavy fee for low part counts. To a level that would shut down the whole idea. It took quite some searching until I found someone willing to do the job for a feasible price. Had I not found a laser, filling and cutting with a saw would have been my last resort. Luckily it didn't come to that.

Other than the design issues mentioned above, it turned out just like I wanted!

Welding

You should find someone else to tell you about TIG welding. On the photo you can see the lower base that turned out too wide and never got ground off. Also the lower base that was cut off instead of bend due to missing clearance.

Welded cage

Painting

3 base coats, 3 top coats of matt black. Some deburing beforehand would have helped the final look as well. I always underestimate how much all these details show up after painting.

Finished cage

Bags

For bags, I decided on Cube ACID PACK PRO 3 (which are 3 liter bags). Even though I bought these, this was not the super easy part. Going into this project my thought was that it will be super easy to find fitting bags. But I had to do quite some digging to find something I liked. 3 liters per site are plenty for my setup, since I just want to spread some weight forward. I have seen these cages used with 5 liter bags, which worked fine as well. The straps do not line up perfectly with the cage, but there is enough wiggle room to make it work.

Cage with bag

Final thoughts

It was a fun project and I will hopefully get to enjoy these cages for a long time. Without having done most of the things required to tackle this project, it took me quite some time to do. But I learned a lot and will surely go into my next CAD/metal/fabrication project with more of a plan!

I hope someone can get something out of my post. This checklist should help if you consider doing a similar project (maybe even any DIY project at all)

Don't do this if you

  • want to save money
  • need some cages quickly

Do this if you

  • enjoy making stuff!
 

Ich habe leider keine humoristische Kleinanzeigencommunity gefunden, denke aber hier passt es themathisch ja auch.

 
 

cross-posted from: https://feddit.org/post/10697822

In der ersten Hälfte geht es darum, wie das Miniaturwunderland Modelle modernerer Autos herstellt und mit welchen Herausforderungen das kommt. Dann kommt ein kurzer Abschnitt zur generellen Energie-und Verkehrswende in Knuffingen.

Ab 24:25 geht es dann darum, weswegen ich das Video hier verlinkt habe: die öffentliche Meinung zu E-Autos in Deutschland und Typische Lügen dazu.

Ab 32:18 gibts dann noch einen Teil mit Eckart von Hirschhausen zur Klimakrise generell und der Auseinandersetzung im Miniaturwunderland mit dieser.

 

In der ersten Hälfte geht es darum, wie das Miniaturwunderland Modelle modernerer Autos herstellt und mit welchen Herausforderungen das kommt. Dann kommt ein kurzer Abschnitt zur generellen Energie-und Verkehrswende in Knuffingen.

Ab 24:25 geht es dann darum, weswegen ich das Video hier verlinkt habe: die öffentliche Meinung zu E-Autos in Deutschland und Typische Lügen dazu.

Ab 32:18 gibts dann noch einen Teil mit Eckart von Hirschhausen zur Klimakrise generell und der Auseinandersetzung im Miniaturwunderland mit dieser.

7
submitted 7 months ago* (last edited 7 months ago) by needanke@feddit.org to c/mediatheque@feddit.org
 

Eine überraschend frische Serie die mentale Gesundheit, Sexuelle Orientierung, patrichale Strukturen, Rasissmus und Cholerische Chefs in einer spannenden story Verpackt. Mich haben besonders die komplexen Charaktere und die aus deren Persönlichkeiten und natürlich wirkenden äußeren Umständen resultierenden Interaktionen beeindruckt.

Ofizielle (meiner meinung nach schwache) Beschreibung:

Die wilden Achtziger machen auch vor den Redaktionsräumen des australischen Nachrichtenredaktion "News at Six" nicht halt. Während sich die Weltereignisse überschlagen, versucht die erfahrene Nachrichtensprecherin Helen Norville, ihre Stellung als Starmoderatorin zu verteidigen. Auf der Jagd nach den spektakulärsten Nachrichten lernt sie Jungreporter Dale kennen.

view more: next ›