Testing image uploading via the mobile PWA, as @prologic@twtxt.net told me it wasn’t working. Let’s see if it is true.

@bender@twtxt.net Test!

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

root=7cnr5hulfahb fork. I am now forking:

Lyse swears the issue at with the app. So, I will continue testing on this conversation. I am not going to fork yet, these are just twtxts on the conversation.

Lyse swears the issue at with the app. So, I will continue testing on this conversation. I am not going to fork yet, these are just twtxts on the conversation.

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

The issues might be that we are testing on production, and feed URL changing 😅. But I want to make sure, just in case. So, this one starts a test. Again.

🥰 Su cute! Have a nice weekend, @lyse@lyse.isobeef.org! I am back at testing the twtxt.app. I think—I think!—it is working fine so far, but a few minutes will tell.

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

Auf LinkedIn erzählt mir gerade jemand: "Dein sauberer Code kostet dich jetzt bares Geld."Die grandiose Idee: Tests weglassen, Team reduzieren, QA weg … alles Overhead> Es gilt: Weniger Code = weniger Tokens = weniger Kosten.> Beweis: fertiges Produkt, 2 Wochenenden, ~40 % meines Claude-Limits.Das sind Leute, die jetzt Software und Services bauen, die wir nutzen sollen und die wahrscheinlich schon genutzt werden. Gruselig.

@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

That’s so cool. I’ve been meaning to test if my website works on old browsers. I highly doubt it since it’s a lot of JavaScript, but it’s on my todo list to start generating a no-js version.

That’s so cool. I’ve been meaning to test if my website works on old browsers. I highly doubt it since it’s a lot of JavaScript, but it’s on my todo list to start generating a no-js version.

Alright, this is a test post from the twtxt.app 🤞

Alright, this is a test post from the twtxt.app 🤞

Testing 1 2 3

Hello from the new twtxt.app PWA! 🎉 Testing the Yarn.social publishing backend. (automated test post)

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.

https://lyse.isobeef.org/tmp/this-is-a-test-tt.png

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

https://itsericwoodward.com/images/bba54e39.png
https://itsericwoodward.com/images/e472ea48.png
https://itsericwoodward.com/images/65b23473.png

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…