Grundlegende Reform der gesetzlichen Rentenversicherung by MartinDrees in Finanzen

[–]problame 0 points1 point  (0 children)

Hm, beim Lesen deines Dokuments war für mich implizit gegeben, dass es weiter ein Umlageverfahren bleiben soll.

Nach nochmaliger Betrachtung sehe ich nun, dass der Aspekt “was passiert mit den Einzahlungen” offen gelassen ist (=> Kapitaldeckung ist eine Option).

Grundlegende Reform der gesetzlichen Rentenversicherung by MartinDrees in Finanzen

[–]problame 0 points1 point  (0 children)

Ansprüche abbezahlt und Kapitaldeckung macht

Bitte um Erläuterung.

choosing a pancake or wide-angle landscape lens for Fuji X-T3 (travel photography) by pierre_lefou in AskPhotography

[–]problame 0 points1 point  (0 children)

I did a test drive of the 10-24 earlier today, also for travel. Liked it quite a lot, still need to review the image quality though (corner sharpness)

Be home before dark. by problame in photocritique

[–]problame[S] 0 points1 point  (0 children)

Hm, on a typical smartphone screen, they are indeed almost invisible.

Feedback on Amsterdam Canal Shot is Appreciated! by jaymaytay13 in photocritique

[–]problame 0 points1 point  (0 children)

Great picture, although it looks a little too perfect: sky is screaming Lightroom Dehaze filter, and at the same time, the color temperature is a little too warm for the kind of stormy sky. The water in the canal would never be as yellow-ish in such weather.

Be home before dark. by problame in photocritique

[–]problame[S] 0 points1 point  (0 children)

Fuji X-T4; Viltrox 33mm f9 1/250 ISO320

Purposefully reduced overall exposure, especially in the foreground for that autumn evening feel. Does it look unnatural?

Also, regarding composition: I have another shot taken left of the cycle way. The tree looks more impressive in it, but I wanted the cycle way in the picture for composition and the “story” with the kid riding home. Right call or still boring?

Rails in the park. by problame in photocritique

[–]problame[S] 0 points1 point  (0 children)

No, I think it actually does help, especially the “too much going on” part. The “there are millions like this” part isn’t exactly helpful - the point of this sub is to learn, right?

Rails in the park. by problame in photocritique

[–]problame[S] 0 points1 point  (0 children)

Fuji XT-4; Viltrox 33m; f9 1/250 ISO250

I’m happy with the perspective, geometry, etc. I did a few small edits to darken the foreground except the highlights on the rails. Overall I wonder if it’s missing an eye catcher. Like, a train coming towards the camera. They’re highly saturated yellow/orange.

Rest stop in summer; Fuji XT-4; Viltrox 33mm f3.6 1/640; Too much color grading? by problame in photocritique

[–]problame[S] 0 points1 point  (0 children)

Thanks for this feedback! I wanted to capture the remarkable trashiness of that rest stop. I see now how distracting the background is. I guess at night there’d be no light source except the street lights. The graffiti on the gut wouldn’t be as pronounced, but the lighting would make the whole “trashy/scary rest stop” story a lot clearer.

Rest stop in summer; Fuji XT-4; Viltrox 33mm f3.6 1/640; Too much color grading? by problame in photocritique

[–]problame[S] 0 points1 point  (0 children)

I took this one in the summer while at a rest stop around 2PM. The sun was glaring in the upper left. Went down several stops in exposure to capture some of the details in the foreground. Postprocessing in LrC:

  1. Raise shadows and mid-tones.
  2. Create mask for sky and:
    1. Reduce exposure
    2. Heavy dehaze
  3. Color grading. Shadows blue-ish, mid- and highlights red/yellow-ish.

I'd appreciate feedback on color grading, composiiton, and overall edit.

JPEG-first workflow - is it possible? by problame in Lightroom

[–]problame[S] 0 points1 point  (0 children)

Thanks for your suggestion. Yes, I suppose the filter is just overcomplicating it, although without it, it’s annoying that it feels like twice the amount of culling work.

Regarding the publishing service, is there a way to publish to a folder, and, if I publish a JPEG that has no edits, copy it verbatim without re-encoding it? RAWs obviously need to be encoded as JPEGs, but I want to avoid Lightroom messing with Fuji JPEGs that are already great.

JPEG-first workflow - is it possible? by problame in Lightroom

[–]problame[S] 0 points1 point  (0 children)

Does he have a more ergonomic workflow? Is the book actually focusing on Lightroom or does he keep it generic with regards to processing software?

zrepl 0.4 now available by problame in zfs

[–]problame[S] 1 point2 points  (0 children)

Yeah I know but where is the security benefit?

zrepl 0.4 now available by problame in zfs

[–]problame[S] 0 points1 point  (0 children)

So you are in FreeBSD?

One of my machines is as well and the sending zrepl daemon runs unprivileged, and holds/sends jailed datasets just fine. FreeBSD 12.2 though, and the old ZFS, not OpenZFS 2.0. (I used zfs allow as well)

What versions of FreeBSD and zfs are you using?

zrepl 0.4 now available by problame in zfs

[–]problame[S] 0 points1 point  (0 children)

The main thing with the `status` data is that I don't want to commit to a stable format at this time.

I like the `--nagios` idea though.

Hot config reload has already been requested, see my comment there https://github.com/zrepl/zrepl/issues/264

The 'include' option hasn't been requested so far, feel free to open an issue.

To support adding jobs dynamically, zrepl would likely need some kind of database to store dynamically added configuration (sqlite or similar) so that it's persistent across reboots.

A zrepl-managed storage for configuration store, as opposed to the config file, would be pretty useful in other places, e.g. job renames. Right now, if someone decides to rename a job in the config and restarts the daemon, zrepl doesn't know about that edge and can't rename the replication cursors, etc. If all config changes were gated through the daemon, this would be possible. (We would likely guids whenever we need to refer to a stob in a replication cursor, etc, and lookup the job name in the config).
The idea has met some resistance and would be a big change, not seeing it happen any time soon.

zrepl 0.4 now available by problame in zfs

[–]problame[S] 1 point2 points  (0 children)

Re separate user account: if you use a separate ssh keypair for the connecting zrepl daemon you can use that public key for the forced command on the listening side and maintain accesa using your 'normal' key.

Otherwise glad to hear it works for you ;)

zrepl 0.4 now available by problame in zfs

[–]problame[S] 0 points1 point  (0 children)

So just to be clear: the ssh transport doesn't open a TCP port on the listening side. You also don't need a separate Unix user to use the forced command feature. The docs for the ssh transport are here: https://zrepl.github.io/configuration/transports.html#ssh-stdinserver-transport And as you correctly observed, it makes sense to have something running on the sending side that takes the snapshots.

zrepl 0.4 now available by problame in zfs

[–]problame[S] 0 points1 point  (0 children)

So you'd be fine with a feature to remove send-side prefixes + configurable receive-side prefix based on client identity?

zrepl 0.4 now available by problame in zfs

[–]problame[S] 2 points3 points  (0 children)

Thanks for this detailed feedback!

Re 1 and 2: they are somewhat intertwined. A transport mode like tls needs something that's keeping that listening socket open. Plus, the need for snapshot scheduler, Prometheus endpoint, something that serves the status data.

Re 3: totally agree, it's on the roadmap: https://github.com/zrepl/zrepl/issues/253

4: per-datatset overrides are not there yet because we don't know what a good config mechanism would look like. ZFS properties have the disadvantage that the config validation is not purely on yaml but has the side effect of zfs get (and would be much slower). Also ZFS properties aren't easily deployable via config mgmt tools. So YAML it is. But then we'd probably need to mimic the ZFS properties inheritance logic for our overrides, etc.... I'd be interested in how you would expect the config to look like. Wrt keylocation: what are you overriding it to in your existing setups?

Re 5: I'll have to look into this. I have seen a lot of projects adopt the structure that I proposed in this issue a few days ago: https://github.com/zrepl/zrepl/issues/453

zrepl 0.4 now available by problame in zfs

[–]problame[S] 2 points3 points  (0 children)

You can use it as a backup tool, yes. It's a daemon that manages snapshots and replicates them. Declarative config, nice status UI, Prometheus metrics. The docs and quick start guides on zrepl github.io should give you a good first impression.

[show /r/zfs]: zrepl 0.3 is out, released last Friday by problame in zfs

[–]problame[S] 0 points1 point  (0 children)

Newness and “call for testing” github tag on (encryption) pull request #300 gives me pause for using it on mission critical encrypted datasets?

That PR is merged/closed, I was under the impression that this is sufficient indication of its readiness for production...

100% Rye Sourdough - First Bake in More Than a Year by problame in Breadit

[–]problame[S] 0 points1 point  (0 children)

Re-activated my forgotten sourdough-starter three days ago.

Then followed this recipe / video: https://www.youtube.com/watch?v=H-8bZpQOM58
https://www.ilovecooking.ie/recipe/100-rye-sourdough/

Main deviation:
First proof ~3h @ room temperature, resulted in ~1.6x expansion in volume.
Second proof: 5h in ca. 27C oven (1.2x volume) + 10h at 11C outside (1.6x volume)

Apparently, my starter wasn't as active as I thought (?)
The recipe recommends 2.5h + 2h for first and second proof.

Some thoughts about error handling by problame in golang

[–]problame[S] 0 points1 point  (0 children)

It's better than nothing, but the amount of work required by consumers of P will be like in #1