The wording can be more subtle like “This feed have not seen much activity within the last year” and maybe adding a UI like I did in timeline showing time ago for all feeds

Image

I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.

The “not receiving replies” could partly be fixed by implementing a working webmentions for twtxt.txt

@prologic@twtxt.net pretty nothing berger. The “blowout” was pretty tame coming from Linus kill yourself now. The world will be a better place” Torvold.

The issue was a dev making a “fix” that didn’t have a documented problem. They reused some specific low level functions they did not understand the reason they were made.

@prologic@twtxt.net I’ve had a Teracube phone for about 3 years now. Theirs comes with a guarantee of 4 years–if something that’s covered breaks, you send the phone to them and they fix it and send it back, or they send you a new one. I took advantage of that last year when the screen broke; their tech support even helped me figure out how to wipe the phone when the screen didn’t display anything. Pretty painless all around. Have to say I’ve been very happy with it. It doesn’t have the top-end features that new big company phones have, but I don’t want those features so that’s not an issue for me. I dunno if it’s available in Australia or if it’s just a US thing.

@mckinley@twtxt.net Yes, I’m still with jmp.chat, and still very happy with them overall. Their beta period ended and their pricing increased a bit, so that’s worth a bit of consideration. I also managed to get one of their eSIMs. I’m slightly less happy with that aspect of their service, though they seem to be actively working on improving it and I knew in advance this was an early beta kind of thing and likely to have issues.

The only unreliability with calls that I’ve noticed was traceable to the unreliability of my own internet connection. I’ve confused incoming calls by simultaneously making and taking calls from the computer and the phone, but I think it’s understandable that problems might arise and that’s not a real use case for me. Once or twice I did not receive a text transcription of a voice mail, but the support is usually quick to address things like that.

I host my own XMPP server and have for a good decade now, and that’s what I use with jmp.chat. I can’t speak to the quality of their hosting options.

Group texting works fine for me if one of the other parties initiates the group text. I haven’t tried to initiate my own group text in well over a year; last time I did, it didn’t work. That may or may not be a problem for you, and it may or may not have been fixed by now. Worth investigating more if it’s important. I should also say I’ve only ever used group texts with 3 participants, and can’t speak to what happens if there are more nor whether there are upper limits.

Group texts don’t use MUC. Rather, they use a special syntax in the JID, something like “+1XXX,+1YYY,…,+1ZZZ@cheogram.com”, where the + and , are required, the XXX, YYY, through ZZZ are the phone numbers (no dashes or other special chars just digits), and the @cheogram.com at the end is required.

I recommend the cheogram app if you’re on android. It has a lot of nice features on top of the Conversations base. I use gajim on my (linux) computer and it works well with jmp.chat.

I’m happy to answer other questions if you have them!

My UPS failed the other day and I don’t know what’s wrong with it yet. Very 😱 until I get that fixed or replaced.

@xuu@txt.sour.is LOL omfg.

This is the absurd logical endpoint of free market fundamentalism. “The market will fix everything!” Including, apparently, encroaching floodwater.

I do have to say though, after spending awhile looking at houses, that there are a crapton of homes for sale for very high prices (>$1 million) in coastal areas NASA is more or less telling us will be underwater in the next few decades. I don’t get how a house that’s going to be underwater soon is worth $1 million, but then I’m never been a free market fundamentalist either so 🤷 Maybe they’re all watertight.

I’m not super a fan of using json. I feel we could still use text as the medium. Maybe a modified version to fix any weakness.

What if instead of signing each twt individually we generated a merkle tree using the twt hashes? Then a signature of the root hash. This would ensure the full stream of twts are intact with a minimal overhead. With the added bonus of helping clients identify missing twts when syncing/gossiping.

Have two endpoints. One as the webfinger to link profile details and avatar like you posted. And the signature for the merkleroot twt. And the other a pageable stream of twts. Or individual twts/merkle branch to incrementally access twt feeds.

I have found the issue with this very subtle bug.. the cache was returning a slice that would be mutated. The mutation involved appending an item and then sorting. because the returned slice is just a pointer+length the sort would modify the same memory.

          CACHE         Returned slice          
original: [A B C D]     [A B C D]
add:      [A B C D] E   [A B C D E]
sort:     [E A B C] D   [A B C D E]

fix found here:
https://git.mills.io/yarnsocial/yarn/pulls/1072

@lyse@lyse.isobeef.org, fixed. 🙈

@lyse@lyse.isobeef.org ¯\_(ツ)_/¯ fixed your arm.

If the only thing you write in your changelog is “Fixes and improvements”, why bother with a changelog at all?

Boot drive failed on the server that hosts my Gemini capsule’s headless repo. Now there will officially be no updates until it’s fixed!

@prologic@twtxt.net, who calls me name when I am busy profiting? 😂 In a less serious note—because nothing is more serious than making profit, of course—yes, it seems your avatar issue has been fixed. I am kind of sad, I looked forward each day to see which random one was going to show. LOL.

More #pixelblog‘ing - today wotking on fixing all the semi-hardcoded paths an moving them to config.php

Image

@prologic@twtxt.net you get your infra all fixed up?

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

@fastidious@arrakis.netbros.com fixed this one yesterday. https://git.mills.io/yarnsocial/yarn/pulls/502

@stackeffect@twtxt.stackeffect.de

now Apache also announces content-type: text/plain; charset=utf-8

Well, that fixed things. 🥳

@jlj@twt.nfld.uk
While at it, fix this one too? You have me at netbros.com, but I am somewhere else. 😆

@movq@www.uninformativ.de
Do I need to do a search and replace on my feed to fix old entries? Thanks for quick fix!

On the blog: Let’s Fix…Facebook https://john.colagioia.net/blog/2021/10/17/facebook.html #lets-#fix #facebook #socialmedia

@prologic@twtxt.net Hopefully this URL change fixes things. Otherwise I am lost; don’t know what’s going on. 😩

It did! And I fixed the bug last night. And now I’m curious how your pod deals with spam. 👆🏼

Fixed another bug in my finger client: rfc1288 says lines have to end with crlf, but I was just sending lf.

Fixed a bug. Found a new bug in yesterday’s work. Fixed that bug.

Fixed the race in tw. Mostly; now it’s just while tw/r is running. Close enough.

@prologic@twtxt.net yah I’ll get a fix out soonish

@prologic@twtxt.net fixed.

Got to fix some scripts, today. Whee…