If you follow HN over the course of 24 hours, you’ll see at least 3 major waves. I tend to have an odd sleep schedule, so I’m always amused when I’m online to see which group is currently active.
There is an Asian/Australian wave, followed by Europe, and the North America. Some of the best times are when the waves start to mix (ex: early morning NYC time, you’ll get the Europe and NA groups interacting).
You’ll see different types of stories posted. Similar enough to where it all makes sense to be on HN, but it seems like a different flavor. But the comments are where I start to see more differences. You can get new takes on the same article if you see the comments from different times of the day.
This doesn’t take into account the total numbers of people active from each region, which I suspect is skewed towards more users the US coasts. But, it does, I think, speak to how US centric HN is. I think it serves the needs each of the waves in a distinct way.
I’d love to actually see this analyzed more. This is just the take from someone who has been awake at enough hours to observe some trends.
If Tailscale is installed on your router, then any client will also be able to connect to Tailscale networks.
Fo example, if you have a default route back to your home network on the router, any client will also connect through that tunnel back through your home. This assumes you are using your travel router to connect your laptop as opposed to say the hotel wifi. (In this scenario, your travel router is connected to both the hotel wifi as an uplink and Tailscale.)
You only need separate users if you want to restrict certain features (devices, apps, etc.) to only certain users (i.e., it's more of a business thing). My wife's machines all use my username because... she lives with me; if she wanted suddenly to learn networking and computers and hack all our stuff, she could do it anyway since she has physical access.
So pretty much anyone you would trust on your LAN can be trusted with your Tailscale user. You can just log yourself into Tailscale on the kids' devices and then use the admin console to make those devices' logins never expire. They can use all the features, but they don't know your authentication method and thus can't get admin access themselves. About the only situation in which the typical home user would need multiple accounts would be if someone was physically away from you and had a new device they needed to connect to your tailnet (their term for your collection of devices, services, etc.) but you didn't want to share your password with them. If they're physically near you, you just authenticate their device and hand it back to them.
I’m not worried about the LLM getting offended if I don’t write complete sentences. I’m worried about not getting good results back. I haven’t tested this, and so I could be wrong, but I think a better formed/grammatically correct prompt may result in a better output. I want to say the LLM will understand what I want better, but it has no understanding per se, just a predictive response. Knowing this, I want to get the best response back. That’s why I try to have complete sentences and good (ish) grammar. When I start writing rushed commands back, I feel like I’m getting rushed responses back.
I also tell the LLM “thank you, this looks great” when the code is working well. I’m not expressing my gratitude… I’m reinforcing to the model that this was a good response in a way it was trained to see as success. We don’t have good external mechanisms to give reviews to an LLM that isn’t based on language.
Like most of the LLM space, these are just vibes, but it makes me feel better. But it has nothing to do with thinking the LLM is a person.
I’ve had some luck with giving the LLM an overview of what I want the final version to do, but then asking it to perform smaller chunks. This is how I’d approach it myself — I know where I’m trying to go, and will implement smaller chunks at a time. I’ll also sometimes ask it to skip certain functionality - leaving a placeholder and saying we’ll get back to it later.
Or it’s a small enough company without an IT department.
Think of an SMB where you might know you need to do something (like connect a new store location to the server in your main location’s closet), but don’t know how or can’t afford to hire an IT person full time. This is probably the main market for this. Then once you get more buy in, experience, and reputation, this VPN could stay to see larger clients. That’s at least how I’d expect to see this grow.
It’s all just loading data into the context/conversation. Sometimes as part of the chat response the LLM will request for the client do something - read a file, call a tool, etc. The results of which end up back in the context as well.
I think that's part of the pitch here... swapping out Minio for Garage. Both scale a lot more than for just local development, but local dev certainly seems like a good use-case here.
Same. I know I have a couple someplace in a bin. That and another embedded card from the era, but I think it had something like a DIMM footprint. I thought it was also Dallas semi, but I can’t find it or remember what it is though…
I remember thinking that some of the tracking features (temperature) of the button would be helpful in some situations. But the ring was the crazy model. Between these and smart cards, authentication was starting to look futuristic. I even remember getting a smart card reader from my credit card company. They thought it would make for more secure web transactions.
I’ve still seen some iButtons in the wild in odd places. Most recently, I saw them tracking car keys at dealerships. The last car I test drove had a key attached to a fob with an iButton. I was more excited by the iButton tracker than the car.
But I thought of it as an example of how long lasting some design decisions can really be. I’m sure someone designed this system 20-25 years ago and it is still in service today. I’m sure today it would be NFC. But now I’m thinking about what the iButton of 2050 will look like.
I wonder how robust the solder joints are for castellated boards. I’d still imagine that to be a weak point vibration-wise. Definitely easier to automate, but would it be that much more robust?
Thinking about those CM sockets and I think the answer is yes - a castellated solder joint (is that the right term?) would be stronger. But other sockets might be more robust than the CM0.
There is an Asian/Australian wave, followed by Europe, and the North America. Some of the best times are when the waves start to mix (ex: early morning NYC time, you’ll get the Europe and NA groups interacting).
You’ll see different types of stories posted. Similar enough to where it all makes sense to be on HN, but it seems like a different flavor. But the comments are where I start to see more differences. You can get new takes on the same article if you see the comments from different times of the day.
This doesn’t take into account the total numbers of people active from each region, which I suspect is skewed towards more users the US coasts. But, it does, I think, speak to how US centric HN is. I think it serves the needs each of the waves in a distinct way.
I’d love to actually see this analyzed more. This is just the take from someone who has been awake at enough hours to observe some trends.
reply