Oof! I found a bug on Yarnβs Markdown rendering, @prologic@twtxt.net. See OP.
@quark@ferengi.one Pinging @movq@www.uninformativ.de, in case it is a bug.
↳
In-reply-to
»
My kid just uncovered a bug in a program I wrote by grabbing my laptop and smacking the keyboard a bunch. Biological input fuzzing; a real-life chaos monkey.
β€ Read More
It did! And I fixed the bug last night. And now Iβm curious how your pod deals with spam. ππΌ
My kid just uncovered a bug in a program I wrote by grabbing my laptop and smacking the keyboard a bunch. Biological input fuzzing; a real-life chaos monkey.
Fixed another bug in my finger client: rfc1288 says lines have to end with crlf, but I was just sending lf.
Fixed a bug. Found a new bug in yesterdayβs work. Fixed that bug.
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
β€ Read More
@prologic@twtxt.net @jlj@twt.nfld.uk @movq@www.uninformativ.de
/p/tmp > git clone https://www.uninformativ.de/git/lariza.git Mon May 24 23:48:18 2021
Cloning into 'lariza'...
/p/tmp > tree lariza/ 12.5s ξ³ Mon May 24 23:48:32 2021
lariza/
βββ BUGS
βββ CHANGES
βββ LICENSE
βββ Makefile
βββ PATCHES
βββ README
βββ browser.c
βββ man1
βΒ Β βββ lariza.1
βΒ Β βββ lariza.usage.1
βββ user-scripts
βΒ Β βββ hints.js
βββ we_adblock.c
2 directories, 11 files
↳
In-reply-to
»
I just timed it: 59 seconds for my Raspberry Pi to boot, 33 of which is waiting for my keyboard firmware to initialize. That's just absurd.
β€ Read More
Unrelated: my first response shows a rendering bug on your site: itβs dropping a backslash. Hard to mix markdown and genuine plain text.
@prologic@twtxt.net Bug in your profile links: itβs repeating a segment. For example, your face tries to get to https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
β€ Read More
@xuu@txt.sour.is @prologic@twtxt.net @thewismit@twtxt.psynergy.io ah.. probably a bug with the re parser. looks like i can do it without the <>βs with lex
I applaud this, but I also advise against this for your career. Unless the change youβre making has immediate and significant business benefits, from a PM/EM perspective youβre 1) wasting time 2) potentially introducing bugs. The correct move is to wait until the org is so bogged down with tech debt that meaningful progress cannot be made, then switch companies/teams. Always leave the code better than you found it | Hacker News
Printer bug + Exchange https://dirkjanm.io/exploiting-CVE-2019-1040-relay-vulnerabilities-for-rce-and-domain-admin/
@Virtusize Seems like you caught a Twitter bug