You can't make an LLM only reference the data it's summarising. Everything an LLM outputs is a collage of text and patterns from its original training data, and it's choosing whatever piece of that data seems most likely given the existing text in its context window. If there's not a huge corpus of training data, it won't have a model of English and won't know how to summarise text, and even restricting the training data to medical notes will stop mean it's potentially going to hallucinate something from someone else's medical notes that's commonly associated with things in the current patient's notes, or it's going to potentially leave out something from the current patient's notes that's very rare or totally absent from its training data.
Sandwich cake is already a term that means the same thing as layer cake. The classic combination of two layers of Victoria sponge with strawberry jam and whipped cream in between is called a Victoria Sandwich. Anyone arguing that a layer cake isn't a sandwich is just illiterate, not a defender of semantic specificity.
AGPL is a full-on FOSS licence with strong copyleft requirements, not a measly open-source licence like Apache, which could be pivoted to proprietary at a moment's notice. We're communicating through an AGPL-licensed system right now as it's what Lemmy's licensed as. If they were going for a corporate-friendly licence, AGPL is the last thing they'd choose as it forces you to share source code with even more people than the regular GPL does.
You might find that your hardware exposes 3.2 features via Vulkan and that if you configure your machine to use Zink rather than native GL, you can get a 3.2 context.
Wikipedia management shouldn't be under that pressure. There's no profit motive to enshittify or replace human contributions. They're funded by donations from users, so their top priority should be giving users what they want, not attracting bubble-chasing venture capital.
Like a real powertool, if you unscrew the safety features because you feel they're getting in your way, they no longer provide safety. Having the guard from a chainsaw in your back pocket does nothing to protect you from the chainsaw you're holding.
I guess this is slightly less disturbing than the previous approach to cyborg cockroaches where their antennae were snipped and enamelled wire was inserted into the stubs to directly stimulate their nerves.
It could still be to cover up war crimes that the BBC team hadn't got quite close enough to discover yet, but the IDF were concerned that they might have if not scared away. It could just be for opsec, but them having been competent at stopping the BBC seeing whatever it was they were hiding isn't proof that the thing being hidden was benign.
Variations of this meme get posted every week, but I've never experienced it, despite having had tens of grub updates murder-suicide the Windows boot loader and grub itself across five or six different machines. Thankfully, it's pretty easy to rebuild a Windows boot partition, but the frequency that I'm hit with this problem is one of the major reasons I avoid using Linux. Eventually I'm going to have to switch, but that's driven mainly by Windows getting worse rather than any of the pain points I've had when trying to switch full time in the past having been fixed.
You don't necessarily want to just ask for volunteers as that's a great way to summon exactly the kind of people you don't want to put in charge of online communities. The best way is usually to notice people who are already part of the community and consistently make positive contributions, then ask for their help. If none of those people want to, though, you're stuck.
I think for something like this, you'd rent cloud servers as you'd expect the number of concurrent users to change over time and ideally would be able to spin up more capacity when you need it without having to have those machines available all the time. You still need some kind of system that decides when to order more capacity with enough warning that it's actually available (you can tell AWS you want a VM immediately, but it still takes a couple of minutes to transfer your data onto it and boot it up, which is longer than people want to sit in a loading screen) and decides which servers to assign to which users.
There's a strong argument that the server architecture needed to be better at launch, but then the game sold more than an order of magnitude better than it was expected to, so no one would have noticed that it scaled badly had the player count been in line with their design and testing.
Even accounting for disasters, coal power puts more radionuclides into the environment into the environment than nuclear for the same amount of energy. If you dig lots of stuff up and spew it all into the air, the small amount of radioactive material that's in coal and the rocks around it is much bigger than the tiny amounts of nuclear fuel a nuclear power plant gets through. If the only concern is radiation that persists on geological timescales, then swapping all coal for nuclear is an improvement. Other things that release surprising amounts of radiation include making things out of granite (it's usually got uranium in) and importing bananas and Brazil nuts.
If it's changes on a geological timescale in general, then as fossil fuels form on a geological timescale (the clue's in the name), digging them up is going to take unfathomable amounts of time to undo. It won't even be as quick as the first time around, as most coal formed before ligninase evolved, so trees fell over and didn't rot and usually became coal, buy they're biodegradable now so need specific fossilisation-friendly conditions to become coal.
That problem isn't unique to nuclear. It wouldn't be newsworthy if a worn-out wind turbine blade was incinerated unsafely, and that's something that happens routinely and is much more damaging than dumping this quantity (about a beer crate full) of depleted uranium. The reason we're hearing about this incident is that the nuclear industry is held to a much higher standard than anything else in the energy sector. There are good reasons for that - the worst case scenario for a single fuckup is much worse - but a lot of it is just fear-mongering by fossil fuel companies who needed to lie to make something seem more dangerous than what they do, even before climate change was recognised.
Nuclear is so much better than fossil fuels that even if we cut every corner and accepted a Chernobyl-scale indicent would happen a couple of times a year, it'd still be preferable over the gradual phase out of fossil fuels and resulting climate crisis we're on track for.
The kind of spoiler tag you used is the kind that doesn't work on every Lemmy app. Fortunately, that's not a problem, as I've already seen Time Trap, and despite forgetting its name, do sometimes think about it.
Something else worth noting is that instance admins do a lot more moderation than Reddit admins did, so the burden on the moderators for individual communities can be smaller. lemmy.ml in particular has a reputation for having admins who actively intervene a lot.
AnyOldName3 @ AnyOldName3 @lemmy.world Posts 1Comments 352Joined 2 yr. ago
You can't make an LLM only reference the data it's summarising. Everything an LLM outputs is a collage of text and patterns from its original training data, and it's choosing whatever piece of that data seems most likely given the existing text in its context window. If there's not a huge corpus of training data, it won't have a model of English and won't know how to summarise text, and even restricting the training data to medical notes will stop mean it's potentially going to hallucinate something from someone else's medical notes that's commonly associated with things in the current patient's notes, or it's going to potentially leave out something from the current patient's notes that's very rare or totally absent from its training data.