chiisana

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.

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.

Shipping address appears to be US only. Oh well.

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.

In the same train of thought, BMW and Tesla execs need to find courage and remove turn signals.

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.

In no uncertain terms:

1. Hypixel.net has Cloudflare DNS for their domain.
2. For their website, it has orange cloud enabled to proxy traffic through CF’s global CDN and DDOS protection service.
3. 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
4. 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.
5. 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.

Years of experience tells me I should generally avoid Apple’s first generation product. First generation Apple Watch, first generation iPhone, etc. left a lot to be desired. I wouldn’t want to try the first generation Apple modem in a daily driver iPhone.

It was never to your definition of free, so you were never going to be using it in the first place. Don’t need to say goodbye when you were never here.