avidamoeba

How's the noise? Tolerable?

Keep telling people about Mastodon. Don't push them. Just explain that this is a result of BlueSky being VC funded and more will follow just like it did with Twitter, Facebook and so on. Add that Mastodon is open source run by multiple non-profits around the world so if one fails, the rest would pickup the slack. Conclude with - if they want to stop having to uproot their network every so often, Mastodon is their best bet for microblogging.

How many times have we watched this movie? At this point these ceasefire negotiations feel more like hasbara than actual attempts to stop the killing.

Whatever the repo is setup with.

How do these compare to the DF64s?

Good thing the Bloc will never allow Carney to sell out our Dairy

How're they gonna stop him if he decides to to that? The cons would back him. Sure he would probably lose the next election if he does that, but is there an actual mechanism for BQ to block such a move if he doesn't care to win again?

Much more important than the enjoyable culture is the material aspect - how much work each developer has to do. Nice vibes help delay burnout but rarely eliminate it. Or they let it happen with a smile on the face.

Pay the developers instead, so they can reduce hours worked elsewhere, if you can. Or contribute code, if you can. This isn't aimed at you personally, but anyone reading. I can't contribute code but I can pay so I do that.

This is going great. Absolutely fabulous.

The vast majority of those jobs were part-time, the agency said.

Important detail.

Nice. So this model is perfectly usable by lower end x86 machines.

I discovered that the Android app shows results a bit slower than the web. The request doesn't reach Immich during the majority of the wait. I'm not sure why. When searching from the web app, the request is received by Immich immediately.

You could absolutely do that and be fucked too. However the point of the pattern I suggested isn't to replace the return with an assignment. That is, the point isn't to do the exact same implementation and then do result = something before returning it. Instead it's to use the initialized result var to directly store your result throughout the function, at every place where you manipulate it. So in this case my suggestion is to not have psize at all. Instead start with int result = -1; and return result; and do all the things you do to psize except on result. Then there's a higher chance you will return the right value. Not a guarantee. I'm not at all implying that "if they only did this one thing, they wouldn't have fucked up like this, so stupid" I'm merely suggesting a style that can decrease the probability of this type of error, in my experience. I'm teaching my team to write in defensive ways so they can feel some confidence in what they wrote, even if they slept 2 hours the night before, and also understand it after another bad night. Cause that ends up happening, life happens and like OpenZFS we also can't afford serious bugs in what we do.

Taco