Searching We.Love.Privacy.Club

Twts matching #follows.
Sort by: Newest, Oldest, Most Relevant

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

⤋ Read More

@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. 

⤋ Read More
In-reply-to » Okay, now that I knew what to look for, I found existing bug reports:

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. 🤯

⤋ Read More

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

⤋ Read More
In-reply-to » @itsericwoodward any news about this? I am, at the very least, curious!

@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!

⤋ Read More

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

⤋ 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.

⤋ Read More
In-reply-to » (#z25erwq) @zvava I never used any of the social media platforms, that's why I'm probably ignorant.

@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.”

⤋ Read More

** 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.

The evaluation model is strictly call-by-value

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”`

⤋ Read More