Off-and-on trying out an account over at @tal@oleo.cafe due to scraping bots bogging down lemmy.today to the point of near-unusability.
I hope that Micron, SK Hynix, and Samsung don't hit any hiccups with their memory chip production buildouts.
You can see that the occupant in that one is clearly outside the triangle formed by the three wheels.
shakes head sadly
Just tell your passengers to shift their mass to the area of the vehicle in the triangle formed by the remaining three wheels.
I'd just stick screens on one's windows and maybe use DEET if you're really at the height of mosquito season in a bad area.
Like, this has a DSLR camera, a GPU constantly churning away, a laser...
https://www.lgbtqnation.com/2017/01/ibm-introduces-new-rainbow-logo-support-lgbtq-community/
IBM introduces new rainbow logo in support of the LGBTQ community
January 9, 2017, 5:00 pm EST
unexplained shit that's happened to you.
I came into existence.
"Why" is a pretty open question.
https://en.wikipedia.org/wiki/Why_is_there_anything_at_all%3F
"Why is there anything at all?" or "Why is there something rather than nothing?" is a question about the reason for basic existence which has been raised or commented on by a range of philosophers and physicists, including Gottfried Wilhelm Leibniz,[3] Ludwig Wittgenstein,[4] and Martin Heidegger,[5] who called it "the fundamental question of metaphysics".[6][7][8]
They're charging for premium features, not for basic access to the service.
searches
All of the letter openers I've used have been relatively blunt.
For the US, my experience:
- Way more smoking (which people also mentioned last time this was asked). Cigarette butts everywhere.
- Government was more dignified.
- Houses were smaller.
- Cars were smaller. And more colorful -- the last decade or so has really favored colors between white and black. Oh, and a wider variety of interior upholstery.
- Telecommunications were much more expensive.
- People smashed trees into pulp, bleached it, rolled it into sheets, and then put their messages on them.
- Libraries were more important.
- Store selection was way, way more limited, and if you lived somewhere rural, even more so. Amazon and similar let you have anything delivered anywhere today.
- I kinda miss some of the styles, like 1980s denim jackets, but there were also things that I disliked compared to today. Oh, yoga pants were not typically worn in public. Or flannel pajamas pants --- that seems to be a thing where I am now. If you were female, you were a lot more likely to be wearing a skirt or dress than today. Clothing was more formal, in general.
- On that note, the necktie was still a thing. It's pretty dead today.
- Carpeting in houses was more popular.
- People spent a lot more time staring at the TV, which I think is a lot more mindless than Internet use today. Oh, and you had far fewer channels than you do on a TV today.
- Lighting was yellower, because of the use of incandescents. Nighttime in houses was darker and yellower.
- The logistics of communication and navigation were more complicated without GPS-equipped smartphones. One typically kept maps in the car. Asking for directions was a thing. You might even have a car compass. Finding payphones was a thing.
- Much less omnipresent surveillance, like the security cameras and automated license plate readers of today.
- If you had a computer, it was much more likely not to be connected to a network, so software couldn't rely on network access. It couldn't phone home or transmit information about you.
- Video games were much less mainstream, especially before the 1990s. Not many adults playing them.
- Way more handwriting done. The fancy pen was more of a thing.
- Flashlights and penlights were more prominent, since everyone wasn't carrying a smartphone that could act as a flashlight.
- I'd say that probably the majority of people wore a wristwatch.
- Computers were much more expensive than they are today, and became obsolete far faster. The rate of computation speed increased such that about every 18 months, computers ran software twice as fast as before. This has a huge impact on other industries, since that constantly made new things viable.
- Lots of devices with disposable batteries.
- Dedicated portable music players with far less battery life were much more common. You carried around much less music.
- Cars, IMHO, looked more interesting. Certainly more varied. Mileage was worse.
- You certainly didn't omit spare tires in cars. Much harder to get roadside assistance.
- I'd say that woodworking skills were more common. A lot of guys could and would do basic projects.
- People spent more time outdoors.
- People were thinner.
- Motor noise was more obnoxious along roads. Cars are quieter today.
- Airline security was way less obnoxious. Didn't have all the security screening stuff that 9/11 spawned. Air travel was more expensive.
- More casual conversations with strangers that one sat near, I'd say. Smartphones severely degraded the custom of chatting with strangers.
- Magazines and newspapers were much more common.
I'm banned in these two communities (some sort of automod script went off at some point for some reason on some comment and banned me from a bunch of places on the sh.itjust.works instance, and the admin never responded when I asked about it), so I'm not there, but some places that won't have people getting upset over people talking about it:
- !localllama@sh.itjust.works. This is probably your best bet for text.
- !imageai@sh.itjust.works. These guys deal with image generation.
Also:
- !stable_diffusion@lemmy.dbzer0.com. As with Reddit's /r/stablediffusion, these guys don't really deal specifically with just the Stable Diffusion image diffusion model --- have broader technical discussion and stuff.
You can search communities on all Threadiverse instances at:
https://lemmyverse.net/communities
If you decide to start a new community somewhere else yourself, let me know. I'd be interested in joining.
and will have huge context menus you could talk to them for hours and they will remember every single detail and be able to pull it up instantly
So, the problem is that the way this is generally handled today --- at least via local LLM stuff that I've looked at, haven't looked at the bleeding edge at cloud providers, and they probably don't talk about it --- is via one of two semi-incompatible approaches.
Large context window
This requires a model trained for it and enough memory to work with it I use a Framework Desktop 128GB in significant part to have enough VRAM to run queries that use this approach with mid-sized models (70b) and a 128k token window, which is larger than most people working on typical GPUs can do.
The way this works is that each time you send something to the LLM, your client also resubmits the entire conversation history (or, IIRC, depending upon the API used, does something functionally comparable that only sends the most-recent message). You probably can't afford to recompute the entire conversation history, but you can cache it using K-V caching.
The problem here is that this requires video memory that scales linearly with the size of all prior conversation. It also, IME, has processing time that scales up linearly as well. You can only have a conversation get so big before you're burning a lot of compute time.
Retrieval-Augmented Generation (RAG)
https://aws.amazon.com/what-is/retrieval-augmented-generation/
Here, you have some primitive, not-very-smart software that looks at the text in your message, looks through the conversation history (and potentially other sources of data) and then, in the background, builds a prompt that contains text that it thinks might be relevant. For example, if you mention the name "death" and "Superman" in your message, maybe it looks to see if there is any past text that also contains "death" and "Superman", and inserts that into the prompt.
This has some advantages. For one, it can scale up to enormous amounts of information. And it doesn't need to just look at your conversation history as a source of data, but it can also query other databases and the like.
This also has a number of limitations.
First, the software doing that retrieval is not very "smart". It isn't always fantastic at determining what is relevant.
Second, the way current LLMs work --- at least insofar as I've looked --- is to try to generate text that would follow subsequent to the prompt by predicting tokens that are probable based on what it's seen.
But...what it's getting, in the background, in the prompt is a bunch of discombobulated snippets of text. And my experience is that if you want to generate text in some style, like that of a novel, seeing a bunch of snippets isn't great for that, since that doesn't look much like a novel. It may be that there are techniques for dealing with that.
Third, this also doesn't work well with the K-V cache approach, since each prompt that actually goes to the LLM can look completely different from the previous one, so you'll constantly be getting cache misses and having to recompute stuff.
My own bet is that what we're going to wind up doing is having some form of new data structure --- possibly a neural net, but might look somewhat different from the multilayer model used by the LLM to store static memories, IMHO. I wouldn't be terribly surprised if this is something more like a directed acyclic graph, and I'd guess that it'll also do something akin to how red-black tree rotations see constant accesses restructure the data structure to bring more-frequently-used nodes closer to each other (though I don't personally think that it'll just be doing specifically a rotation. I'm just providing an example of another datastructure that dynamically restructures itself based on use). That'll be a mutable memory, to act like the "context" that human minds have when they're working on a problem. It'll provide properties that today human minds have and LLMs don't, like where repeatedly doing something makes you better at it. Just as we mentally associate things that we've experienced in the past together, so too will future AIs.
It may also be that something like this replaces in part the multilayer neural nets that are LLMs today. My own personal bet is that ultimately, a lot of the way advanced AIs work will not be LLM-based; LLMs just don't have properties that mirror how human minds in a number of ways. Maybe advanced AIs will incorporate an LLM as a component.
But --- and I haven't been following the research closely here --- I don't think that that's currently something being worked on, or at least not widely.
But I do think that, yes, advanced AIs are going to need the ability to do something like that as they head towards approach human capabilities.
I don't think that I've ever seen something like that occur, but can you hit DEL at boot, go into the "boot options" or similar in the BIOS and try manually selecting the USB flash drive as your boot device?
Can you try a different USB flash drive, on the assumption that it's something about the device?
This is probably a Hegseth thing, not originating with Trump. A while back, Hegesth went on some rant about how high command was too fat.
Huh. I had no idea that one would use an impact driver on Torx screws.
I kind of mentally associate Torx with (delicate) personal electronics and associate impact drivers with big, heavy pieces of hardware with rusty bolts.
But Lisp is case-insensitive
looks bemused
I don't do that much Lisp, mostly use it for emacs, but I'm pretty sure that it's not.
opens emacs
(setq foo 1) (print foo) 1OK. So far so good.
(setq foo 1) (print FOO) Debugger entered--Lisp error: (void-variable FOO) (print FOO) (progn (print FOO)) eval((progn (print FOO)) t) elisp--eval-last-sexp(nil) #f(compiled-function () #<bytecode 0xf6febdfec01a>)() eval-last-sexp(nil) funcall-interactively(eval-last-sexp nil) command-execute(eval-last-sexp)Elisp sure doesn't look to be case-insensitive. Maybe he meant some specific variant? Common Lisp?
$ sudo apt install sbclApparently sbcl's REPL doesn't support readline.
$ sudo apt install rlwrap $ rlwrap sbclHuh. Looks like with readline, I also get cursor flashing to do paren matching, kinda like emacs can do. I had no idea that readline could do that. Apparently Common Lisp doesn't do
setqeither.more experimentation
* (let ((foo 1)) (print FOO)) 1 1Huh. So, yeah, I guess that Common Lisp is case-insensitive. That is a bit wild. I guess I do remember vaguely seeing old Lisp stuff with keywords in all-caps.
Is Scheme?
$ sudo apt install guile-3.0Apparently the guile REPL doesn't support readline either. God.
$ rlwrap guileAnd it looks like "print" is "display" in Scheme-land.
scheme@(guile-user)> (let ((foo 1)) (display foo)) 1Okay, so that's the syntax. Case-insensitive?
scheme@(guile-user)> (let ((foo 1)) (display FOO)) ;;; <stdin>:2:24: warning: possibly unbound variable `FOO' ice-9/boot-9.scm:1676:22: In procedure raise-exception: Unbound variable: FOONope.
I kinda feel like there are Lisps that the author could have used if they wanted Lisp and case-sensitivity, if that was the major irritation.
People who want to prevent their devices from being swept into botnets should install security updates in a timely manner and resist the urge to continue using software or devices that no longer receive them.
That doesn't really seem likely to happen on its own. I'm pretty sure that most IoT devices phone home and upgrade themselves (which, frankly, I'd be maybe more-concerned about as a vector than a lack of updates, since anyone can buy a defunct IoT maker and thus get control of all those devices, or penetrate the IoT maker's network) and I imagine that most people have no idea when a device has last been updated.
You can maybe have some sort of network protocol where devices can report their last update. That'd maybe permit for auditing that, if you had a device that would tell a user about an outdated device, which isn't really the case today. Also kind of hard to tell an end user what a device at IP address X is. If they're on the same Ethernet segment, maybe could try to identify it by OUI on the Ethernet address, I guess, but that's not going to give you a convenient helpful-to-most-end-users product ID for a lot of devices. So if your audit program sees a device on the network that doesn't implement the "last updated" protocol, it may have a hard time identifying it to you in human terms.
If you're willing to wait until 2028 when memory prices are expected to drop, and if you're willing to get new hardware if memory prices drop, I'd give real consideration to waiting until then. There'll also probably be better hardware and better models then.
If you can constrain yourself to MoE-based LLMs, they'll generally deal better from a performance standpoint with not entirely fitting in VRAM better than non-MoE LLMs, as experts may not get loaded into VRAM at all.
Yeah, but he's got a point. The GOG new game library is much smaller than on Steam.