I don't understand that point. Why do e-bikes become better or more safe when you have to rotate your legs? Its really frustrating and silly that I have to go through the motions (literally) of riding a bicycle if I want to get the priviledge of using a bike lane or going without a license plate. (At least that's the case here in Germany AFAIK).
They could go ahead and make "fast electric bikes" and "slow electric bikes" or something as categories and that would make sense - but hinging the decision on whether your legs or your wrist is turning is illogical. I think it is actually morally charged - like you have to put in the work if you want the privilege.
Its easy, the accelerations are completely different and very hard to gauge. Also you have the elderly going speeds that does not mach their reactions, while also being unaware of how fast they are going. If you try biking with them it become very obvious how many dangerous situations they cause compared to true e-bike and normal bikes.
Pedal assist feels like amplifying your natural power. The boost it gives is perfectly matched with your own movements so it feels more like you are just super fit. And there is far less chance you can just slip and apply too much power unlike throttle controlled.
In my area, I think that non electric bikes are often more dangerous: they are often non tolerant of others and hesitant to slow down because of speed conservation. Especially in our hilly town. Easy "free" acceleration is plus here.
We can focus on clamping down of "faux pedal ebikes" when the time comes, but for now it looks like we'll be throwing out everything to just to stop teenagers on surrons.
It's because absolutely everyone understands the proportional nature of "press pedals to go" while nobody without special training understands "turn wrist to go", especially not the crucial details of "untwist wrist to stop" and "by the way don't yank open the throttle while attempting a sharp turn".
> Why do e-bikes become better or more safe when you have to rotate your legs?
Because you're directly engaged in operating them. Electric handcycles are also legal, the problem isn't which body part it is, it's whether you're moving muscles to move your bike - and, perhaps more importantly, that your bike will stop accelerating when you stop your body.
That's the limit for continuous rated power. The motor's frequently have 600W-750W of peak power output, and can legally use this much for short amounts of time (usually seconds, like accelerating from a stop; but often also for going up a steep hill for several minutes).
The point in distinguishing the different classes is about where the bike should fit into the ecosystem. Should it ride on the shoulder, interacting with pedestrians and slower bikes, or should it ride on the road, interacting with cars and motorcycles.
It doesn’t matter how much riding it takes, it matters how fast and controlled it is moving compared to the other traffic in that class.
"hinging the decision on whether your legs or your wrist is turning is illogical"
No it's not, it's recognizing the psychology between "big push with foot makes go fast" and "pressing button makes go fast".
Besides, if the only thing that matters is speed, then logically you'd have to require normal pushbikes to register as well, once cyclists are able to pedal sufficiently fast.
> recognizing the psychology between "big push with foot makes go fast" and "pressing button makes go fast".
And what is the psychological difference? As far as I'm concerned when I'm using torque-sensing pedal assist, I'm just pressing the button with my foot. The distinction between throttle and pedal assist is non existent in my eyes: pedal assist is just pressing the throttle with your foot.
It's like the invention of the power loom, but for knowledge workers. Might be interesting to look at the history of industrialisation and the reactions to it.
I guess technically you are right, in that NAT doesn't prevent connections, it enables connections. But in the situation where you would have a NAT, behind a residential router, an outside host cannot connect to an arbitrary host on my internal network.
On a publicly routed PC, I can call `listen` and an outside host can connect to me.
On a PC behind a NAT - if I don't set up port forwarding - I can call `listen` and nobody from outside can connect to me.
So one could say, going from publicy routed to behind a NAT means that only allowed incoming connections are possible. Or am I missing something and you can really, from the outside, open a connection to a PC on a residential network which is behind a simple NAT (TCP server listening on that PC)?
The only caveat is that if you're using RFC1918, it greatly limits who can connect -- only your ISP, or another customer connected to the same shared VLAN your router is, or anyone that can physically attach to that network (or anybody in a position to order, blackmail or social engineer those three groups or their employees) can do it, because they're the only people that can set a route to your router for RFC1918 destinations.
Other than that, the connection will just head right on through your router. NAT's whole thing is to change the source address of your outbound connections. Inbound ones (when they don't match port forward rules) are ignored by it, which means they get routed by the router in exactly the same way they would if the router wasn't doing NAT.
At best you could argue that RFC1918 blocks connections, which would be somewhat closer to true, but... well, it doesn't. If you actually want to stop all connections from outside your network, you've always had to do it with a firewall on the router.
And of course, I said "if". You can NAT on public IP space. On residential connections you're unlikely to have public IP space on v4, but that's just a consequence of v4 being exhausted.
There have been incredibly clever attacks based on tricking intervening routers into routing the traffic to the target gateway, but more prosaicly my next hop ISP is itself a threat I worry about.
Nooo... I don't want something to exist that can absolutely prove that a photo is real. This only serves to enforce social norms more rigidly. These include reasonable norms like against committing crimes or behaving abusingly but it also includes stupid norms like behaving uncool or doing something embarrasing. The problem is, where do you draw the line? I think if somebody does something stupid or even morally dubious there should always be a way of forgetting it.
That you can't believe everything you see in the age of AI is a feature, not a bug. We are so used to photographs being hard facts that we'll have to go through a hard transition, but we'll be fine afterwards, just as we were before the invention of photography. Our norms will adapt. And photographs will become mere heresay and illustration, but that's OK.
I think here the same dynamic is at play as with music/videos and DRM. Our society is so used to doing it the old way - selling physical records - that when new technology comes along, which allows free copying, we can't go where the technology leads us (because we don't know how to feed the artists, and because the record industry has too much power), so we invent a mechanism to turn back the wheel and make music into a scarce good again. Similar here: we can't ban Photoshop and AI, but we invent a technology to try to turn back time and make photos "evidence" again.
LLMs are just the speech center part of the brain, not a whole brain. It's like when you are speaking on autopilot, or reciting something by heart, it just comes out. There is no reflection or inner thought process. Now thinking models do actually do a bit of inner monologue before showing you the output so they have this problem to a much lesser degree.
> this just hasn't been the case for some time now
Which I find sad actually. The idea of C++ as a superset of C is really powerful, especially when mixing C and C++. A while ago I had a C project (firmware for a microcontroller) and wanted to bake the version and the compilation time into the firmware. I didn't find a way to do this in plain C, but in C++ you can initialize a global struct and it gets statically linked into the output. This didn't even use constexpr, just preprocessor trickery. Then it was just a matter of renaming the c file to cpp and recompiling. I guess you could also do that with C, but there are things like RAII or constexpr or consuming a C++ library that you can't do without.
> wanted to bake the version and the compilation time into the firmware. I didn't find a way to do this in plain C, but in C++ you can initialize a global struct and it gets statically linked into the output. This didn't even use constexpr, just preprocessor trickery.
I might be misunderstanding here, but if you are okay with preprocessor trickery, then it's doable.
> Cellebrite admits they can not hack GrapheneOS if users had installed updates since late 2022.
So, how do I know that GrapheneOS is not a honeypot for the really big fish?
At this point it seems if you really want to be safe, you have to add obscurity (in addition to conventional best practices). Like changing the pinout on your USB port so the exploit device can't connect.
Or 3) there are illegal immigrants and ICE is deporting them according to the law, BUT some people think this is unjust and want to do something against it. The democratic process to change laws is too slow or doesn't work properly, or there is no majority to change the law.
Remember there is a difference between legal and legitimate. You don't have to do something just because it is the law (well, you could define "have to" to mean what the law says, but then it becomes pretty circular).
Historically, often behavior changes before the applicable laws change. Think about the acceptance of gay relationships, or the use of cannabis. If people don't sometimes break the law, society can't evolve. That doesn't mean the rule of law has to break down. I think the rule of law is very important and would uphold it in most cases, but there are certain cases where conscience might order one to break or circumvent a law.
I think users applies to end-users here. So you must not run the software as a service (either paid or for free) for other users. You are free to use it yourself.
Crucially, I think what is banned to offer accounts. Offering turnkey-hosting is probably banned in spirit, but the person offering the turnkey-hosting is not in violation, rather the person booking the turnkey hosting and offering the accounts on the instance to third parties is in violation.
I think the wording is originally against somebody like Amazon hosting e.g. database instances for other people to use, and then giving you an account in that database. It's still OK to rent a VM from them and use the package manager to install it.
In any way, it is really confusing, in a way a license should not be. And I don't really understand why someone builds a blog platform, which is not monetized, open sources it, but doesn't want other people to host it. If I open source my stuff, I want people to use it. If I want to share the code but don't want people to use it I'd just put it somewhere it with no license at all (all rights reserved).
Idk. That's not how I'm reading it. Someone reading my blog is a user of the blog software. So running the blog and letting people read it would fall under that limitation and therefore would be prohibited.
I understand that's probably not what they tried to write, but wouldn't want to defend that understanding in a courtroom.
> It's still OK to rent a VM from them and use the package manager to install it.
Do you open up port 80 to the world? Because then you are hosting the service that offers users access to substantial features or functionality.
> In any way, it is really confusing, in a way a license should not be.
So, as there are a couple of docks coming out that work with Switch 2 and have apparently reverse engineered the protocol... I wonder if some company could make a small dongle that just sits between the switch and my monitor, or my USB-C docking station, and fixes the communication.
For a DIY solution, protocol wise it doesn't seem too complicated, but electronically USB-C or HDMI is out of reach for most hobbyists. And I assume most USB-C interface chips you can get aren't programmable to the degree neccessary...
They could go ahead and make "fast electric bikes" and "slow electric bikes" or something as categories and that would make sense - but hinging the decision on whether your legs or your wrist is turning is illogical. I think it is actually morally charged - like you have to put in the work if you want the privilege.