

It’s closed source. So it’s impossible to verify Facebook doesn’t have you pkey and goes MitM.
They say they don’t, but you can only take their word for it.
It’s closed source. So it’s impossible to verify Facebook doesn’t have you pkey and goes MitM.
They say they don’t, but you can only take their word for it.
You still can. But I see how trying to shoehorn collaboration into a purely text-file-based platform would be a huge PITA.
Horses for courses.
If your codebase is closed source there’s no risk of that happening, if it’s open source there’s nothing you can do about it.
Either way there’s no use worrying.
Someone clearly had a fun photo shoot. 😄
People want to travel to the USA still? Bizarre.
The reason I compare them to autocomplete is that they’re token predictors, just like autocomplete.
They take your prompt and predict the first word of the answer. Then they take the result and predict the next word. Repeat until a minimum length is reached and the answer seems complete. Yes, they’re a tad smarter than autocorrect, but they understand just as little of the text they produce. The text will be mostly grammatically correct, but they don’t understand it. Much like a compiler can tell you if your code is syntactically correct, but can’t judge the logic.
Getting an explanation is one thing, getting a complete solution is another. Even if you then verify with a more suited tool. It’s still not your solution and you didn’t fully understand it.
Or, and hear me out on this, you could actually learn and understand it yourself! You know? The thing you go to university for?
What would you say if, say, it came to light that an engineer had outsourced the statical analysis of a bridge to some half baked autocomplete? I’d lose any trust in that bridge and respect for that engineer and would hope they’re stripped of their title and held personally responsible.
These things currently are worse than useless, by sometimes being right. It gives people the wrong impression that you can actually rely on them.
Edit: just came across this MIT study regarding the cognitive impact of using LLMs: https://arxiv.org/abs/2506.08872
Not sure where you take the N from. Plus it’s needlessly derogatory. How about FMAGA instead? Because F MAGA!
Wouldn’t that be a great use case for a QR-code?
Didn’t weigh them before drying because they were still on the branches. But post drying the flowers were very brittle and in the swamp bags the hygrometer initially showed <30% humidity. It eventually crept up to ~55% over the two week cure, thanks to the Boveda packs.
Well, Wile E. Coyote, no? Road Runner just runs away.
42,39g dry. Think I overdried it a little.
Yes, most times gamescope isn’t required. Thing is, sometimes it is and not having the option is an inconvenience in the best case and makes games unplayable in the worst case.
My partner is currently running PopOS. They somehow managed to combine the chronically outdated Ubuntu packages with a rather counterintuitive UI.
Updates frequently fail, commonly used packages like gamescope aren’t available, overall wouldn’t recommend.
Had it on my Fairphone 4 for a while, but was put off by the very iOS look-and-feel. Ditched it on favour of Lineage.
I get that. But that doesn’t mean you can demand someone else investing a lot of time in what is commonly unpaid work.
Well, you’re free to patch support for your ancient OS back in. But you can’t expect someone else to do it for free.
Can the more experienced growers maybe weigh in? Definitely getting autumn colours, pistils are ~50% darkened, trichomes seem to be mostly milky, as best I can tell. I don’t have a microscope to check. Some trichs over purple leaves look more amber. Harvest already?
Not necessarily and also not how I understood the post. It’s certainly an option and an ergonomic one at that. So it’s not unthinkable they go that route.
But you could also offer a choice of backend when creating a new graph. Text-based allows you to sync you files between devices, e.g. via source control, and offer asynchronous collaboration this way, while the DB-based approach forfeits source control and opts to keep its data consistent through simultaneous edits from multiple clients itself.
But managing that consistency takes quite considerable effort, as we’re witnessing, for no clear advantage, just a tradeoff. And I at least think it would be a shame to let the work already gone into the development of the text backend go to waste. I think the devs might share that opinion.