Show more

hell yeah i'm blocking javascript. now i am attacking it. en garde!

I just learned the video is up of "Countering Imposter Syndrome Culture", Sage's 2019 SeaGL keynote! There are lots of talks for people who have imposter syndrome, but this talk tells you how to avoid triggering imposter syndrome in others. archive.org/details/imposter_2

@clacke I finally got up the nerve to listen to the interview and I'm happy with it, yay ๐Ÿ˜

It reminded me of one thing @fluffy mentioned though, which might be a good addition to the show notes: tools.ietf.org/html/rfc6721 is informally referred to as the Atom tombstones spec, although officially it's 'The Atom "deleted-entry" Element'; the "tombstones" terminology only lingers in the XML namespace URL for it.

Also if you do decide to update the show notes again, I guess I could be pedantic and say that the organization is spelled "X.Org", not "Xorg", unless you're referring to the specific device-dependent X server implementation. Of course, absolutely nobody actually cares. ๐Ÿ˜†

I've always thought of nano as a text editor that exists for people like me who haven't learned vim yet

But it's only recently occurred to me that like. People made nano. And they still develop for it. It's maintained. They're probably proud of it. It's good software.

It didn't emerge from the aether as a stepping stone for text editing in the terminal.

It's kind of changed my perspective, actually. I still want to learn vim, I've always wanted to, but I'm going to try to not be embarrassed to admit that I use nano for now. It's good! It's few people's favourite but there's absolutely nothing wrong with it.

This is a bizarre little story about very well funded and incredibly shady online restaurant delivery services.

"Doordash and Pizza Arbitrage"

themargins.substack.com/p/door

Another day, another "bring back Google Reader" article that does not acknowledge Reader's extremely robust social features.

These features allowed someone to, for example, share an article they liked to their friends and spawn a private mini-forum to discuss that article. It was similar to sharing an article with friends on Facebook, but based on your RSS curation rather than whatever you got from Facebook's awful news feed.

"As the challenged party, you may choose the weapon for the duel."
"I chose forgiveness."
"That... That is not a weapon."
"Can it hurt people?"
"I guess, if the forgiven is petty, but-"
"Then it can be a weapon."
"But how do you intend to win?"
"Who says I intend to win?"
#MicroFiction #TootFic #SmallStories

HPR3082: RFC 5005 Part 1 โ€“ Paged and archived feeds? Who cares? 

Itโ€™s up!

Recorded together with @fluffy and @jamey , it will hit the main feed Tuesday in two weeks.

http://hackerpublicradio.org/eps.php?id=3082

When serving most RSS/Atom feed readers today, you have to choose: Do you make a complete feed with all the things you ever published, or do you make a shorter feed with just the latest entries?

This is a trade-off with pros and cons, and it seems like a trade-off you have to make, but a solution to let your Atom feed have the cake and eat it too existed already 13 years ago, if only any of our feed readers would adhere to it: RFC 5005, Feed Paging and Archiving

Audio direct: http://hackerpublicradio.org/eps/hpr3082.spx

@clacke

It's funny how I think of this RFC as "the one about paged feeds", yet after talking about it and re-reading it (the title is "feed paging and archiving"), it clearly is about archived feeds. I guess that's why that's the best specified part too.

Section 2: This is what people are accidentally doing already, let's mark clearly the semantics of that with this one tag.

Section 3: This is what people will do as a naive attempt to carry low-effort HTML paging over to Atom, so let's at least formalize the vocabulary.

Section 4: Ok, here's what you should actually do (except a few special cases where section 2 applies).
Show thread
The exact text in the spec regarding the unreliability of "section 3" feeds, "paged feeds", is "Therefore, clients SHOULD NOT present paged feeds as coherent or complete, or make assumptions to that effect.". In section 4 it also digs at paged feeds, saying "Unlike paged feeds, archived feeds enable clients to do this without losing entries.". Clearly section 3 is the designated black sheep in this spec. ๐Ÿ˜€

... and at the same time I assume that most people would start by implementing section 3 feeds, because they're the easiest. ๐Ÿ˜
Show thread

this is obviously not advice, because who would offer this as advice, but I would bet this is a prime time to set up a pirate fm radio transmitter and seize the airwaves if one were interested in such absurdities. I doubt they're rolling a lot of teams to track down rogue transmitters right now. but like I said, there's no way anyone would offer something so outlandish and try to pass it off as advice. inconceivable really.

The student bowed.
"Master, I am sorry."
"Why were you absent yesterday?" the sword master asked.
"I don't know. I... simply could not get out of bed."
"If this happens again..."
"Yes?"
"Allow yourself to stay in bed."
"Master?"
"A blunt sword can be honed. A broken one can not."
#MicroFiction #TootFic #SmallStories

found haiku in Frankenstein. for a long time I have had a blanket ban on haiku generators in my classes because what more is there to say about computer-generated haiku that wasn't already said 53 years ago rwet.decontextualize.com/pdfs/ but... I had never actually programmed the "find haiku in an existing text" thing before I did have fun and learned a bit making it, whoops

If you really want to understand an RFC, follow these four simple steps:

1. Quickly read the RFC once or twice to get a rough idea.
2. Be super lucky and find two of the people in the world who are passionate about this RFC specifically.
3. Hang out with them for an hour, record.
4. Edit the recording while reading the RFC again, detect all your misconceptions that you exposed while recording.

๐Ÿ˜

RT @coldfootfilms@twitter.com

I'm not saying this photo will solve all your problems.

I'm just saying some days you need a picture of a kitten at the exact moment he realizes that maybe playing bass isn't as easy as it seems.

๐Ÿฆ๐Ÿ”—: twitter.com/coldfootfilms/stat

Isnโ€™t dialectics the stuff that makes you pee

@s0 @djsundog If the surface depth is under 5mm, I think NFC radio would still pass through. I don't know how well complex electronics would fare a few hundred years in the future (especially electrolytic capacitors), but ironically, older electronics might still be viable

RFID is doable with ancient components, but you'll need a stronger radio field

If "future" is a long time, then an ancient relic powered by a spark gap transmitter might be pretty cool

In 1997 QNX released the QNX Demo Disk - a floppy that featured the QNX 4 OS, GUI, PPP or networking, web browser, file browser, and several demo applications... all in a single 1.44MB diskette.

I was really impressed by the thing at the time. Both it and the demoscene drove home that software didn't have to be as big as it was starting to get.

๐ŸŽž๏ธ Demo video: youtube.com/watch?v=K_VlI6IBEJ

๐Ÿ’พ Demo Disk image files: toastytech.com/guis/qnxdemo.ht

:hacked: Hacking the demo disk: openqnx.com/node/259

๐Ÿ“š Original website: web.archive.org/web/1997071016

#retrocomputing

IT'S BEEN 

a hard day's night, and I've been working like a dog ๐ŸŽต

Show more
Toot.Cat

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!