@aelaraji@aelaraji.com Oh, sorry it’s a typo. Also developer previously worked in vk (making mobile app afaik). Not he hates him xD

Hey @kat@yarn.girlonthemoon.xyz If you see this, I’m aware of a bug. I’m trying to figure it out and fix it. bare with me 🤗 It is what’s causing things to “stall” and to have to “restart”. Sorry 😞

@prologic@twtxt.net exciting!!!!!! i’m SO SORRY i didn’t get to doing the migration for my instance though - i’ve been really busy! T__T but i hope to get to it sometime this week i really wanna upgrade i think i’m just a bit nervous for whatever reason lol

@thecanine@twtxt.net Sorry, but you were expecting what now?! 🤣

I also fundamentally do not believe in the notion that Twtxt should be readable and writable by humans. We’ve thrown this “argument” around in support of some of the proposals, and I just don’t buy it (sorry). As an analogy, nobody writes Email by hand and transmits them to mail servers vai SMTP by hand. We use tools to do this. Twtxt/Yarn should be the same IMO.

@movq@www.uninformativ.de oi, that has to be a bot. AI bot? Maybe not, but still a bot. I see this becoming more and more of an issue, sorry to say…

@twtxtory@twtxtory.adn.org.es sorry, it isn’t. After you enter the password, it takes a very long time to render anything. I don’t have the patience to wait. Longest I waited is 3 minutes, and nothing. Super extremely slow.

@prologic@twtxt.net oh, sorry, you are right. Beautiful 404. The most beautiful 404 I have ever seen. Tremendous! 🤪

@bender@twtxt.net Sorry! 🤣

Sorry, more pixels:

@abucci@anthony.buc.ci totally my fault sorry 😞

Oh hey @rrraksamam@twtxt.net 👋 Welcome back! 🙌 Sorry about the data loss 🤯

I don’t think I’d personally be worried about migrating, just re-fetch. Sounds cleaner anyway?
Sorry I’m late to the party!

Oops, I think this pod (twtxt.net) just sync ~1k missing root twts with god only knows which peers 🤦‍♂️ I forgot a couple of important key things:

• Only coverage with a subset of peers
  
• Only converge with trusted peers
  

Fuck me 🤣 Ooops. Sorry!

@movq@www.uninformativ.de no no it’s ok i say it because it’s true also it’s funny to me hahah! don’t be sorry

@kat@yarn.girlonthemoon.xyz Ouch. 🥴 Alright, that’s not so great then, sorry. 🫣🥴

@thecanine@twtxt.net I’m so sorry I fucked things up 🥲 I hope you can trust I’ll try to do a better job of backups and data going forward 🤗

Show HN: Seven39, a social media app that is only open for 3 hours every evening
I built this site as a quick test if a time boxed social media experience feels better than an endless one. So far I’ve just been using it with friends and it feels nice, but it seems like it is time to bring it to a larger audience.

Let me know what you think! It is just based on EST for now, sorry.

Comments URL: https://news.ycombinator.com/item?id=43328095

Points: 500

# Comments: 253 ⌘ Read more

@bender@twtxt.net Sorry to disappoint (again): https://blogs.nasa.gov/planetarydefense/2025/02/24/latest-calculations-conclude-asteroid-2024-yr4-now-poses-no-significant-threat-to-earth-in-2032-and-beyond/

@andros@twtxt.andros.dev yeah, sorry I couldn’t get back to you sooner. I’ve already made an account on codeberg in order to file in an issue but, I just can’t get myself to concentrate with everything going on with the family lately. I’ll do my best and get things done properly and soon

@sorenpeter@darch.dk Sorry, I realized that shortly after posting. Here’s another attempt to post the images:

Image

Image

Image

Three years of ephemeral NixOS: my experience resetting root on every boot
We had a bit of a bug caused by changes we made to make quotes look better, but we’ve fixed it now, so we’re back on track (you may need to do a force-reload in your browser). Sorry for the disruption – and if you want to stay up-to-date on such issues next time it (inevitably) happens, you should follow the OSNews Fedi account (or just bookmark it without following it, if you’re not … ⌘ Read more

Sorry Simba, i had to😭 ⌘ Read more

@prologic@twtxt.net Sorry to hear that.

@lyse@lyse.isobeef.org oh yeah i forgot to mention i changed the domain to pinktape lol! sorry about that! https://pinktape.girlonthemoon.xyz/

HI SORRY I DISAPPEARED THINGS HAVE BEEN HECTIC AND WILL CONTINUE TO BE HECTIC FOR ANOTHER WEEK

Thank you @bender@twtxt.net Much appreciated 🙏 and Sorry you/anyone had to read that…

I’m usually comfortable keeping my hardship to myself, most especially AWAY from the internet; an act of kindness of sorts towards others, “Everyone’s got their own problems to worry about” kind of thing.. But maaan am I starting to believe creating a twitter account would be a healthy decision 🤣🤦 Read nothin’ out there, just a one way echo chamber of sorts to let that shi_ out of my chest. It seem that’s what everyone else’s been using it for all this time.

A Bsky would be even better! 😂 I’d get to shi_ post and yap all I want, allll the way from terminal and never ever have to look back at it or whatever comes out of it. But I digress…

I FU_ing despise this … whatever this is. I wish I could just wake up in some sort of parallel universe where everything is just sunshine and rainbows, alas, life would be just as meaningless.

and sorry you had to read this if you did.

thanks to prologic i now know i can post video here. sorry for bringing idol fancams to this humble network do you still love me

Video

@lyse@lyse.isobeef.org Oh! no need to be sorry and feel free to keep at it if it helps, I don’t mind. It’s just that I’m always on the lookout for corpo-bots and crawlers slipping through the cracks (a fun little game of sorts) 😅 the only thing I let them see is a robots.txt telling them to :diffoff

Also, I’m curious about the invalid lines in my feed. is it something I should lookout for in future?

@andros@twtxt.andros.dev Sorry I missed your messages to #twtxt on IRC. There are people there, but it can take several hours to get a response. E.g. I check it every day or two. I recommend using an IRC bouncer. To answer your question about registries, I used a couple of registries when I first started out, to try to find feeds to follow, but haven’t since then. I don’t remember which ones, but they were easy to find with web searches.

** Year in review, 2024 **
As a treat, I figured I could write a year in review kinda thing, too. In no particular order here are some reflections organized into some mostly sensical categories.

Since recovering from my brain bleed and the subsequent repair procedures, this year I’ve enjoyed getting back into a routine of exercising. I’ve never been one to track numbers, or reps, or distances — I mostly exercise because I enjoy doing it. This year I got back into going for regular short runs, very long walks (sorry aging d … ⌘ Read more

sec-t 2024
[This has been in my draft folder since September. Sorry! It’s been a
few months with ups and downs, mostly downs. Energy to spend time on
blogging has been low. Hell, energy to do much of anything has been
low. I’m trying to clean out the drafts folder and will post more
stuff.]

I attended the security conference sec-t 2024 in Stockholm the other
week. I held a presentation during the Community Event, Wednesday
September 11: “Verifying the Tillitis TKey”.

The TKey uses a novel way of helpin … ⌘ Read more

I am so sorry.

@movq@www.uninformativ.de i’m sorry if I sound too contrarian. I’m not a fan of using an obscure hash as well. The problem is that of future and backward compatibility. If we change to sha256 or another we don’t just need to support sha256. But need to now support both sha256 AND blake2b. Or we devide the community. Users of some clients will still use the old algorithm and get left behind.

Really we should all think hard about how changes will break things and if those breakages are acceptable.

Sorry but i dont undestand b. New feed author? But why?

@bender@twtxt.net

Sorry, you’re right, I should have used numbers!

I’m don’t understand what “preserve the original hash” could mean other than “make sure there’s still a twt in the feed with that hash”. Maybe the text could be clarified somehow.

I’m also not sure what you mean by markdown already being part of it. Of course people can already use Markdown, just like presumably nothing stopped people from using (twt subjects) before they were formally described. But it’s not universal; e.g. as a jenny user I just see the plain text.

@prologic@twtxt.net sorry but nope. Neither jenny, nor yarnd supports it at all. This was treated as a thread because I picked one of @falsifian@www.falsifian.org’s twtxts (with the “old subject”), and replied to it (hence starting the thread).

@lyse@lyse.isobeef.org Sorry, I don’t think I ever had charset=utf8. I just noticed that a few days ago. OpenBSD’s httpd might not support including a parameter with the mime type, unfortunately. I’m going to look into it.

@jmjl@tilde.green howdy! Sorry for mistaken you with https://blog.nfld.uk/ (jlj), but glad to connect. Cheers!

@movq@www.uninformativ.de Thanks! Looking forward to trying it out. Sorry for the silence; I have become unexpectedly busy so no time for twtxt these past few days.

@stigatle@yarn.stigatle.no @xuu@txt.sour.is @lyse@lyse.isobeef.org “Not cool”? I was receiving many broken (HTTP 400 error) requests per second from an IP address I didn’t recognize, right after having my VPS crash because the hard drive filled up with bogus data. None of this had happened on this VPS before, so it was a new problem that I didn’t understand and I took immediate action to get it under control. Of course I reported the IP address to its abuse email. That’s a 100% normal, natural, and “cool” thing to do in such a situation. At the time I had no idea it was @xuu@txt.sour.is .

The moment I realized it was @xuu@txt.sour.is and definitely a false alarm, I emailed the ISP and told them this was a false positive and to not ban or block the IP in question because it was not abusive traffic. They haven’t yet responded but I do hope they’ve stopped taking action, and if there’s anything else I can do to certify to them that this is not abuse then I will do that.

I run numerous services on that VPS that I rely on, and I spent most of my day today cleaning up the mess all this has caused. I get that this caused @xuu@txt.sour.is a lot of stress and I’m sincerely sorry about that and am doing what I can to rectify the situation. But calling me “not cool” isn’t necessary. This was an unfortunate situation that we’re trying to make right and there’s no need for criticizing anyone.

@prologic@twtxt.net Sorry, my messages don’t get included in the current convo unless I tag you. Guess something gets lossed in translation with this weird posting issue. ANYWAY, it is rather perplexing. Clearly only an issue on my Pod, but what could the source of it be 🤔

Yeah sorry just realised, but just checked again and the referrer is the same (/post) on either the POST or the GET 🤔

Haha, yeah sorry about that, I wasn’t even trying to nuke the database either but it worked out that way 😩

Room Code
⌘ Read more

Room Code
⌘ Read more

[Fixed] Feedback Form Wizard
The Feedback Form Wizard
has been fixed so that it can now, once again, create the CAPTCHA versions (ReCAPTCHA and hCaptcha) of the script.
Apparently, somewhere along the line, I seem to have broken it during one of my internal updates. I’m very sorry
for the inconvenience. Note: you do not have to recreate your script if you successfully generated it before.
(The problem was that under certain conditions, the wizard choke … ⌘ Read more

…det blev så til det her etch-a-sketch-agtige tegneprogram.

(Sorry for mørk video - jeg kan filme noget i dagslys om lidt). ⌘ Read more

Sorry for that RSS twtxt noise