I’m still on a deckbuilding kick, so I was thrilled that we managed to get 3 games of Magic in last night.

In game 1, my Marvel Villains deck couldn’t stand up to Doctor Who’s Missy and her army of Cybermen (and Daleks). Since someone else was playing a dark lord Sauron deck, I guess that means she’s even more “villainous” that anything Marvel or Tolkien could offer.

For game 2, I ran my Guardians of the Multiverse deck (formerly known as The B-Vengers or Marvel Heroes 2: Electric Bugaloo). It was working well, and I had quite an army going, but I was still one turn from a win when an opponent’s tribal elf deck went off, killing everyone with 19 19/19 forest-walking elves. ¯_(ツ)_/¯

Then in game 3, I ran my Avengers deck, and finally got the win thanks to a Heroes’ Podium, a pair of Hawkeyes, and a flying, shield-wielding Captain America. Assemble, indeed.

Last night will likely be my final Marvel-only game night for a while. I still need to test the decks out some more, but they’re basically complete (I don’t currently plan on adding any more cards to them). Plus, while I’m on this kick, I’d like to finally finish my Sauron deck, and I’ve got some cards on order for both a Dune-themed deck and a couple of decks inspired by the old-school Beatdown Box.

Finally, I added some tests and fixed this. After updating the feed metadata, I now just return early and do not attempt to build an SQL multi-value INSERT statement. Easy-peasy.

@movq@www.uninformativ.de “when this stuff still mattered” LOL, true :-D

Right, the good old pen test! Never gets old. :-D

Bwahahaha, these security folks have a great sense of humor! :-D Got a phishing test e-mail disguised as an overdue anti-phishing training e-mail:

We receive these test phishing e-mails every now and then at work. When you follow the links and log in at the fake login, you probably get assigned another (real) training.

When I got this e-mail, I immediately thought of such a test. Since I actually do have some stupid training deadlines coming up soon, I wasn’t 100% sure, but still doubted that this was one of them. To make the timing even better, in the team meeting last week, our bosses reminded us to complete outstanding trainings before the deadlines. Ideally well in advance. Notifications about deadlines coming closer are sometimes not only sent to the individuals but also to the bosses and their bosses. And then things can get out of hands when somebody doesn’t read the e-mails properly and mistakes them for deadline exceeded reports.

Anyway, the URL also looked kinda legit. It really doesn’t help a single bit that domain names change all the fucking time. So, still with the test program in mind, I thought, I just give it a quick shot out of curiosity. Since I just had logged in before, the empty SSO username field was totally obvious then. Looking at the e-mail headers confirmed that this was indeed one of security’s field checks. :-)

@movq@www.uninformativ.de No I haven’t :/

Just out of curiosity, have you ever ran this on real hardware? 😃

Only QEMU. Would you like to help test it on real hardware? 😅 I’m not sure I have anything worth testing it on!

@david@daiwei.me Might not have tested that path very well. Can you make a note of this on Gitea?

Testing offline posting …

Testing the NEW Composer Preview

@dce@hashnix.club Ahh! Let’s fix the 403 error then? I don’t have access to Codeberg, so I can’t reasily test. Can you walk me through what you tried and any other details? I’ll get this fixed.

test

@bender@twtxt.net Test!

Well, after all these tests, I can’t reproduce. I have used exclusively the desktop to conduct these tests.

@david@daiwei.me good, let’s get this test going. This is simply a reply to iqqsqst5vokf (first twtxt).

@prologic@twtxt.net Let’s give it a shot! Test!

@aelaraji@aelaraji.com wow, look who the cat dragged in! 😂 I was thinking about you just yesterday, when testing the twtxt.app, and seeing your avatar photo broken. And today, here you are! Nice to “see” you mate!

Test 3

multiline link

https://movq.de/

Test 2

multiline

Test 1

Test! It works now.

🚨 jenny was broken due to the switch to v2 hash tags.

I pushed a hotfix to main, but this needs a few more test cases. I’ll do that tomorrow.

@lyse@lyse.isobeef.org Test!

This is a neat tool for comparing several public DNS resolvers (some of which were new to me) on various criteria; includes a speed test. https://evilbit.de/dns-resolver-guide.html

@movq@www.uninformativ.de Test passed. I think.

This is a test.

test helololol

this is a test

@movq@www.uninformativ.de

What’s your motivation for running this, btw? 🤔

Basically, two things a) feeling generous for folks that either can’t afford or find it hard to have a little place to call home (webpage, feed, whatever) and b) a real opportunity to test some of the components that make it possible sshbox, which I know works well as it fronts my Gitea instance’s Git+SSH service and box, a container runtime I wrote a while ago, recently improved, hardened and polished.

testing 1 2 3

Hello World! testing an offline-first PWA Yarn.social / Twtxt client :)

@lyse@lyse.isobeef.org Oh, no, he was the one providing the feedback. 😅

mgk appears to be everywhere. His Unicode box drawing demo has been part of my unicode-test script for a long time: https://movq.de/git/bin-pub/file/unicode-test.html#l23

@bender@twtxt.net The good thing is that it’s already pretty battle-tested. 😅 There was this dumpster fire a few years back: https://news.ycombinator.com/item?id=31114554 This was on their front page for quite a while, just look at the number of comments … 😂

@movq@www.uninformativ.de LOL. At least now you know your infrastructure and web server can handle some traffic. Consider it a test, in addition to the fleeting recognition. 🤣

On the subject of debugging these so-called AI(s) / Black Boxes… the model is a black box sure, but that’s not really the problem. Everything around it — the inputs, the outputs, the decisions it makes — all of that can and should be fully logged, traced and replayed. The “program” isn’t the model, it’s the full context you feed it. That’s what you debug. It’s not so different from any other system really; if you’re running something in production with no logs, no structured outputs and no tests, you’d have the same problem. The model doesn’t change that discipline, it just makes it more important.

Testing, testing, everything seems to be in order. Alright gordon your suit should keep you safe from all of this..

I’m pleased to announce that express-twtkpr (my ExpressJS library for hosting, editing, and posting to a twtxt.txt file) continues to crawl towards a full release with another (pre-alpha) update published to NPM. This update includes a whole new plugin system, and even a (little) more documentation. Check it out, if you dare (and use it at your own risk): https://www.npmjs.com/package/express-twtkpr

And speaking of plugins, here’s where the fun’s at: announcing express-twtkpr-core-plugins, a set of 3 plugins for your TwtKpr install: emojiButton, uploadButton, and postToMastodon. Like express-twtkpr, this set of plugins is still in pre-alpha, and lacks documentation, examples, tests, installation flexibility, or polish (so also use them at your own risk). Other than that, they work great: https://www.npmjs.com/package/express-twtkpr-core-plugins

Stay tuned for more! 🤘

Hello, this is a test post.

testing weeks soon ^^ I’m so close to graduating

AD Pentesting https://niklas-heringer.com/penetration-testing/active-directory-pentesting-part-02/

Just a test

Interesting. Another parsing issue? Let’s test: this should be italics. Then this also should be “italics”. End.

@lyse@lyse.isobeef.org That’s crazy! If you don’t mind me asking, what browser are you using when you see this?

@bender@twtxt.net Glad to hear it, I’ve neglected a Safari test thus far.

Thank you both for checking.

For what is worth, I am not experiencing what @lyse@lyse.isobeef.org described. Tested with Firefox on Ubuntu, and Safari on macOS.

@bender@twtxt.net both, but neither directly. I know every workaround there is, including those used by developers, to test apps, while working on them. However if “sideloading” becomes so tedious, even the more technical users, cannot be bothered to do it, competing appstores and independent developers, not wanting to send their money and ID to Google, loose users at such rate, they likely won’t be able to justify continuing to maintain their projects, people like me rely on.

I’m happy to report that, earlier today, I published an early version of express-twtkpr: an ExpressJS library that enables hosting (and directly posting to) a twtxt.txt file. It works great (otherwise you wouldn’t be able to read this), but it’s still in alpha and lacks documentation, examples, tests, installation flexibility, or polish, so please use it at your own risk. Enjoy! https://www.npmjs.com/package/express-twtkpr

I’m supporting incremental SQLite schema changes to just upgrade from an older database version to whatever the current software version supports. In the past, I already noticed that this is quite expensive in unit tests when each test case runs through the entire schema patches and applies them one by one.

To speed up test execution I now decided that I finally go through the troubles of maintaining both a set of incremental patches and a full schema setup in one go. A unit test verifies that both ways end up with the same structure. This gives me a set of SQLs to check the structures:

SELECT type, name, tbl_name, sql
FROM sqlite_schema
ORDER BY type, name, tbl_name

Unfortunately, the resulting CREATE TABLE SQL queries are formatted differently, depending on whether the full schema was set up in one big step or the structure had been modified with ALTER TABLE. Mainly, added columns are not on their own lines but appended in one physical line. That’s why I wanted an SQL formatting tool. Since I didn’t find one that works decently, I’m now doing some simple string manipulation. Joining consecutive whitespace into a single space character, removing spaces before commas and closing parentheses and spaces after opening parentheses. This works surpringly good enough. Of course, if it fails, the “diff” is absolutely horrendous.

Now for the cool part, my test execution dropped from around 5:05 minutes to just 1:32 minutes! I call that a win.

I just stumbled across PRAGMA table_info('tablename') https://sqlite.org/pragma.html#pragma_table_info, PRAGMA foreign_key_list('tablename') and friends. I guess, I have to play with that, now. It’s probably much better to use than the SQL text approach.

And we’re back! 1st test trip 👌

Our first test over night trip 🤞

Testing…

@prologic@twtxt.net LOL. Best test ever: if it doesn’t work out, walk a few steps to complete comfort. Win-win!

sleeping in my van tonight, which is parked outside the front of our house just as a test from overnight 😂