61–70 of 92 posts
Earlier quoted context omitted.
Nobody took away your choice. You just need to implement/find SSL for that older device.
I think you've got something mixed up here, it's not that more effort is required by either party, it's just NOT to block port 80, and NOT write explicit redirect rules, and poof, stuff works.
> For most typewriters, restoration is only a matter of taking the time to do it. There’s no complex skills or tools involved. Even the most difficult operations could be learned alone, by simple trial and error. What. Let's say an internal piece failed because of mechanical stress caused by lack of lubrication or a jammed foreign object. How do you figure out "by simple trial and error" which piece failed, why it fa…
> no mention of why you'd want to do this In the introduction, OP says: "Well, given how we use the resources of our planet, the question is not if we could or not. We need to do it, no matter what." I tend to believe he is right about that.
> For most typewriters, restoration is only a matter of taking the time to do it. There’s no complex skills or tools involved. Even the most difficult operations could be learned alone, by simple trial and error. What. Let's say an internal piece failed because of mechanical stress caused by lack of lubrication or a jammed foreign object. How do you figure out "by simple trial and error" which piece failed, why it fa…
> Why it failed. Out of scope. You just want to get it working again and don't care if you have to replace the same piece in another 5 years. Maybe that is not a "proper" repair, but you can do it yourself. > which piece failed Everything is large enough and mechanical failures are obvious enough that you see what is broken (maybe that part that is literally broken into pieces).
As for being "obvious", I don't understand that sentiment. A broken piece pretty much by definition does not look the way it should, so unless you know the exact design of every piece by heart before starting the repair you're not going to automatically know what it's supposed to look like, in the general case.
- Building a laptop (and not a desktop/workstation computer, or a blade/server hardware) makes the task much more difficult than it has to be.
- Even modern Debian is supposed to run on Pentium 1, so that's hardware from 25+ years ago (I suspect the main memory would be a bottleneck though). But now that Moore's law doesn't seem to apply anymore, and unless there will be some unexpected breakthroughs, at least the same 25 years seem fairly easy.
- As anecdata, I've built a computer about a decade ago (had no hardware issues at all since), and another one a couple years ago -- and their specifications are very similar.
- I guess replacement parts may be more of an issue: with hardware interfaces changing, it becomes quite a bit harder to find older ones, just as with any appliances.
- As for interfaces for talking to the outside world, I think so far they change (with breaking compatibility) slower than internal ones, though it can be an issue too. Maybe can be mitigated with analog interfaces where applicable, open hardware and GPIO pins for future hacking, and general attempts to keep compatibility. And adapters, of course.
Earlier quoted context omitted.
I think you've got something mixed up here, it's not that more effort is required by either party, it's just NOT to block port 80, and NOT write explicit redirect rules, and poof, stuff works.
Some other party then has the extra effort of security, privacy, etc. support for those using 80 with modern computers and browsers...
Earlier quoted context omitted.
> Why it failed. Out of scope. You just want to get it working again and don't care if you have to replace the same piece in another 5 years. Maybe that is not a "proper" repair, but you can do it yourself. > which piece failed Everything is large enough and mechanical failures are obvious enough that you see what is broken (maybe that part that is literally broken into pieces).
If you don't understand why it failed, you might do more damage with your repair, or you might have to replace it again in a week, rather than five years. As for being "obvious", I don't understand that sentiment. A broken piece pretty much by definition does not look the way it should, so unless you know the exact design of every piece by heart before starting the repair you're not going to automatically know what i…
Or it might not and we are talking about a very concrete case. The point is that everything is "large", low-tech and lots of stuff works the same. So replacement parts are fairly easy to get and easy to install. No soldering, no dexterity, no "exact design of every piece" required.
Compare that to fixing a smartphone, where you might need special tools to even open the device.
Earlier quoted context omitted.
There is a reason to read Wikipedia via https: ISP can otherwise inject ads or even change the page. This has actually happened.
That's not a good reason to take away my choice, and rob me of the opportunity to access this information on an older device if I wanted to.
It’s just like all the other kinds of safety measures we expect, such as seat belts, regulations w.r.t. food safety, fire protection, standards for tool safety, etc.
Nothing of that is needed, until you need it (I’ve never needed seat belts or airbags, for example, but can understand society requiring them)
If the industry hadn’t forced the world to https, I think governments would have.
Right now, I don’t see how a general purpose computer could last 50 years. The article refers to it being modular, but you’d have to replace so many parts… would it still be the same computer?
I also own a Core 2 Quad with maxed ram (8gb) that is about 15 years old and it can handle a modern Linux distro quite well. I've added USB 3.0, card readers and I bought a cheap AMD workstation GPU and stuff works ok. If the hardware doesn't fail it probably be okay for another 10 years. If I ran a BSD on there it would last longer.
What normally causes me to upgrade machines are new games and/or heavy weight software stacks and IDEs that eat ram and CPU time.
Earlier quoted context omitted.
I got to say you're spot on. Keeping things working is no challenge looks at his commodores . Keeping them relevant is more of a challenge, this is one reason I hate to see people forcing redirects to HTTPS, it's just great and dandy that modern browsers suggest this to users (as long as they don't force), but for vast vast amounts of information, in the free world, you shouldn't force people into always-encrypted. T…
There is one reason I can think of for encrypting websites, it tells you the information is coming from where you expect and not an interloper. I agree its worth thinking about about serviceability and longevity but I can't help feeling like it would be like worrying about keeping a PDP 11 running for fifty years.
And it’s already 52 years old, today. Seems like solved problem.
Earlier quoted context omitted.
I got to say you're spot on. Keeping things working is no challenge looks at his commodores . Keeping them relevant is more of a challenge, this is one reason I hate to see people forcing redirects to HTTPS, it's just great and dandy that modern browsers suggest this to users (as long as they don't force), but for vast vast amounts of information, in the free world, you shouldn't force people into always-encrypted. T…
There is one reason I can think of for encrypting websites, it tells you the information is coming from where you expect and not an interloper. I agree its worth thinking about about serviceability and longevity but I can't help feeling like it would be like worrying about keeping a PDP 11 running for fifty years.
This would be an example of progressive enhancement, which has fallen out of favor.