Nick Offerman says he's not a real cyclist because he doesn't put on Lycra and go 30 Miles per hour.
I disagree. Biking on the streets of NY and LA makes you a real cyclist. I'm not sure what putting on Lycra makes you ...
Nick Offerman says he's not a real cyclist because he doesn't put on Lycra and go 30 Miles per hour.
I disagree. Biking on the streets of NY and LA makes you a real cyclist. I'm not sure what putting on Lycra makes you ...
It depends where the motorists are used to driving with bikes, and how fast they're going.
I'm confused about what kind of data you want to protect. If you mean your posts and comments, they are already publicly availible on the Internet. Meta doesn't need to make a activitypub app that gets federated with Lemmy (or kbin) to aggregate and sell this data.
Is there an other kind of data that is visible only to server administrators?
Can't they aggregate and sell your Lemmy activity data without federating with your sever? It's all in the public Internet.
I guess it won't be that useful if they have no way of tracking you. But, I don't think federation makes it easier to track users. Do sever admins get ip addresses of every user on a server they federate with?
Plastic also works, and is far more durable
Do you think blood donors are more or less likely to be exposed to COVID?
I was struck by the number of highways in Philadelphia:
Seems like we could tear down a few to reclaim some valuable urban land.
I wish drive thrus would just go away entirely. Theyre bad for cities.
Why not kbin?
Does this also apply to comments?
How do you define "largest cities?" I get around fine without a car in a city with a population under 200k.
One problem with kbin is that the whole federation of instances thing didn't work so well there. It seems all the users and all the content is one one server: kbin.social.
This is concerning since it introduces a single point of failure.