🧮 USERS:1 FEEDS:2 TWTS:1483 ARCHIVED:90252 CACHE:2744 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1482 ARCHIVED:90241 CACHE:2743 FOLLOWERS:22 FOLLOWING:14
Google details Android developer certification requirement, and it’s as bad as we feared
Google has been on a bit of a marketing blitz to try and counteract some of the negative feedback following its new developer verification requirement for Android applications, and while they’re using a lot of words, none of them seem to address the core concerns. It basically comes down to that they just don’t care about the consequences this new requiremen … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1481 ARCHIVED:90211 CACHE:2731 FOLLOWERS:22 FOLLOWING:14
@aelaraji@aelaraji.com, I mean to follow up here on the brief exchange we had on irc.mills.io, but I forgot. Never too late, so here it goes:
18:16 <aelaraji> quark 🙏 much appreciated but it won't be necessary, since there isn't much to miss out on in most of where I hang out, so I could just disconnect and spare everyone else the noise
18:17 *** aelaraji (aelaraji@776014f5a3edd32f1ed19658b7b85c8c655945b0feacaedd92fe60e61a3c0ae2) has quit (/ME goes "yeeeeet..!")
18:18 <quark> No noise for me.
18:18 <quark> It’s all good.
18:18 <quark> What would IRC be without on/offs?
18:19 <quark> Preeeety boring!
18:19 <quark> Ah, he was gone.
18:19 <quark> Well, I will twtxt this to him. LOL.
🧮 USERS:1 FEEDS:2 TWTS:1480 ARCHIVED:90198 CACHE:2728 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1479 ARCHIVED:90183 CACHE:2723 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1478 ARCHIVED:90172 CACHE:2715 FOLLOWERS:22 FOLLOWING:14
The twtiverse appears to have shrunk. Among the 61 feeds that I follow, I don’t see any hash collisions anymore. 🤔
🧮 USERS:1 FEEDS:2 TWTS:1477 ARCHIVED:90160 CACHE:2714 FOLLOWERS:22 FOLLOWING:14
Is Mainstream Tech News Dead?
Millions of “Followers”, but struggle to get a single “Like”? ⌘ Read more
Speaking of groff: I’ve been following their mailing list for a while now and this G. Branden Robinson person invests an insane amount of energy into that project. 🤯
🧮 USERS:1 FEEDS:2 TWTS:1476 ARCHIVED:90118 CACHE:2724 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1475 ARCHIVED:90066 CACHE:2689 FOLLOWERS:22 FOLLOWING:14
10 Crazy-Specific Rules Dallas Cowboys Cheerleaders Must Follow
Being a Dallas Cowboys cheerleader is one of the most high-profile off-field jobs in all of professional sports. The iconic uniforms, the backing of one of the most followed NFL teams in the country, and the throngs of cheering fans at games and events all make it so. The Cowboys’ cheerleaders are undoubtedly the most […]
The post [10 Crazy-Specific Rules Dallas Cowboys Cheerleaders Must Follow](https://l … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1474 ARCHIVED:90050 CACHE:2682 FOLLOWERS:22 FOLLOWING:14
@itsericwoodward@itsericwoodward.com pretty cool! Started following you, not to miss any progress. Thanks for the exhaustive reply!
@bender@twtxt.net Thanks for asking!
So, I’ve been working on 2 main twtxt-related projects.
The first is small Node / express application that serves up a twtxt file while allowing its owner to add twts to it (or edit it outright), and I’ve been testing it on my site since the night I made that post. It’s still very much an MVP, and I’ve been intermittently adding features, improving security, and streamlining the code, with an eye to release it after I get an MVP done of project #2 (the reader).
But that’s where I’ve been struggling. The idea seems simple enough - another Node / express app (this one with a Vite-powered front-end) that reads a public twtxt file, parses the “follow” list, grabs (and parses) those twtxt files, and then creates a river of twts out of the result. The pieces work fine in seclusion (and with dummy data), but I keep running into weird issues when reading real-live twtxt files, so some twts come through, while others get lost in the ether. I’ll figure it out eventually, but for now, I’ve been spending far more time than I anticipated just trying to get it to work end-to-end.
On top of it, the 2 projects wound up turning into 4 (so far), as I’ve been spinning out little libraries to use across both apps (like https://jsr.io/@itsericwoodward/fluent-dom-esm, and a forthcoming twtxt helper library).
In the end, I’m hoping to have project 1 (the editor) into beta by the end of October, and project 2 (the reader) into beta sometime after that, but we’ll see.
I hope this has satisfied your curiosity, but if you’d like to know more, please reach out!
🧮 USERS:1 FEEDS:2 TWTS:1473 ARCHIVED:90042 CACHE:2678 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1472 ARCHIVED:90032 CACHE:2678 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1471 ARCHIVED:90021 CACHE:2680 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1470 ARCHIVED:90004 CACHE:2669 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1469 ARCHIVED:89989 CACHE:2669 FOLLOWERS:22 FOLLOWING:14
Silent Component Updates & Redesigned Update Experience
Following on from our previous initiative to improve how Docker Desktop delivers updates, we are excited to announce another major improvement to how Docker Desktop keeps your development tools up to date. Starting with Docker Desktop 4.46, we’re introducing automatic component updates and a completely redesigned update experience that puts your productivity first. Why We’re… ⌘ Read more
Apologies if I’ve been spamming anyone out there in twtxt-land today.
I’ve been working on a couple of twtxt-related projects, and one of them is a reader (tentatively called twtstrm) written in JS. I used dummy data for the first few stages of development, but now I’m at the point where I need some real data, and that meant hitting up my actual following list.
Of course, it didn’t help that I had a typo in my If-Modified-Since headers, but all that has since been resolved.
Anyways, if I accidentally spammed you with requests today, I am sorry, and it shouldn’t happen anymore.
We thank you for your patience, and apologize for the inconvenience.
🧮 USERS:1 FEEDS:2 TWTS:1468 ARCHIVED:89982 CACHE:2683 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1467 ARCHIVED:89975 CACHE:2680 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1466 ARCHIVED:89964 CACHE:2691 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1465 ARCHIVED:89956 CACHE:2696 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1464 ARCHIVED:89943 CACHE:2694 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1463 ARCHIVED:89933 CACHE:2719 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1462 ARCHIVED:89926 CACHE:2715 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1461 ARCHIVED:89907 CACHE:2729 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1460 ARCHIVED:89905 CACHE:2731 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1459 ARCHIVED:89894 CACHE:2727 FOLLOWERS:22 FOLLOWING:14
@lyse@lyse.isobeef.org a content warning is a way to tell the audience the content they are about to see is (or might be) shocking, or unsuitable, or unlikable. The audience can then chose to see it, or not. You know, akin of movies stating:
“Warning: The following film contains scenes that some viewers may find disturbing. Viewer discretion is advised.”
🧮 USERS:1 FEEDS:2 TWTS:1458 ARCHIVED:89883 CACHE:2723 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1457 ARCHIVED:89869 CACHE:2715 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1456 ARCHIVED:89837 CACHE:2703 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1455 ARCHIVED:89815 CACHE:2688 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1454 ARCHIVED:89800 CACHE:2675 FOLLOWERS:22 FOLLOWING:14
@zvava@twtxt.net oh duh! Sorry, I promised I read, my brain just didn’t process it right. I shall follow your progress, and offer bits and pieces of unrequested trivialities. :-)
🧮 USERS:1 FEEDS:2 TWTS:1453 ARCHIVED:89786 CACHE:2676 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1452 ARCHIVED:89778 CACHE:2673 FOLLOWERS:22 FOLLOWING:14
Aussie apple exports to Canada easier as restrictions relaxed
Australia apple growers will have easier access to the Canadian export market following trade negotiations between the nations. ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1451 ARCHIVED:89768 CACHE:2666 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1450 ARCHIVED:89755 CACHE:2658 FOLLOWERS:22 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1449 ARCHIVED:89735 CACHE:2650 FOLLOWERS:22 FOLLOWING:14
** Answering some questions about Baba Yaga **
My previous post found its way to Hacker News; I don’t have an account there, but a commenter asked a few questions that I thought I could answer in a follow up post.
Baba Yaga uses call-by-value evaluation, not call-by-need (aka“lazy”).
From the interpreter,
”`hljs javascript
function visitFunctionCall(node) {
const callee = visit(node.callee);
// Arguments ar … ⌘ Read more”`
🧮 USERS:1 FEEDS:2 TWTS:1448 ARCHIVED:89727 CACHE:2644 FOLLOWERS:22 FOLLOWING:14