• 1 Post
  • 61 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle











  • I put the wire down my shirt or coat. Doesn’t get in the way at all.

    Never have to charge- that is so important to me because I definitely don’t want anything else to have to charge. I hate smartwatches for the same reason (and because I don’t like wearing watches.)

    And lastly, port doesn’t have to be omitted. Xiamoi or whoever had a razor thin phone with a jack- no issues with space. Also, companies had IP68 or whatever ratings with headphone jacks before.

    You’re not gonna convince us. We know what we like and we know there is zero reason that the jack can’t be put in. It wouldn’t preclude people like yourself from using BT all the same but would afford us a simple time-worn and battle tested way of listening to music the way we like that clearly has upsides to only having BT available.








  • 0e2475ba-882a-4f61-8938-2642ca80193b WARN     │  ┝━ 🚧 [warn]: WARNING: index "displayname" Equality was not found. YOU MUST REINDEX YOUR DATABASE
    0e2475ba-882a-4f61-8938-2642ca80193b WARN     │  ┝━ 🚧 [warn]: WARNING: index "name_history" Equality was not found. YOU MUST REINDEX YOUR DATABASE
    0e2475ba-882a-4f61-8938-2642ca80193b WARN     │  ┝━ 🚧 [warn]: WARNING: index "jws_es256_private_key" Equality was not found. YOU MUST REINDEX YOUR DATABASE
    

    I had to drop it for a few days. I got that at some point though. It’s all brand new so I wouldn’t know why. Seems a bit rough around the edges so far. I’ll try to reindex and attempt again. I really want this to be the product I use since it’s a nice AIO solution but we’ll see.

    Edit:

    [~]$ podman run --rm -i -t -v kanidm:/data \
        kanidm/server:latest /sbin/kanidmd reindex -c /data/server.toml
    error: unrecognized subcommand 'reindex'
    

    Phew boy. Straight from the docs. Same with the vacuum command.

    Looks like the docs need updated to specify the command is kanidm database reindex -c /data/server.toml

    And further upon trying to login…

    300e55b7-e30a-42a5-ac3e-ec0e69285605 INFO     handle_request [ 188µs | 0.00% / 100.00% ]
    300e55b7-e30a-42a5-ac3e-ec0e69285605 INFO     ┕━ request [ 188µs | 72.94% / 100.00% ] method: GET | uri: /v1/auth/valid | version: HTTP/1.1
    300e55b7-e30a-42a5-ac3e-ec0e69285605 INFO        ┝━ handle_auth_valid [ 50.8µs | 25.54% / 27.06% ]
    300e55b7-e30a-42a5-ac3e-ec0e69285605 INFO          ┝━ validate_client_auth_info_to_ident [ 2.85µs | 1.51% ]
    300e55b7-e30a-42a5-ac3e-ec0e69285605 WARN            ┕━ 🚧 [warn]: No client certificate or bearer tokens were supplied
    300e55b7-e30a-42a5-ac3e-ec0e69285605 ERROR         ┕━ 🚨 [error]: Invalid identity: NotAuthenticated | event_tag_id: 1
    300e55b7-e30a-42a5-ac3e-ec0e69285605 WARN        ┕━ 🚧 [warn]:  | latency: 204.504µs | status_code: 401 | kopid: "300e55b7-e30a-42a5-ac3e-ec0e69285605" | msg: "client error"
    

    I think I’m gonna have to just nuke it and start fresh but yeah, this is not a great first impression at all.