chaospatterns

joined 2 years ago
[–] chaospatterns@lemmy.world 2 points 2 days ago

After I read this, I thought it would be really cool to try to make this myself. But then I realized I'm barely able to get a simple circuit working much less one that involves complex RF signalling.

[–] chaospatterns@lemmy.world 12 points 2 days ago (3 children)

Yeah this isn't even human readable even when it's in YAML. What am I going to do? Read the floats and understand that the person looked left?

[–] chaospatterns@lemmy.world 5 points 3 days ago

The point seems to be able to handle a UPS failure

[–] chaospatterns@lemmy.world 2 points 6 days ago

WiFi is on all three bands. It's not so much what's newer vs older. Newer devices tend to support 2.4, 5, and 6 and switch between them based on quality of signal and support by the WiFi network. Higher frequencies like 5 and 6GHz are generally better because there's less interference.

Cheaper devices tend to only support 2.4GHz

[–] chaospatterns@lemmy.world 0 points 6 days ago* (last edited 6 days ago)

Yes, but from a societal perspective, theres value in making cuts in a lot of different places.

Maybe you can do a meatless Monday, and somebody else will go vegan. Tell the people in private jets to stop flying private, but the family that's going to another culture and learning and maybe becoming better has benefits.

[–] chaospatterns@lemmy.world 3 points 1 week ago (1 children)

Fascinating. Just based on your comment and nothing else, sounds like it could be something like a CPU Enclave like Intel SGX. Basically a remote client can validate that an application runs in a secure part of a remote cloud computer. The stated goal of SGX is that you only have to trust Intel and if you trust Intel and say run program X in the enclave, then only that part of the CPU can access the data, not the applications running in the non-secure enclave.

Now that brushes over some things like you still need to trust the client and IIRC in a WhatsApp situation, you don't really know what enclave does, but the communications between the enclave and the host OS are heavily restricted. LLMs also require lots of CPU and are usually run on GPUs, so not sure how that works yet.

[–] chaospatterns@lemmy.world 3 points 2 weeks ago

It wasn't as crazy as the SLU one, but it always had a bunch of people in it which is what surprised me about this news.

[–] chaospatterns@lemmy.world 5 points 2 weeks ago

Not great news for me. This marks two grocery stores that were convenient to me that are now closed in the area.

[–] chaospatterns@lemmy.world 6 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

I think #1 is suggesting to move the neutral over to another hot phase and change the outlet to a 240v nema 6/three prong (I think) with two hots and a ground instead of the 4 prong.

The 240v at the same amps gives you higher watts so faster charging without an expensive new conductor. I'm

49
submitted 3 weeks ago* (last edited 3 weeks ago) by chaospatterns@lemmy.world to c/homeassistant@lemmy.world
[–] chaospatterns@lemmy.world 8 points 4 weeks ago (1 children)

Maybe that's intentional to keep you from wanting to stay there a long time and negotiate.

[–] chaospatterns@lemmy.world 17 points 1 month ago (1 children)

Sounds a lot like getting used to time zones. Just get used to it being 3pm there when it's 6pm here

[–] chaospatterns@lemmy.world 1 points 1 month ago

It makes some things hard and some things easier. For example, you can more easily defend against DoS attacks because there's just more targets.

But decentralized makes it easier for bot manipulation because you can hide your actions across multiple users on different instances and those instances can't easily identify bot signatures like IP addresses to ban many accounts.

 

I'm disappointed it's delay, but I'm eagerly awaiting the opening.

 

An update from GitHub: https://github.com/orgs/community/discussions/159123#discussioncomment-13148279

The rates are here: https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28

  • 60 req/hour for unauthenticated users
  • 5000 req/hour for authenticated - personal
  • 15000 req/hour for authenticated - enterprise org
 

Sound Transit has received the Federal Transit Administration’s Record of Decision for the West Seattle Link Extension project. This major milestone allows the project to advance into the next stage of development, the design phase.

The 4.1-mile West Seattle light rail extension was approved by voters in 2016 as part of ST3, and today’s approval of environmental work is the culmination of the planning phase that began in 2017. In that time, the project team has worked closely with the West Seattle community and agency partners to develop an alignment and future station locations that will serve more than 24,000 riders a day and cut travel times from Alaska Junction to Westlake in half, while enhancing station access and the transfer experience from buses to light rail.

With this record of decision, Sound Transit will advance engineering and design on the route and station locations selected by the Board in October 2024. At the same time, Sound Transit is continuing work to inform a financially sound West Seattle Link Extension project, including financial, programmatic and project-level measures to improve affordability.

view more: next ›