urushitan 漆たん

You’ve hit the nail on the head. What you’re describing isn’t just laziness — it’s a fundamental breakdown of trust in the modern workplace. Let’s delve into this.

Here’s the thing: when someone copy-pastes AI output without reading it, the document was never the deliverable — the verification was the deliverable. The prose isn’t load-bearing; the checking is. A document nobody read isn’t a document — it’s a liability with formatting.

And that’s the thing, isn’t it? Is the AI actually the problem here? No — the workflow is. This genuinely comes down to ownership:

• Trust erodes silently. Every unchecked paragraph is a small withdrawal from a shared account nobody audits — until the balance is zero.
• Verification is idempotent. Ten minutes of reading costs the same whether you do it once or a hundred times — but skipping it compounds.
• The failure isn’t technical — it’s cultural. No review, no judgment, no accountability.

This is exactly the kind of thing that starts as one bad research doc and scales — from a single email, to a team norm, to an entire organization quietly outsourcing its thinking. In today’s fast-paced world, the ability to say “I read this and I stand behind it” isn’t just a soft skill — it’s a superpower, and honestly? A testament to the rich tapestry of what human-AI collaboration could be.

Ultimately, your colleague didn’t fail to use AI correctly — they failed to be the human in the loop. The tool didn’t remove their judgment. They left it at the door.

I hope this helps! Would you like me to draft a one-page best-practices memo your team can circulate? 🚀

/s in case this isn’t blatantly obvious

reads the wikipedia article

considered overhyped, low quality, and unattractive

double checks to make sure I’m not on the cybertruck article

Probably reliable until the next “feature and experience update” where they move or remove the setting and default it back to allow for all users again and all the soulless advertisers cum their pants because their malware delivered impression counts just went up again

lol I imagine you have to just be like a meteorologist and ballpark it by squinting hard and nobody can say anything if you’re wrong

Not sure how, it works so well

Ahh, thanks!

Is it a private repo? I couldn’t see any other public repos about a desktop app that are active (there’s a kotlin one, also archived)

Looks like their desktop app is archived on github

https://github.com/Drop-OSS/drop-app

Wonder what happened

“So which one of your 30 houses do you spend the most time at? Is it one of the 5 in California?”

In many countries Ford and Tesla are on the top 10 lists. The Ford Puma is the number 1 selling vehicle in the UK right now. If you had said “American cars don’t have the majority of sales outside of America” you’d be right, but “Nobody buys them” certainly isn’t true.

It is identical. The only difference is one is OpenAI branded and they vibecoded software to make it control parts of the codex desktop app

Well considering that the “UEFI Shim’s” role is to sit in between a Microsoft owned certificate signing chain, it is certainly part of it’s primary role.

With Linux distributions supporting UEFI Secure Boot, the above-described Secure Boot mechanism built around Microsoft keys introduces some challenges. Every Linux distribution generates its own bootloader binaries, and each of them has a different hash. Getting every Linux bootloader signed directly by Microsoft would be slow, bureaucratic, and impractical (if not impossible) to maintain across all Linux distributions.

The solution to this problem is a shim: a small, minimal first-stage bootloader that Microsoft can vet and sign once, and which then creates a secondary trust anchor for the rest of the Linux distribution-specific boot stack – usually GRUB 2 and the Linux kernel. This trust anchor is another certificate, referred to as a vendor certificate (managed by the distribution vendor), added to the shim binary before it is signed by Microsoft.

E.g. it’s an AI built discord clone with a nearly identical interface, not a chat platform “with discord features”

oh wow lol that’s not just “discord features” that’s o.g. “linux is not unix” built by claude. thanks for the share

Without having gone on that discord, like most discords, it would be my guess that 80% of the purpose of it is for shitposting, custom emojis, and sharing gifs.

Ironically few if any self hosted chat platforms share that focus, so that’s likely part of the gap. It’s either irc (very light on features, no ui for administration/customization for those not wanting to use admin text commands), matrix (very heavy, focus on federation, also has many commands that are only through text, very light support for custom emoji or built in gifs), or the crippleware open source business oriented chat platforms like rocketchat, mattermost, or zulip.

Honestly zulip is probably best but then you get into the wonderful world of mobile push notifications, capped at 10 users or unlimited for “eligible communities” there

Also the IMDb app is almost certainly just a web view wrapper, as are the vast majority of apps today

https://futurism.com/

It’s the style their design director Tag Hartman-Simkins uses for a ton of their articles

Yeah I’ve thought about the question there of like is it acceptable then for those managing the instance to collect a percentage of transactions in the case where they provide payment management, arbitration, etc. Because if someone is a bad actor on Lemmy or mastadon you just ban them or the instance, but in the case of money changing hands that’s more difficult to administer

Many people who aren’t retail investors won’t even have a choice anyway. Their 401(k) will be tied up in speculative funds they don’t control. People’s retirements will shield the rich, all part of the plan

That means that he managed to keep the fine small enough that Samsung made significantly more money off the price fixing than they ever lost from the fine. Hasn’t changed

https://www.axios.com/google-facebook-fines-profits--134d3567-1052-4d9d-aa70-dc7c25ed4ebf.html