@movq@www.uninformativ.de I think it was user error. Testing again.

Testing … (yeah!)

The editor can launch a new shell now:

https://movq.de/v/6ec68b50dd/los86-edit-shell.mp4

Trivial to implement but super useful. It allows for simple but meaningful dev cycles: Edit source code, run/test it, back to editor. That’s what I do in the video.

(The Brainfuck program is silly, but I got nothing else at the moment.)

The I/O cache is also getting better. All that back and forth doesn’t hit the disk at all, once cached.

This whole thing is much more fun and interesting when you run it from a real floppy disk. It’s a 5.25” floppy in the video (so it’s actually floppy 😅). Disk seek times can be catastrophic and you don’t notice any of this on modern disks.

Test twtxt parser (please remind me to delete this)

I’m still making progress with the Emacs client. I’m proud to say that the code that is responsible for reading the feeds is almost finished, including: Twt Hash Extension, Twt Subject Extension, Multiline Extension and Metadata Extension. I’m fine-tuning some tests and will soon do the first buffer that displays the twts.

Meh, I hit an import cycle while writing tests. Now I have to relocate some code. What do we conclude from that: don’t write tests. ;-)

tz test

test

testing video posts here’s a yunjin fancam

why’d it announce my test account LOL

👋 Hello @test@yarn.girlonthemoon.xyz, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗

I cobbled that together yesterday, @aelaraji@aelaraji.com. Since I was too lazy to write some tests, I simply hit your feed as I knew it contains two invalid lines right now. Sorry mate! :-( Next thing is to actually write some proper tests, improve the messages, etc.

Here’s the code: https://git.mills.io/yarnsocial/validator

Looking forward to that, @prologic@twtxt.net. :-)

@lyse@lyse.isobeef.org it’d be a blast to record too with my camcorder! i’d have to figure out positioning and stuff like you said but i could probably figure something out with a bit of testing :P yeah it probably does make the project itself longer than it should be but i feel like if you make it a cozy kinda “sew with me” video where people watch you sew and film it with a static angle instead of like, showing every step? i think that’d be nice even if a bit boring. so i could absolutely try that.

magnetic tape camcorders omg!!! mine is digital but i’d LOVE to get a tape camcorder

my camcorder battery & mini dvds came in the mail so i did a test recording! it’s so cool i love the crap quality. i do hope the memory stick arrives soon though because for the discs i can’t get them on my computer (not even a rom drive filesystem mount) without “finalizing” the disc which is like an old camcorder thing. i still think i’ll prefer disc recording though even if a limit of 30 minutes (or longer for lower quality) is strict. i like limitations like that

image upload test. have a wonyoung

another cli test for icons this time

cli test 3

cli test 2

cli test

test

test

test test test

Test Mention for Goryon! @doesnm@demo.yarn.social

Lasering Incidents
⌘ Read more

Dies ist ein Test!

Does anyone else declare a computer dead after extensive testing, let it sit on a shelf for 2 weeks or a year, try it again, and have it work fine? It seems like that’s happened to me a lot more than it should.

@eapl.me@eapl.me why not https://domain.com/.well-known/twtxt/:domain/:user ?

the business card test is this can you write it on your business card and have someone you give it to be able to figure it out without added context?

• phone number: yes because everyone knows what a phone number is.
  
• email address: yes, everyone knows an email and their aol or prodigy will let them email.
  
• twitter/x/insta/pintrest handle: no, whats a twitter? do i need to sign up?
  
• domain name: yes its simple and you just type it in a browser right?
  
• twtxt url: kinda? its a bit long and is that a forward slash? or a backward slash?

Lyse and me tested. Now prologic make public key auth. Ask prologic for create user and give your public key

Another test testing your test! 😆

test

Test post from IndiePass app

Micropub test of creating a basic h-entry

Hm, does your implementation works not with txt-only? I’m tried to write own but didnt test it: https://paste.ee/p/CopOR

@aelaraji@aelaraji.com Can you walk me through your testing process here and share example links etc? 🙏

@sorenpeter@darch.dk What are we testing?

Cleaned up my npm package for twthash; made it CommonJS compatible, added more documentation and even a test. Current version is 1.2.2

test post EDIT

I sent a few local tests, could you help me check if you see https://eapl.mx/twtxt.txt in your log file?

If you want more eyes on the agent, you can tell tell me, as I was thinking on something similar to catch those ‘following requests’.

Yarn spoiler test:

! foo

@prologic@twtxt.net had to get Compiz from the edge/testing repo, but I believe that you can do without it. Xfce’s default Alt+Scroll thing works out of the box.

testing the bluesky cross-poster i added into my silly python script for posting status updates

testing the bluesky cross-poster i added into my silly python script for posting status updates

testing the bluesky cross-poster i added into my silly python script for posting status updates

@aelaraji@aelaraji.com You could use https://lyse.isobeef.org/tmp/twthash.py to generate twt hashes. I cobbled that together in order to generate test data for my client.

test? asdf 3ae3hqa

test?

@movq@www.uninformativ.de Oh, cool. Larger than the the workers. I don’t know the actual size of this test tube, but when this is a regular sized one, the queen is still not that big.

I’ve been testing our new APRS digipeater, that allows us to report our geographic position via radio.

@eapl.me@eapl.me Neat.

So for twt metadata the lextwt parser currently supports values in the form [key=value]

https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/parser_test.go#L692-L698

After testing Vivaldi for a couple of weeks I am convinced this is a great browser and to support the team behind it, I decided to start sending them a couple of Euro monthly, just to keep the momentum going.