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

@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.

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 😩

@jmjl@tilde.green I’m sorry that I’m not super knowledgeable about alternatives to jmp.chat but I’ll tell you what I know.

You’re probably right about jmp.chat not working for you, at least as it is now. You can only get US and Canadian phone numbers through it last time I checked, so if you’re not in either of those countries you’d be making international calls all the time and people who wanted to call you would be making international calls too.

I’ve seen people talk about using SIP as an intermediary: you can bridge SIP-to-XMPP, and bridge SIP-to-PSTN (PSTN = “packet switched telephone network”, meaning normal telephone). You can skip the SIP-to-XMPP side if you’re comfortable using a SIP client. I don’t know very much about SIP or PSTN so I am not sure what to recommend, but perhaps this helps your search queries.

There are a fair number of services like TextNow that let you sign up for a real telephone number that you can then use via their app (I wouldn’t use TextNow–they had tons of spyware in their app). I don’t know if that kind of service works for you but if it does perhaps you’d be able to find one of them that isn’t horrible. This page (https://alternativeto.net/software/jmp-chat/) has a bunch of alternatives; I can’t vouch for any of them but maybe it’s a starting point if you want to go this route.

Good luck!

@prologic@twtxt.net hmm, now I get this:

$ ssh -p 2222 -i PRIVATE_GITHUB_KEY GITHUB_USERNAME@cas.run add | sh
sh: 135: docker: not found

The quickstart says:

## Quick Start

  ssh -p 2222 cas.run add | sh

so that’s why I tried this command (I had to modify it with my key and username like before)

Edit: 🤦‍♂ and that’s becasue I don’t have docker on this machine. Sorry about that, false alarm.

@lyse@lyse.isobeef.org, hey, thank you! :-) Yeah, I am abusing the headers on ferengi.one, sorry about that. Will change it. You know, because Lyse.

Microsoft apologizes for Windows, returns to DOS
“We’re really sorry about that whole GUI thing.” ⌘ Read more

@movq@www.uninformativ.de, is removing the hash from the body of the twt on the TODO? I read it, but I am unsure if it is there already, or not. 🙈 Sorry if it is, and I failed to spot it!

@fastidious@arrakis.netbros.com sorry. the fix was around having a mention in parenthesis like (yo @prologic@twtxt.net)

Now talking about HomePod Mini. Not interested, sorry.

@movq@www.uninformativ.de
Sorry! 🙈

@prologic@twtxt.net I knew you were short sided from day one I saw Yarn. On desktop everything is huge, and I assumed it was to cater short-sightedness. Also, you have enabled underlines on buttons on iOS, bold and bigger fonts, etc., so that was also a give away. Sorry if I digress, but, glasses wouldn’t help? I have to wear mine all the time, otherwise I am also near blind myself!

@lyse@lyse.isobeef.org (#hut4mnq) I am so sorry for you. I left my Java job for Go. Though through “restructuring” its become a Python job.

@prologic@twtxt.net lol.. sorry about the spam

@lucidiot@tilde.town haha oops! sorry about that. It’s fixed now.

@kas@enotty.dk Sorry I never replied. Haven’t quite gotten up to speed, here, but investigating the blog issue and twistnik!

@kas@enotty.dk Sorry, i haven’t tested the build-script, should be fixed now #termpub

Im sorry twtxt, I dont mean to ignore you… things are fine here, except my brain is made of snail poop

iOS autotweet test #sorry

@durcheinandr@durcheinandr.de Sorry, no idea then. I have a ticker with news agencies like dpa, afp etc. at work but that’s more like a firehose.

@trevor@destroyed.today, @tx@0x1A4.1337.cx Sorry, too many new users! :) @tx@0x1A4.1337.cx suggested printing the messages to stdout.

Yeah, sorry, i meant epoch, which doesn’t count leap seconds.

You can find my twtxt feed at https://domgoergen.com/twtxt/mdom.txt Sorry for the trouble!

Just added a search field for users and tweets at https://roster.twtxt.org And sorry for just tweeting about new features…

@dracoblue@dracoblue.net Sorry, but what tweet are you referring to? I have no idea what sounds great… We need a way to reference tweets!

@quite@lublin.se Ah sorry, should have checked the commit. #twet is officially the first twtxt client with colors! :)

As german speaker i missed the unintended meaning of txtwat. Sorry, if anybody was offended. The project is now called txtnix.