Looks like they disabled the comments lol
If you don’t like the titular hit 'i glued my balls to my butthole, again" , then fuck you
Aside from global concerns about labor displacement, somewhere like Kenya seems silly for robot staff usage in 2024
You would expect to see this in places where labor is incredibly expensive, such that the cost of running robots (even if they are actually useful) competitively beats the cost of human labor
It’s after closing time. So leave.
American here: worked jobs from digging ditches to writing software… This only happens if you let it.
If it’s offered and it’s free, check the times with the boss, if a reasonable reschedule (like "I’d really like you with me in a meeting at 10, can you take the 11 appt? Sure.) , Do it. Else, keep the appt and have your employment docs on hand for reference as needed.
That’s pretty fuckin cool
They could just look 5+ years back, gauge the average rate of comment editing (with falloff for time since comment creation), take that as a standard, and pass that as a filter over any modern edits. You would literally have to edit slower than the average bear, especially accounting for older comments.
I’ve been saying this from the start:
Any basic level competency backend team has change history on comments. Crack whatever jokes you like about Reddit but they at least have “basic level competency”
It’s trivial for them to build some filters to detect mass changes and just fuckin roll them back.
If you post ANYTHING on ANY server you don’t own: it’s out there. For ever.
https://media1.tenor.com/m/OUzcn0WrxFEAAAAC/sandlot-forever.gif
It is done.
I’ve seen increasing usage of “allowlist/denylist” .
In this example it is a config value that the software expects to be present, I’m guessing based on the screenshot it is to be added to the homeserver.yaml
Why’s that a mistake? Not everything is built for a novice
If the documentation is sufficient for the intended audience, it’s good enough.
What’s confusing here? Break down the steps and parts of the command
SHOW ME WHAT YOU GOT
Great points.
For isolated projects in the past I’ve had great success storing things in postgres,. (generally large documents that are relationally tied to other more traditional PG data, in a db driven project) Just saying size and recall have been pretty happy.
As you say the other features are distinguishing.
Thoughts on this vs postgres blob storage? I know they aren’t the same thing.
The content about the reasons for different smiles is cool. And the highlighting of the training data influencing things is also good stuff.
But as far as realistic image generation based on culturally relatable smiling sounds like a skill issue. You can’t just generate images about specific times or settings or people with “defaults”. You have to specify your prompt.