Lewis Pullman, Bill Pullman, Josh Gad, Rick Moranis, Daphne Zuniga and Josh Greenbaum chat with ET's Nischelle Turner all about their highly anticipated new ...
I wonder what they're going to do without Joan Rivers and John Candy. Regardless, I really hope this is as good as the first one. It's so hard to do that with sequels.
Content warning: bitching about openai/chatgpt/ai/llms
chatgpt isn't "just a tool". at best it's the worst social media website in the world; you only chat with one guy, yet everything is a click away from being publicly available to everyone. at worst it's the best way to rot your brain and lose all of your skills; you start to depend on the misinformation that it feeds you and you're stuck needing to pay Sam Altman $20 a month.
i just wanted the industry to give me a search engine that was slightly less ass, y'all. fuck me.
Content warning: bitching about openai/chatgpt/ai/llms
Couldn't agree more, tbqh. It's kind of frustrating because the concept of a natural language computing interface like that and the technology behind how it works is legitimately interesting, but in practice how it's been implemented and how it's been marketed to users is just straight up vomit inducing.
We are at or very very near peak AI bubble. I am pretty confident that it will pop no later than Q2 2027, and probably sooner. But, as always, itâs completely impossible to predict these timings exactly, so Iâm not gonna risk any money on it. âThe market can remain irrational longer than you can remain solventâ, as they say.
Thanks to Monarch for partnering with me! Start your free trial and get 50% off your first year of total money clarity using my link https://monarchmoney.yt....
It's been weird to watch online commentary on this -- lots of "this is because permits are getting cancelled due to public outcry" and "this is all expected - companies are putting out more plans than required in this race", etc, all to say that AI isn't a bubble.
Definitely worth understanding if youâre using âAIâ for pretty much any reason. The companies that make it all understand that it is generally bad and have all written as much into their TOS. You can not rely on this software. https://youtu.be/uMDwmg7i2_4
Have you ever actually read the TOS for any of the AI tools you use, well probably not but there's some fun little excerpts that you can find==========Suppor...
sometimes u just become a bee ya knowtldr-- been working full time as a teacher after i graduated college ~ 2 years ago & have been working on my own indie p...
Not here to catch anything today. He has seen people feed the fish before, tossing little bits into the water. So he thought⌠why not share something better? That something he enjoys a lot!
Piece for Red Panda Bean. Traditional. Markers + Colored pencils.
we care for your privacy and choice, that's why there is a button to accept all cookies, and a button to open a sub menu where you can uncheck each of the 6 partner cookies, then you click the "save my preferences" button that opens a pop-up, and can click the "confirm my choices" button that's just to the right of "accept all cookies anyway"
I could not find my multimeter. Looked everywhere I could think of. Eventually, gave up and sat back down at my desk⌠and immediately found it. It was right next to my left elbow.
With a piece of paper on top of it.
The 3.6V battery I wanted to test in fact read about 2mV, so yes, replacement ordered.
Attached: 1 image
It's frustrating that the UK is trying to follow in the USA's political footstepsâŚ
#USPol
#UKPol
(Not sure who to credit for the artwork.)
I just tried to tell my dad what I'd achieved today, and had one of those "first create the universe" moments. I pretty much ended up describing (simplified) the whole technical history of my hosting network, what BGP, OSPF and VRRP do and how they fit together, how my router setup has evolved over time, and quite a few sidetracks too, to explain that what I'd done today was to complete a script that sets up Linux "virtual MAC interfaces" for the VRRP implementation I'm hoping to soon migrate to, because the vrrp keyword built into the ifupdown2 package I've been using doesn't do a few things quite exactly the way I need and it's easier to reimplement than to fix.
Explaining all that took probably an hour and left my throat really dry and with the realisation of just how *much* technical stuff I have to look after to run a whole hosting ISP single-handedly. I really *really* ought to actually try to get some more customers in - pretty much all the customers I have, I got by accident.
FYI I do server colocation in London, UK, plus most of the other stuff a hoster does: domains and DNS, email (well, not really at the moment, email's one of the more horrible things to host and the current setup is very old and crusty and needs modernising before I'll be happy taking on email customers), web hosting, virtual servers, etc. My main selling points are service and reliability - if cost is your main factor in choosing a host, you might want to try elsewhere. ;) If I haven't scared you off and you're interested, feel free to ask.
So, VRRP on the new router works fine on one VLAN, but fails on another VLAN. The configs seem identical, but on one, I turn on VRRP and its announcement Rx counter correctly starts ticking up and it remains in backup mode. On the other VLAN the Rx counter stays at zero, it transitions to active mode, and I can see announcements from both old and new routers in tcpdump. Checked FRR config, "ip -d address ls" and "ip -d link ls", /proc/sys/net/ipv?/ interface-specific stuff... can't see anything wrong. My last resorts, I think, are (a) capture VRRP traffic, analyse, verify checksums, see if I can find any reason at all that the new VRRP is ignoring announcements from the old VRRP, and (b) forget it for now, install a newer FRR/VRRP on the second new router (which is not yet in service so I can do that without worry), and try getting VRRP on that one to work when I get to that stage. Frustrated.
Looks like FRR's VRRP implementation has a lot of weirdnesses. It works by having you configure a macvlan interface attached to the actual interface VRRP is running on. The macvlan interface has the VRRP virtual router MAC address on it, plus the virtual IP addresses. VRRPd doesn't touch the addresses or interfaces, other than to set or remove "protodown on" on the macvlan interface.
Weirdnesses discovered so far:
1. Packets that should transit the router running VRRP which are addressed to a virtual IP address on a VRRP macvlan interface in backup mode get received by that router rather than being routed on and ending up at the active VRRP router. Not a huge problem, but can be annoyingly misleading when, e.g., tracerouting.
2. Packets addressed to the VRRP subnet get routed out the macvlan interface even in backup mode unless you turn on "ignore_routes_with_linkdown" for the interface in sysctl. Again, not a huge problem (it's nice to have ingress and egress from a given subnet on the same router for statistics purposes but it's not a deal-breaker if not). Solved, but just the first indication that there may be any number of other related weirdnesses.
3. The one that's currently bugging me. Since the macvlan interface is still "up" (albeit also "protodown on") while VRRP is in the backup state, so that VRRPd can listen for VRRP announcements from other routers, the kernel still receives packets addressed to the VRRP virtual MAC address. Unfortunately, it also still *forwards* those packets. That's not actually a problem as long as your switches correctly learn where the VRRP MAC address lives and send packets only to that interface, but if (as mine have) they decide they are confused as they've seen that MAC address in two different places, throw up their little hands and say "I have no idea, let's just flood frames for this MAC address" you'll get all VRRP routers in a subnet (active and backup) all receiving all packets going out the default router, and therefore all routing those packets out. So your outbound bandwidth suddenly doubles if you have two VRRP routers, or triples or more if you have three or more. Ouch.
4. Can't remember if there was anything else. But⌠it feels like there are more that won't come to mind as I write this up.
I've been pondering how to fix number 3, and so far I have a tiny shell script which has to run continuously all the time on every VRRP macvlan interface (and if it breaks, the world ends), which uses "ip monitor" to see when "protodown on" is turned on or off. It would then do something to fix things while in backup state â potentially remove/re-add IP addresses, or possibly turn off/on forwarding for the interface using the kernel sysctl interface, or maybe move the interface between groups so that firewall rules can block forwarding when it's in backup state, or⌠something else. It feels like I shouldn't need to do this kind of thing just to get the protocol to work properly, though. I wonder if there's a better VRRP implementation I should be using instead, or if I should be reporting bugs to FRR (but their VRRPd has had very few changes in years, which suggests they either consider it works properly or it's disused. And I lack the energy to work out how to report bugs, and to write them up properly.)
Hmm, wow. A small language model that fits in an 8-bit Atari! But browsing through the training data (a single 13KB text file) I'm getting serious ELIZA vibes - seeing such a stripped-down language description is a good reminder just how non-intelligent these language models really are.
đšď¸ Is this the smallest language model in the world? I just managed to squeeze real artificial intelligence into 30 kilobytes, running on a 1979 Atari 800. A fully generative, deterministic langu...
Is this kind of stuff of use or interest to anyone? Any of it likely to be worth archiving in some way, or are all these sort of things typically on a publically accessible archive already? (This is a random selection of some of the disks my aunt has been dumping on me as she's spring cleaning stuff my late uncle used to carefully store away - there are more.)
Iâd say any piece of software like this is absolutely with archiving. Not only for historical interest but also for historical information as a snapshot in time.
Definitely worth checking archive org and other such places to see if thereâs already a copy up on there, and getting things up if not.
If theyâre otherwise getting thrown out, Iâd certainly be interested in some of those!
there may also be different versions of the "same disc" which can also be worth archiving, IA might have a copy that's newer/older/different region, but perhaps not the exact one
Anyone interested in old old monitors? They'd need collecting from East Hampshire (or I could bring 'em to ConFuzzled). I can't vouch for their electrical condition as they've been in a shed for many years and might not even work (I haven't tested), and also I (probably inexpertly) repaired the 15" Iiyama many years ago when a solder joint on the PCB on the back of the tube cracked and the red channel stopped working, but I'm guessing a retrocomputing enthusiast might be able to get them safe and working again.
Happy birthday @pamiiruq.bsky.social , hope you have a good day today! (ft. @fibrekitty too) đ¸ - @bartonfox.bsky.social #Fursuit #furry #mascot #cosplay
