We didn’t stop trying to make faster, safer and more fuel efficient cars after Model T, even though it can get us from place A to place B just fine. We didn’t stop pushing for digital access to published content, even though we have physical libraries. Just because something satisfies a use case doesn’t mean we should stop advancing technology.
I’ve never been a Twitterific user, even back when everyone was on it. The UI never really made sense to me because it always felt lacking. But maybe that minimalistic approach is their entire schtick, and their former users that enjoyed their style would buy it right up.
On a similar thought, I think if Tapbots made a similar aggregator, I’d buy it in a heart beat.
Apple TV’s hardware is just so much more capable than other platforms that they’ve just been coasting along the last several generations of ”Apple TV 4K”. Our over 7 years old Gen 1 is still super capable and the only reason we picked up Gen 3 is so we can get the Thread radio in a centralized location. As an Apple user, I’m extremely glad there’s going to be a new competitor in the space, which will hopefully push Apple further along the innovation path.
Ask it for a second opinion on medical conditions.
Sounds insane but they are leaps and bounds better than blindly Googling and self prescribe every condition there is under the sun when the symptoms only vaguely match.
Once the LLM helps you narrow in on a couple of possible conditions based on the symptoms, then you can dig deeper into those specific ones, learn more about them, and have a slightly more informed conversation with your medical practitioner.
They’re not a replacement for your actual doctor, but they can help you learn and have better discussions with your actual doctor.
If you can serve content locally without tunnel (ie no CGNAT or port block by ISP), you can configure your server to respond only to cloudflare IP range and your intranet IP range; slap on the Cloudflare origin cert for your domain, and trust it for local traffic; enable orange cloud; and tada. Access from anywhere without VPN; externally encrypted between user <> cloudflare and cloudflare <> your service; internally encrypted between user <> service; and only internally, or someone via cloudflare can access it. You can still put the zero trust SSO on your subdomain so Cloudflare authenticates all users before proxying the actual request.
It is pretty clear that you have less of an inclination against Seagate than my experience dictates me to. Stats can be twisted to tell anything, and my twist on what I’m seeing tells me to steer away from Seagate; your interpretation can most certainly differ.
AFR is a percentage, 1 drive from a pool of 10 means 10%, 5 drives from 100 means 5%; so with regards to your point that they don’t have much WD drives, if they don’t have much WD, then each fail is even more detrimental on the chart, therefore making the data even more impactful. The data also showed the average across all manufactures and you can see clearly Seagate being consistently above the average quarter over quarter. The failure rate is annualized, so age of drive is also factored into the consideration.
When there’s a clear trend of higher failure rate represented as a percentage, I’m not going to volunteer my data, NAS or otherwise, as tribute to brand loyalty from a manufacture that’s gone downhill from the decades past.
Way back when SSD were prohibitively expensive for poor student me way back when, they came up with Momentus XT; I don’t know if they were the first hybrid HDD/SSD, but it was my first foray into flash storage. I had the earlier version with controller such that should the flash memory dies, I’d still have access to the HDD.
It, was, glorious…
I hear you. The brand is really not what we remembered them to be.
WD has been treating me well, but the most recent batch had been hgst he10 from server part deals from a couple years back so I can’t comment on the more recent drives.
Just don’t buy Seagate. Their drives consistently have the highest annualized failure rate on Backblaze reports ( https://www.backblaze.com/blog/wp-content/uploads/2024/05/6-AFR-by-Manufacturer.png ), and is consistent with my experience in small anecdotal sample of roughly 30 drives. This results in a ripple effect where the failed drive adds more work to the other drives (array rebuild after replacement), thereby increasing their risk of failing, too.
Deepseek referred here seems to be v3, not r1. While the linked article didn’t seem to have info on parameter size, fact that they state it is sparse MoE architecture should suggest it is capable to run pretty quick (compared to other models of similar parameter space), so that’s cool.
8B parameter tag is the distilled llama 3.1 model, which should be great for general writing. 7B is distilled qwen 2.5 math, and 14B is distilled qwen 2.5 (general purpose but good at coding). They have the entire table called out on their huggingface page, which is handy to know which one to use for specific purposes.
The full model is 671B and unfortunately not going to work on most consumer hardwares, so it is still tethered to the cloud for most people.
Also, it being a made in China model, there are some degree of censorship mandated. So depending on use case, this may be a point of consideration, too.
Overall, it’s super cool to see something at this level to be generally available, especially with all the technical details out in the open. Hopefully we’ll see more models with this level of capability become available so there are even more choices and competition.
More than once I’ve heard the jokingly saying that ‘everything causes cancer in the state of California’ (regardless if they bore the warning label or not). I think while the intention may be good, the equivalent of notification fatigue is at play here and might not be delivering intended benefit/value.
I wonder if it’s more because they’re hitting capacity limits as result of physical limitations of memory on package design — physical distance resulting in potentially unbalanced performance due to some memory simply doesn’t have physical space that could deliver consistent performance, thus limiting capacity as an idea that crossed my mind.
So less so of a “it’ll be more performant” thing, but “this was great but we have to back paddle because we need more memory than the space could permit” kind of thing?
Yeah. We came from a time of incandescent light bulbs taking 60W per bulb with fixtures needing 2-3 bulbs. Turning those off regularly mattered. The obsession people have with turning their modern electronics off in the name of power savings is silly if not outright insane.
Electronics components do not like to have power states change frequently. Turning devices on and off frequently will decrease lifespan of device. Sure, you are saving money on your electricity bill, but at some point, the savings and environmental impacts are outweighed by the cost of the device/parts and the impact during manufacturing.
Also, don’t forget phantom draws from the power supplier is a real thing, which will most likely exceed your 5 zeros threshold. So that microwave oven, and laundry dryer? Don’t forget to unplug those after each use.
The amount of confidently incorrect responses is exactly what one could expect from Lemmy.
First: TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process, but more on this later.
Second: Minecraft and website are both using TCP. TCP is part of layer 4, transport; whereas HTTP(S) / Minecraft are part of layer 7, application. If you really want to, you could cram HTTP(S) over UDP (technically, QUIC/HTTP3 does this), and if you absolutely want to, with updates to the protocol itself, and some server client edits you can cram Minecraft over UDP, too. People need to brush up on their OSI layers before making bold claims.
Third: The web server and the Minecraft server are not running on the same machine. For something that scale, both services are served from a cluster focused only on what they’re serving.
Finally: Hypixel use reverse proxy to sit between the user and their actual server. Specifically, they are most likely using Cloudflare Spectrum to proxy their traffic. User request reaches a point of presence, a reverse proxy service is listening on the applicable ports (443/25565) + protocol (HTTPS/Minecraft), and then depending on traffic type, and rules, the request gets routed to the actual server behind the scenes. There are speculations of them no longer using Cloudflare, but I don’t believe this is the case. If you dig their mc.hypixel.net domain, you get a bunch of direct assigned IP addresses, but if you tried to trace it from multiple locations, you’d all end up going through Cloudflare infrastructure. It is highly likely that they’re still leaning on Cloudflare for this service, with a BYOIP arrangement to reduce risk of DDOS addressed towards them overflow to other customers.
For their website, it has orange cloud enabled to proxy traffic through CF’s global CDN and DDOS protection service.
For their Minecraft server, they advertise mc.hypixel.net, but also have a SRV record for _minecraft._tcp.hypixel.net set for 25565 on mc.hypixel.net
The mc.hypixel.net domain has CNAME record for mt.mc.production.hypixel.io. which is flattened to a bunch of their own direct assigned IP addresses.
Traceroute towards those direct assigned IP addresses goes through Cloudflare infrastructure but final destination is obscured, just like their website, to protect them from DDOS attacks.
Using Ollama to try a couple of models right now for an idea. I’ve tried to run Llama 3.2 and Qwen 2.5 3b, both of which fits my 3050 6G’s VRAM. I’ve also tried for fun to use Qwen 2.5 32b, which fits in my RAM (I’ve got 128G) but it was only able to reply a couple of tokens per second, thereby making it very much a non-interactive experience. Will need to explore the response time piece a bit further to see if there are ways I can lean on larger models with longer delays still.
chiisana @ chiisana @lemmy.chiisana.net Posts 4Comments 500Joined 2 yr. ago 
We didn’t stop trying to make faster, safer and more fuel efficient cars after Model T, even though it can get us from place A to place B just fine. We didn’t stop pushing for digital access to published content, even though we have physical libraries. Just because something satisfies a use case doesn’t mean we should stop advancing technology.