Joseph Nuthalapati @njoseph_1@toot.thoughtworks.com

#NotreDame #Reconstrucción #catedral #cathedral

Have you checked out https://pinafore.social? It's a web-based alternative front-end for Mastodon servers. Simple, performant, perfect for low-end and older devices.

@codesections The tracking is a choice made by the website developers, not a given.

The browsers are reducing the costs involved in making that choice, thus directly facilitating and encouraging it.

Treating tracking as a given, is exactly the lie we're being fed by the industry.

“…more than 750 communities across the country have built their own broadband ISPs or cooperatives. Studies have shown these locally owned and operated networks tend to offer lower prices, faster speeds, and better customer service than their private-sector counterparts.

“Instead of competing by offering better service—private sector telecom giants like Comcast and AT&T have routinely turned to a cheaper alternative: easily corrupted state lawmakers.”

https://motherboard.vice.com/en_us/article/kzmana/report-26-states-now-ban-or-restrict-community-broadband

here is a thread of sci-fi and horror short fiction I have enjoyed recently

you can read them all online

Okay, this took way longer than expected, but now I have my own #Wallabag instance, dockerized and authenticated against LDAP.

Does Wallabag support LDAP out of the box? Nope.
Is there a patch? Yes.
Do you want to figure out yourself how to apply it? You absolutely don't.

But you don't have to: https://git.rys.io/rysiek/docker-wallabag-ldap/

I had ~150 open tabs. Now they're all in my Unread list. Way more manageable.

And if you'd like to have a laugh, look at the commit messages.

I think @emacsen estimated that @librelounge has about 500 listeners or so around now. I guess there are a lot bigger podcasts out there, even in the FOSS space, but that feels like a lot more than I still expect... especially since we still aren't on the major podcast directories (hopefully I can finish the last feed things this weekend.)

I'm glad that people are enjoying listening to it. We're definitely enjoying making it.

#mastoAdmin #keybase #bullshit

Contrary to their documentation, Keybase does not ask for the consent of the admins of a Mastodon-software instance before adding our instance as a "partner".

Since they are liars, I am blocking the endpoint they use to confirm our users. (/.well-known/keybase-proof-config)

We are also *extremely* concerned about their "What's Next", and do not consent to these tech-bro experiments.

https://keybase.io/blog/keybase-proofs-for-mastodon-and-everyone

images like PNG and JPEG files get blurry when zoomed in beyond 100% of their size. this is true of video files, too, and many other methods of representing graphics. this is because these files contain an exact description of what to show. they tell the computer what colour each point on the image is, but they only list a certain number of points (or picture elements - pixels!). if a photo is 800x600, it's 800 pixels wide, and 600 pixels tall. if you ask the computer to show it any bigger than that, it has to guess what's between those pixels. it doesn't know what the image contains - to a computer, a photo of the sky is just a bunch of blue pixels with some patches of white thrown in. there are many algorithms that a computer can use to fill in those blanks, but in the end, it's just an estimation. it won't be able to show you any more detail than the regular version could.

a font, however, is different. almost all fonts on a modern computer are described in a vector format. rather than saying "this pixel is black, this one is white", they say "draw a line from here to here". a list of instructions can be done at any size. if you ask a computer to show an image of a triangle, it'll get blurry when you zoom in. but if you teach it how to draw a triangle, and then tell it to make it bigger, it can "zoom in" forever without getting blurry. there's no pixels or resolution to worry about.

vectors can also be used for images, such as the SVG format. here's an example of one on wikipedia: https://upload.wikimedia.org/wikipedia/commons/0/02/SVG_logo.svg
even though it's an image, you can zoom in without it ever getting blurry!

even though you can resize an SVG to your heart's content, it'll never reveal more detail that what it was created with. so you can't "zoom and enhance" a vector image either.

there are always exceptions to the rule. not all fonts use vector graphics - some use bitmap graphics, and they get blurry like PNGs and JPEGs do too.

so if vector graphics don't get blurry, why don't we use them for photos? to put it simply, making a vector image is hard. you need to describe every stroke and shape and colour that goes in to replicating the drawing. this gets out of hand very quickly when you want to save images of complex scenery (or even just faces). cameras simply can't do this on the fly, and even if they could, the resultant file would be an enormous mess of assumptions and imperfections. the current method of doing things is out best option.

#LynneTeachesTech