keverets @keverets@librem.one

One of the main reasons we don’t have a truly decentralised internet is actually really simple: it’s the fact that providers globally don’t give us symmetric upload/download speeds and fixed IP addresses at home. Kills decentralisation at the root. 1/2

omg

Anyone who thinks decentralization is an unmitigated good never heard of cars in comparison to public transport

Good luck #BlackBerry users... you have been mobile security pioneers!

"The shutdown means the phones will no longer reliably function for "data, phone calls, SMS and 9-1-1 functionality"

#mydataisMYdata
#smartphones #privacy

https://www.nbcnews.com/tech/tech-news/classic-blackberry-devices-stop-working-normally-jan-4-rcna10616

Spotted in the wild


#CashFriday

Before you buy that e-book from Amazon, do yourself a favor and see if the publisher has a website with direct sales.

I've found a number of books that I was interested in DRM-free, in EPUB format, and sometimes at a discounted price, just by poking around a little.

You can connect WordPress blogs to the Fediverse by using the ActivityPub plugin:

https://wordpress.org/plugins/activitypub/

The plugin lets people on Mastodon etc. follow your blog as well as share and comment on your blog posts.

The author of the plugin is @pfefferle

#FediTips #Fediverse #WordPress #MastoTips #Mastodon

James Webb Space Telescope over Earth

Image Credit: Arianespace, ESA, NASA, CSA, CNES

https://apod.nasa.gov/apod/ap211226.html #APoD

I've always been told it's better to write comments describing the *why* rather than the *what*. This was for a couple of reasons but the primary one was that if you can't understand what the code does by reading it, you shouldn't be messing with it. That makes perfect sense to me.

However, Jon Calhoun from the Go Time podcast recently interviewed a (nearly) blind developer, Dominic St-Pierre, who had a very interesting take on this. He said that describing the *what* actually makes code more accessible; it saves those using screen readers from having to sit through a whole code block to figure out what could have been described in a comment in just a few words.

Those of us without any vision impairment can skim through and understand a whole page of code in just a few minutes while it might take half an hour with a screen reader.

Good comments can save a ton of time

https://changelog.com/gotime/209

@jlcrawf Yes, and if you do an unauthorized repair of a Tesla, you run the risk of Tesla remotely disabling Supercharging "for safety" (but really about control). The Rich Rebuilds Youtube channel had covered a lot of the issues around how Tesla is trying to redefine the traditional secondary repair market to lock people into dealerships for repairs, and making it hard for owners or unauthorized mechanics to get spare parts. Think Apple, but for cars.

The first wave of EVs are old enough their batteries are starting to fail. People tend to repair old ICE cars, but at a $22k price tag to replace batteries that will inevitably fail, it seems like older EVs will be thrown away instead of repaired. https://gizmodo.com/finnish-man-passes-on-paying-22-600-to-replace-his-tes-1848268874

Saying goodbye to an old friend https://ar.al/2021/12/16/saying-goodbye-to-an-old-friend/
from @aral. We are with you at @XWiki and @cryptpad Trillions $ corporations should not own our data and the software we use.. Our civil liberties are indeed getting frog boiled

RT @teachergoals@twitter.com

I feel seen. 🙌

🐦🔗: https://twitter.com/teachergoals/status/1473293389126852620