- abestic9 parentI was expecting a mention of all the repositories that are popping up primarily developed by AI prompts. The UI and the READMEs are full of the typical patterns (emojis, gradient/glow CSS effects, em-dashes, etc) and seem just-put-together-enough to slap up an r/selfhosted post and gain a few dozen stars on GitHub.
- In short: land covenants. In HOAs you will see titles containing terms about the property being subject to restrictions voted for/applied by the association. If you continually decline to adhere to the restrictions, you can be legally compelled to sell and move on.
Note: I'm using phrasing local to me, I expect there may be minor differences but the same gist.
- Both/neither, I would suggest. Offloading manufacturing reduces risk, but requires you to have better oversight in other areas before actually shipping.
From what I've seen, businesses will often hire someone with specific experience dealing with Chinese manufacturers in their specific vertical, for example PCBs/electronics, tooling like injection molds, or textiles.
- I'm not a fan of the manufacturer dubbing these "Magic Balls", when "sensor spheres" or even "Neuron" from the original article linked in this thread, is more than sufficient. We're not trying to appeal to home consumers here. Maybe it's for politicians...
Cool project though, transmission costs account for a large proportion of energy delivery.
- As good as Steam might be, it’s still required for the games you purchased to run, and that doesn’t align with some people. You own your games on Steam as much as you own your music on Spotify. So priacy is still alive and well, and a lot of the arguments I see for it is stripping DRM and ownership.
I prefer Steam over other platforms because multiplayer is effortless, with a friend or at a LAN party that means means more time actually playing the game. But if it’s not on Steam or not everyone can afford it, we’re probably playing a cracked, portable copy.
- Up to a certain point it's not much of an issue, but I had to re-read several sentences and I'm fairly capable of following written text. It's also an accessibility thing, screen-readers and dyslexics might have trouble interpreting the text.
I support bringing it up when it's frequent enough to cause frustration. Putting some effort once into the writing - typing correction occurs almost effortlessly on almost any device these days - benefits every reader.
- I was about to respond to a comment that got flagged about this. A lot of this opinion I suspect stems from platforms like TikTok where non-psychiatrists are able to perpetuate the stereotype that ADHD is a "quirky", surface-level trait that makes for a neat partner/employee/friend.
Your experience is a common one, and ADHD is both under-diagnosed and badly represented, making for a toxic perception which some of the crowd here doesn't seem immune to.
- If you're having trouble reading the diagrams, several barrier types are available in this New Zealand Transport Agency publication [1]. The F-shape barrier is detailed on page 10.
[1] https://arco.co.nz/wp-content/uploads/2017/12/m23-road-safet...
- Outside of the timezone-agnostic advantages, .beats are about what I'd expect single notable tasks to resolve to and seem to be a great notation for that purpose. Retrieving an item I know the rough location of might take 1 .beat, disinfecting a kitchen countertop might take 2 .beats, resolving a P1 service outage I know the cause of might take 4 .beats to correct, verify and push into production. That ease is what makes it a viable replacement for me.
So after widespread adoption it could be used effectively as second nature and improve communication without the wasted thought cycles it takes to consider seconds/minutes, just to end up supplying poor ETAs. For example, from, "just a second," really meaning anywhere between 5 and 300 seconds, to a moment being hopefully less than 15 minutes, instead we hear, "need to grab something from the garage, back in... 2 beats," to mean around 3 minutes and parallelise our own movements appropriately.
With that edge, I'm optimistic that .beats wouldn't become arbitrary language after a few decades, that its use would be more thoughtful, but I'm ignorant to the psychology.
If decimal time of any description were to catch on, all systems should be updated, right down to the instruments requiring microsecond accuracy. Similarly, while we propose reformed timekeeping, can we decimalise the calendar year? https://en.wikipedia.org/wiki/Calendar_reform
- Project Farm, a YouTube creator that faces various brands of tools off against each other, has purchased an early (but apparently production) release of one of these. In a recent comment on one of his videos he’s stated he aims to have a video of ratcheting screwdrivers including this one out in a few days.
I’m optimistic given the attention to detail portrayed in this video, and the fact that Linus displays a passion for quality workmanship in his reviews of other products.
- I'm optimistic that Apple is working on most of these issues (especially catch-all) right now and this is just representative of their new offering.
Like many things I've seen from Apple it will take a release cycle or two (of 1-2 years per cycle) to bring in this arguably basic functionality - as is tradition we'll groan about other issues being held back in favour of fancy new features.
I have no doubt they intend to fully compete with the email services from Google and Microsoft. Following on from last year we should see VPs taking us through the updates to iCloud+ alongside device launches as it expands into a fundamental service offering.
- Awesome concept, I heavily factored in the different widths and glyph variations (like O, 0). I was surprised to get Overpass Mono, I would've never considered it otherwise. A couple of suggestions:
- Allow editing and preserve the user's content or at least the ability to select a language. CSS doesn't display a lot of the nuances present in other languages, and some people simply use monospaced for other kinds of writing. Though I appreciate this may add a requirement for a syntax formatting library.
- Add Iosevka and Cascadia Code fonts, among probably many others that will be suggested here. Better yet, add the ability for a user to set a custom font source URL and change it to a blind test!
- Themes, pretty self explanatory.
- I'm not impressed by STH's moves, I'm not sure if it's a recent development or I've failed to notice it before. Their articles are sometimes uncanny to read, as if they were written by someone who doesn't speak English natively (which is fine), but never proofread.
Add to that their nasty advertising methods, I'm really disappointed because STH has for a long time been one of my favourite resources for enterprise-grade and home lab gear. I've made considerations in commercial decisions using their reviews, but I don't feel I can trust their integrity at this point.
- I would expect to see ad/tracker blocking technology to advance as the users encounter more invasive types of tracking. But what if the server requires that information as part of a request to serve content in it's response?
This will always be a cat and mouse issue, and unfortunately right now most of the authority is on the server side. The data-driven web that TimBL envisions is just not profitable enough and content has to be heavily intertwined with distractions and trackers to monetise us cattle. See RSS.
- Cool concept with channels, but it took me over 7.5 seconds to load the front page with half of it before any visible content, and almost 2.5 seconds to load About. Also, hot-linking images is bad practice, it may be worth just getting rid of the images while you build out functionality. Are you planning on releasing the source for it?
- I can see why anti-rape self-defense is a popular rhetoric as gun ownership has indeed prevented crimes, and not being raped is a very good thing. Unfortunately, it's also used often as an emotional sales tactic, causing people who shouldn't be in possession of a gun to be in possession of one, resulting in unnecessary injury and death.
Coupled with the fact that even if you arm every single person capable with a gun, there's still going to be crime, you have to consider a balance. Some countries are doing very well without them.
- Google called me wanting to confirm my business address and asked me a bunch of personal details, as well as a 6 digit code that was going to be sent to my number (the one they called me on?). I refused and told them to give me a number to call them back on and they said they didn't have that facility. I then asked if they could email me or point me to a form and they said they could only do it on that same call.
After 10 minutes in a verification tug-of-war, the rep escalated me to someone who did provide proof they were actually Google (using a field I updated in my account). All up it took 15 minutes and felt very fraudulent until they finally gave me some helpful context.
- If you're experiencing volume corruption, or can no longer guarantee the integrity of your system, at that point does it matter that it's open source? At what point do you cut the investigation, reinstall and get on with your day?
Proprietary OSes are less flexible but not to the extreme you're describing. In both instances there are faults you can recover from, and faults where you can't.
Edit, to rephrase my question as not rhetorical: I'm genuinely interested in knowing if troubleshooting this type of fault is a common occurrence to people outside of OS/kernel programming, as I lack experience with it.
- Apple's next 72 hours, if not when this popped up years ago, will define their deliberate, public choice for how they're going to handle this.
I can imagine their forum censorship getting enough visibility to see more scrapers archiving posts for useful facts and truths. How sad does that sound for the company that thought different?
It escapes me why the execs are playing like this during such a defining moment in their company history. R2R cannot come soon enough.
- The mirror was precisely polished "to spec" with custom-built equipment that was assembled incorrectly. They correctly saw the distortion issue on the ground with the conventional kit, but rejected the result as erroneous because it tested fine with the "better" testing equipment.
https://en.wikipedia.org/wiki/Hubble_Space_Telescope#Origin_...