@kiwu@twtxt.net after you upload, make sure the audio file looks like this:

And it will work.
And here we go! Yup, hash has seven.
Testing jenny. You should probably ignore this, and the next twtxt.
@rdlmda@rdlmda.me that’s odd. In here is similar, but not random. All it takes is some rain, and then flip a coin: we may, or may not lose power.
Third power failure in two weeks. Every time a different apartment loses power at the same time as mine. I hope the power company is able to find the cause.
@prologic@twtxt.net it does! it wont let me do it like that tho
@lyse@lyse.isobeef.org no dice. Same.
Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).
@movq@www.uninformativ.de I don’t think it is anything you are doing wrong. I think it is on @prologic@twtxt.net side. I am getting the exact same result, but I never cloned that repository. Maybe it worked fine at certain point, when @lyse@lyse.isobeef.org cloned it, but I doubt brand new users can get through.
For the record, the third thing is to activate agent forwarding. In ~/.ssh/config:
Host git.mills.io
ForwardAgent yes
** WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to “store now, decrypt later” attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html
😱😱😱
@lyse@lyse.isobeef.org Changing the user name helped, it now says Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).
Here’s a debug log, @prologic@twtxt.net, perhaps you could take a look at this 🙏: https://movq.de/v/116c5f514b/clone2.txt
(Might be a silly mistake on my part. Wrong remote path or something?)
@rdlmda@rdlmda.me LOL. Do it, do it!
@lyse@lyse.isobeef.org “deep layers of the Mills infrastructure” LOL.
@rdlmda@rdlmda.me it is called, in Spanish, “the mother”. It is created through a bit (not by much) effort, and kept as a starting point. Just like Asian cuisine has dishes that never cool, always cooking leaving always a base on it.
How do you think a lathe (and just about any tool, etc.) is done? Yup, in part by using a lathe. 😅
@bender@twtxt.net Somehow, the enshittificator himself does not have to deal with enshittification in his own life. In fact, his job gets better with the internet! This can only mean one thing, we all have to becom…
@falsifian@www.falsifian.org Congrats, mate, no sleep at night anymore! ;-D That’s a cool age measuring blanket. Haven’t seen something like that before.
Btw. the index.html includes an out of place </ul>. And I just wanna let you know that the full-size photos don’t load for me over here across the pond. They always run into a timeout after a few slooow percent. But no worries. :-)
@movq@www.uninformativ.de @bender@twtxt.net You need a running SSH agent in order to make it through the deep layers of the Mills infrastructure: After ssh-add, git pull always works for me.
And contrary to what the UI shows, the username git always has to be replaced with your own one.
For what is worth, I get the same thing when trying over ssh. 🤷🏻♂️
@prologic@twtxt.net network is very secure! 🤪
@movq@www.uninformativ.de just use https instead:
git clone https://git.mills.io/yarnsocial/twtxt.dev.git
https://www.youtube.com/watch?v=T4Upf_B9RLQ
“A proud tradition, but it is hard work. Enter… The Internet!”
Anyone else having trouble pulling from git.mills.io? 🤔
$ g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
Cloning into 'twtxt.dev'...
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.
The key verification function on https://git.mills.io/user/settings/keys says I’m using the correct key.
This also looks good:
$ GIT_SSH_COMMAND="ssh -v" g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
...
debug1: Authentications that can continue: publickey
debug1: Offering public key: /home/user/.ssh/keys/key-millsio ED25519 SHA256:nVNT... explicit
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.
Does it work for you, @lyse@lyse.isobeef.org @prologic@twtxt.net?
@falsifian@www.falsifian.org My condolences. I mean, errr, congratulations! 😅
@falsifian@www.falsifian.org congratulations mate! Let it be joy, and happiness! Enjoy every moment. Time will fly, and next you know you will be a curmudgeon who knows nothing. 😅
@falsifian@www.falsifian.org Congrats! 🥳
Hmm I think it’s a bug in the Javascript. It’s meant to be 
I turned off indexing and anonymous access i think? 🧐
@bender@twtxt.net Lets bend it!
Hello twtxt! I still exist. I have a baby now and put some pictures at https://photos.falsifian.org/ . Album HTML loosely inspried by @lyse@lyse.isobeef.org
@kiwu@twtxt.net those moods don’t play, they download. 😩
today’s mood Ghost.Mp3
@thecanine@twtxt.net sorry to hear that, mate. Don’t worry, something better will come up. After all, it has got to be easy to beat Android, right? :-)
@movq@www.uninformativ.de and @lyse@lyse.isobeef.org rock, and thank you for taking the initiative to get this done. @prologic@twtxt.net, what say you?
Let’s finalize https://git.mills.io/yarnsocial/twtxt.dev/pulls/28/.
@lyse@lyse.isobeef.org We’ll see. Hasn’t really happened in the past. 🤔
@thecanine@twtxt.net are you referring to the “WE FUCKING WON!” twtxt?
@movq@www.uninformativ.de Now, they’re always cloning the entire repo I suppose. X-(
@arne@uplegger.eu (Arrrrrgh, bitte lass’ mich nicht noch ein Spielzeug kaufen … 😂)
Now that Winter has come to an end, I’m realizing that the default amber color scheme of my widget toolkit might be problemaic.
Readability isn’t great when the sun is blasting through the windows. 🥴
I should probably make this full themeable by the user …
(Haven’t worked on this code in a month, sadly.)
as things are now in fact even worse
You mean this, right?
Contrary to a vague mention of a possible “advanced flow” that may eventually allow “experienced users to accept the risks of installing software that isn’t verified”, Google’s description of the program continues to state plainly that:
Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices
Until such time that they have shown evidence that it will be possible to bypass the verification process without undue friction, we must believe what is stated on their official page: that all apps from non-registered developers will be blocked once their lock-down goes into effect.
Putting obstacles in their way: To make scraping my code slightly less trivial, the repos on my website now only show the newest 15 commits, e.g.: https://movq.de/git/katriawm/log.html
Last year, I made a huge mistake. I repeated on here, what multiple sourcea at Google told me, and what is to this day, written on their blog about Android.
I failed to take into consideration, that people who work at Google, often just lie, or present things intentionally vaguely, so they do not have to follow through with their promises.
I would like to apologize to everyone, who took my previous posts here, as assurance software not explicitly approved by Google, will continue working on Android, past this year (or even just a couple months from now) and that everything has been resolved, as things are now in fact even worse, than they were before. To follow the current state of “Open Android”, please check: https://keepandroidopen.org/
@rdlmda@rdlmda.me I never saw the point of a registry to be honest, as it defeated the point of what I believed to be a truly decentralised non-social social ecosystem. What can and does work however is a search engine and crawler. I used to run one, but I took it down, mostly because it got expensive to operate, at least the implementation I built… Maybe one day i’ll try again with a SQLite backend.
What @bender@twtxt.net said ☝️
@rdlmda@rdlmda.me We see and read yout mutterings just fine 😅
@bender@twtxt.net I agree, I had oats in yoghurt for dinner. :-)
@rdlmda@rdlmda.me You might or might not find this useful: https://lyse.isobeef.org/tmp/twthash.py