@falsifian@www.falsifian.org That’s awesome! And nice Avatar! 👌
@stigatle@yarn.stigatle.no Ahh cool! 😎
At this point I’m thinking of migrating away from OnlyDomains and choosing a different registrar. If OnlyDomains can’t even do something as simple as maintain their own fucking domain name, how am I supposed to trust them as a service/registrar of my domains?! 🤔 – Not only that, but recently they’ve put all their domain prices up too on a bunch of TLD(s).
@bender@twtxt.net That ain’t the half of it. The worst part is, they (support) don’t give a crap, seem to be poorly trained in “incident management” and you can’t even tell anyone at the company about this (that cares) 🤦♂️
Not only that, but how embarrassing is it for a domain registrar to not be able to get domain management right? Support tell me things like:
We only have onlydomains.com we don’t use onlydomains.com.au
To which I reply:
No, you are wrong. I’ve been a very long-term customer and your portal has always been available on both domains. You don’t know your own company’s history.
Holy moly! 😱 It’s still down and has been over night. This has probably been down for longer hmmm 🧐
@stigatle@yarn.stigatle.no Is saving the password a good idea security-wise? Or do you save/load it from the user’s password manager using an API to do so? 🤔
@slashdot@feeds.twtxt.net Well no shit! But not only “agile” but this stupid over-uses thing called “micro services” 🤦♂️
@falsifian@www.falsifian.org You need an Avatar 😅
@falsifian@www.falsifian.org Nope we don’t! yarnd
only has a limit (configurable) to prevent abuse really.
@falsifian@www.falsifian.org Welcome to Yarn.social 🥳
Found out today, that the registrar that I use Only Domains’s AU front door is DOWN. That is https://onlydomains.com.au
$ host -t A onlydomains.com.au
onlydomains.com.au has address 198.50.252.65
$ curl -v https://onlydomains.com.au/
* Trying 198.50.252.65:443...
* connect to 198.50.252.65 port 443 failed: Connection refused
* Failed to connect to onlydomains.com.au port 443 after 222 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to onlydomains.com.au port 443 after 222 ms: Couldn't connect to server
That’s scrutiny is definitely something I wanna look at running. 👌
@mckinley@twtxt.net oh I see! Yeah, health checks looks like something I wouldn’t have any need to run myself or use because most of my background jobs or tasks run in my swarm cluster anyway and I don’t really have that many background or cron type jobs in the first place.
Hmmm looks like I started the repo and previously found it “interesting” 🤔
@mckinley@twtxt.net Is this open source and someyhing you run locally on the machine? 🤔 No Cloud?
@aelaraji@aelaraji.com Fuck no it was unintentional 🤣 Oops! Too late to fix now!
@lyse@lyse.isobeef.org I’ll let him know 😅
OTS works Soo great! 👌 Juat got my mother to use it to share some creds so I could take over her web hosting needs 🤣
Fixed!
@bender@twtxt.net Oh! 🤔 Hmmm I’d better check the data
directory. Not sure what happened there 😢
@bender@twtxt.net He’s doing alright 👍 Thanks for ask’n ! 🙇♂️
Okay. The house is properly cleaned up. There are 77 users on this pod, 34 inactive and 12 active. That’s a good effort I think. Maybe some of those folks that haven’t been around for a while, but were pretty decent folks to talk to and interact with may come back. For example @off_grid_living@twtxt.net 😅
@aelaraji@aelaraji.com I do and we (royal asshole we) still use and abuse people’s data even today right?! 🤣
Why should or would I want to join that evil fucked ip crowd 😅
To me as a self-hosted enthusiast its noise and wasteful.
@lyse@lyse.isobeef.org Samw here 🙄 I hardly ever take much time off 😱 🤦♂️
make test
. I will look into that.
@lyse@lyse.isobeef.org Thank you! 🙏
Hmmm even this thread is weirdly inconsistent and there should be no reason for it hmmm 🤔
@xuu [confirmed]
@bender@twtxt.net Okay, easy enough to do. And I agree ☝️
@xuu Merged!
@lyse@lyse.isobeef.org Yeah @xuu has a Paul request to fix this already so I’ll have a look at that and get that merge soon.
@bender@twtxt.net you mean to say always show the domain part for mentions even on the same pod?
@stigatle@yarn.stigatle.no very nice 👌
@bender@twtxt.net Hmm none whatsoever in the feed they are teh same:
2024-08-03T23:24:20Z (#iztis3a) @<bender https://twtxt.net/user/bender/twtxt.txt> LOL 🤣
2024-08-03T23:24:54Z (#thfnzga) @<bender https://twtxt.net/user/bender/twtxt.txt> LOL 🤣
However just noticed both of these now render the same again, weird 🤔
Many thanks @lyse@lyse.isobeef.org 🙏
Or rather reverted lextwt (for the time being)
Fixed! 💪
@bender@twtxt.net ROFL 🤣 So now you want Twts to be analyzed for secrets, keys and what not before posting and some kind of DLP ?! 😱 Farrrrrkkkkk 🤣
Scratch that. Bug found! 🐞
@lyse@lyse.isobeef.org More on #yarn.social on LiberaChat (IRC) obviously 🙄
@lyse@lyse.isobeef.org I think it’s these lines of code: https://git.mills.io/yarnsocial/yarn/src/commit/5101ec240ddb0e5e39809bf8a7b847508b3ac298/internal/feed.go#L162-L166
It’s also (expectedly) in the feed file on disk:
2024-08-04T21:22:05+10:00 [foo][foo=][foo][foo=]
@lyse@lyse.isobeef.org Holy fucking shit! You’re right! You got me out of bed for this one, I spun my local dev instance and entered a Twt with [foo]
and ended up with [foo][foo=][foo][foo=]
wut da actual fuq?! 🤔
The reason I think this is some kind of attack is based on the repeated content and some of its uniqueness 🤔 This is so uncharacteristic if both victims 🤔
@stigatle@yarn.stigatle.no Nice one 🥳 Kooking really good! 👌
@lyse@lyse.isobeef.org I’m not sure this is a bug to be honest? What possible code could cause this?! 🤔
@lyse@lyse.isobeef.org Thank you! 🙏
How do the feeds look on disk? Do they already contain this bracketed text?
Because the handle just serves the Twtxt file directly.