My client is twet which i grabbed at https://github.com/jdtron/twet

(#5uon66q) @doesnm LOL sorry which client are you using? 🤔 You can of course have a say! There aren’t that many active/used clients at the mo …
@doesnm @doesnm.p.psf.lt LOL sorry which client are you using? 🤔 You can of course have a say! There aren’t that many active/used clients at the moment, and I forget which one you’re using 🤣🤣 ⌘ Read more

Lol only i use discontinued client? (with patches but i’m lost sources so they “proprietary”)

(#ot56hla) For the record; we consider the new authority on the Twtxt spec(s) going forward (has been for some years actually) to be implement …
For the record; we consider the new authority on the Twtxt spec(s) going forward ( has been for some years actually) to be implementers / primary maintainers of widely used clients. To date that is:

• yarnd @prologic (me and others)

• jenny [@movq @www.uninformativ.de](https://twtxt.net/external?uri=https://www.uninformativ.de/twtxt.txt&nick=movq … ⌘ Read more

Dragonfly v2.2.0 has been released
Dragonfly v2.2.0 is released! 🎉🎉🎉 Thanks the contributors who made this release happend and welcome you to visit d7y.io website. Features Client written in Rust The client is written in Rust, offering advantages such as ensuring… ⌘ Read more

What’s a reasonable per second or per minute rate limit that I could apply in general at my edge proxy for all clients? (no matter what) … L …
What’s a reasonable per second or per minute rate limit that I could apply in general at my edge proxy for all clients? ( no matter what) … LIke a good reasonable upper bound? 🤔 ⌘ Read more

(#o2ru6pq) @doesnm It is the same API that yarnc the command-line client uses.
@doesnm @doesnm.p.psf.lt It is the same API that yarnc the command-line client uses. ⌘ Read more

(#gjl3gwq) @andros What do you mean by API? yarnd (which powers Yarn.social pods like twtxt.net) does have an API, however that API is desig …
@andros @twtxt.andros.dev What do you mean by API? yarnd ( which powers Yarn.social pods like twtxt.net) does have an API, however that API is designed for clients to interact with the pod and the user’s account and feed. e.g: there is a command-line client called yarnc and I used to maintain a mobile native app ( … ⌘ Read more

(#v3q6xuq) Could this be the Emacs client I’ve heard about? 🤔
Could this be the Emacs client I’ve heard about? 🤔 ⌘ Read more

(#v3q6xuq) @lyse I wouldn’t know sadly. I don’t pay attention to the actual clients themselves as you know. I just let yarnd do it’s thing.
@lyse @lyse.isobeef.org I wouldn’t know sadly. I don’t pay attention to the actual clients themselves as you know. I just let yarnd do it’s thing. ⌘ Read more

(#vwonyga) @kat No worries! I consider Yarn.social to be really an ecosystem of clients, tools and services. Twtxt is the underlying exchange fo …
@kat @yarn.girlonthemoon.xyz No worries! I consider Yarn.social to be really an ecosystem of clients, tools and services. Twtxt is the underlying exchange format used and extended (See https://twtxt.dev) ⌘ Read more

(#dphjuwa) @kat Haha yeah I often use the CLI client to post things from the terminal! 👌
@kat @yarn.girlonthemoon.xyz Haha yeah I often use the CLI client to post things from the terminal! 👌 ⌘ Read more

**For my reference, but anyone else too… Creating a new Wireguard public/private key pair and bringing up a new client:

wg genkey | tee /e ...**
For my reference, but anyone else too… Creating a new Wireguard public/private key pair and bringing up a new client:

wg genkey | tee /etc/wireguard/private.key
cat /etc/wireguard/private.key | wg pubkey | tee /etc/wireguard/public.key

vim /etc/wireguard/wg0.conf
wg-quick up wg0

⌘ [Read more](https://twtxt.net/twt/vlbohoq)

(#grm3u6a) @sorenpeter@sorenpeter I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by …
@sorenpeter @darch.dk I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes. ⌘ Read more

(#2zve52q) @sorenpeter No I agree. I think if the feed doesn’t hint at a nick, just default to displaying the bare domain. These sorts of things …
@sorenpeter @darch.dk No I agree. I think if the feed doesn’t hint at a nick, just default to displaying the bare domain. These sorts of things btw need to go into a Client recommendations / guidelines. If someone wants to start drafting up such I doc I will fully support this and help shape it 👌 ⌘ Read more

What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?

What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.

@doesnm@doesnm.p.psf.lt So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld

(#b7mk3nq) @andros Oooh exiting, we haven’t seen a Twtxt client in a functional language yet 🤣
@andros @twtxt.andros.dev Oooh exiting, we haven’t seen a Twtxt client in a functional language yet 🤣 ⌘ Read more

(#ah5h6mq) @andros See – There isn’t really anythign specific about avatars or how big they should be, etc. The spec mostly talks about what’s …
@andros @twtxt.andros.dev See https://twtxt.dev – There isn’t really anythign specific about avatars or how big they should be, etc. The spec mostly talks about what’s possible and supported by clients and publishers of twtxt feeds. We have yet to write specific client/server recommendations. ⌘ Read more

Use ChatGPT by Phone by Calling 1-800-ChatGPT for AI Voice Answers & Communication
OpenAI, the company behind the popular ChatGPT artificial intelligence tool, has introduced a new phone-based ChatGPT client experience. By calling 1-800-ChatGPT (1-800-242-8478), you are able to have a phone conversation with ChatGPT to get AI answers by phone. Essentially the phone line for ChatGPT means that you can access and use ChatGPT entirely by voice, … [Read More](https://osxdaily.com/2024/12/20/use-cha … ⌘ Read more

JMP: Newsletter: JMP at SeaGL, Cheogram now on Amazon
Hi everyone!

Welcome to the latest edition of your pseudo-monthly JMP update!

In case it’s been a while since you checked out JMP, here’s a refresher: JMP lets you send and receive text and picture messages (and calls) through a real phone number right from your computer, tablet, phone, or anything else that has a Jabber client.  Among other things, JMP has these features: Your phone number on every device; Multiple phone numbers, one app; Free a … ⌘ Read more

JMP: Newsletter: Year in Review, Google Play Update
Hi everyone!

Welcome to the latest edition of your pseudo-monthly JMP update!

In case it’s been a while since you checked out JMP, here’s a refresher: JMP lets you send and receive text and picture messages (and calls) through a real phone number right from your computer, tablet, phone, or anything else that has a Jabber client.  Among other things, JMP has these features: Your phone number on every device; Multiple phone numbers, one app; Free as … ⌘ Read more

(#5zxfl5q) @xuu@xuu Built-in to what though? The spec? A client? A Serivce?
@xuu @txt.sour.is Built-in to what though? The spec? A client? A Serivce? ⌘ Read more

(#624dwtq) @xuu@xuu is there anything stopping in clients from supporting this as an optional feature?
@xuu @txt.sour.is is there anything stopping in clients from supporting this as an optional feature? ⌘ Read more

Kaidan: Kaidan 0.10.1: Media Sharing and New Message Marker Fixes
This release fixes some bugs.
Have a look at the changelog for more details.

Bugfixes:

• Fix displaying files of each message in appropriate message bubble (melvo)
  
• Fix sending fallback messages for clients not supporting XEP-0447: Stateless file sharing (melvo)
  
• Fix margins within message bubbles (melvo)
  
• Fix hiding hidden message part (melvo)
  
• Fix displaying marker for new messages (melvo)
  

@prologic@twtxt.net What IRC client is that?

vtnerd completes 2024 Q3 Monero dev work CCS
vtnerd1 has posted a third and final progress report2 for their full-time 2024/Q3 Monero development work CCS proposal3:

The bulk of the time was making LWS HTTP client requests asynchronous4 - the scanner, exchange rates, and /login are no longer blocked by I/O. [..] I’ve probably missed a few things, this was a somewhat busy month of work.

”`

• LWS /get_random_outs is also now asynchronous
  
• … ⌘ Read more”`

**(#dy3n2cq) Also interesting:

edit_hash: When a message is edited, a new message is created– this field holds the hash of the modified messag …**
Also interesting:

edit_hash: When a message is edited, a new message is created– this field holds the hash of the modified message. The client follows the chain of edit hashes to end up at the final, edited message to display. This lets us keep an “undo” history (not yet implemented) and is a marker so the client can display a marker that the message has been edited. ⌘ Read more

**(#ptp2n7a) > Why is my @ mention is all over the place?

Just the way yarnd (my client) behaves, which I’m also refactoring and improving the …**

Why is my @ mention is all over the place?

Just the way yarnd (my client) behaves, which I’m also refactoring and improving the way mentions are expanded and auto-completed. ⌘ Read more

Yes it work: 2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :D

The .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.

Access to those files are closed to the public.

Maybe realize webmention in my feed? (receiving). Sending maybe will be implemened in WIP client…

@movq@www.uninformativ.de Were you going to add Jenny here?
@movq @www.uninformativ.de Were you going to add Jenny here? https://twtxt.dev/clients.html ⌘ Read more

(#ewcgw4a) Not really sure how this is similar at all teally as Yarn like every other twtxt client just fetches feeds you tell it to? 🤔
Not really sure how this is similar at all teally as Yarn like every other twtxt client just fetches feeds you tell it to? 🤔 ⌘ Read more

(#u6ymywa) To @anth’s points, I think this should be written as “Client recommendations” and “Serve recommendations”. Separate from the “Twtxt …
To @anth @a.9srv.net’s points, I think this should be written as “Client recommendations” and “Serve recommendations”. Separate from the “Twtxt format” spec. ⌘ Read more

@sorenpeter@darch.dk on 4 for gemini if your TLS client certificate contains your nick@host could that work for discovery?

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

JMP: Newsletter: JMP at SeaGL, Cheogram now on Amazon
Hi everyone!

Welcome to the latest edition of your pseudo-monthly JMP update!

In case it’s been a while since you checked out JMP, here’s a refresher: JMP lets you send and receive text and picture messages (and calls) through a real phone number right from your computer, tablet, phone, or anything else that has a Jabber client. Among other things, JMP has these features: Your phone number on every device; Multiple phone numbers, one app; Free as … ⌘ Read more

(#gctrz4q) > Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don�� …

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My ¼ -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

Yeah I’ve closed the PR, I just wanted to write it up and see what we all thought. Much easier to talk to a concrete spec proposal sometimes. … ⌘ Read more

(#gctrz4q) > What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think …

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes ¼ on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that sup … ⌘ Read more

@bender@twtxt.net @prologic@twtxt.net I’m not exactly asking yarnd to change. If you are okay with the way it displayed my twts, then by all means, leave it as is. I hope you won’t mind if I continue to write things like 1/4 to mean “first out of four”.

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing 1/4 with ¼, or other similar transformations. It’s not needed, because ¼ is already a unicode character that can simply be directly inserted into the text file.

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic@twtxt.net, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes 1/4 on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that supports displaying unicode characters, including Jenny, would then display ¼ as ¼.

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My 1/4 -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

(#s7t3gya) @bender@bender The only changes I can foresee are really to yarnd. As no other client I’m aware of really cares aall that much. …
@bender The only changes I can foresee are really to yarnd. As no other client I’m aware of really cares aall that much. 🤣 It’s only in an attempt to solve this. No I’m not sure about this 🤣 ⌘ Read more

@sorenpeter@darch.dk I run Weechat headless on a VM and mostly connect via mobile or dwsktop. I use the android client or gliwing bear. Work blocks all comms on their always on MitM VPN so I cant in office anymore. So I just use mobile.

(#rjapt4a) @movq Hmmm now I’m confused 😅 I’ve made no changes anywhere – we still need to all agree, especially client authors and maintaine …
@movq @www.uninformativ.de Hmmm now I’m confused 😅 I’ve made no changes anywhere – we still need to all agree, especially client authors and maintainers 🤣 ⌘ Read more

@Codebuzz@www.codebuzz.nl Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I’m referring to the definition that it’s the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.

Erlang Solutions: Implementing Phoenix LiveView: From Concept to Production
When I began working with Phoenix LiveView, the project evolved from a simple backend service into a powerful, UI-driven customer service tool. A basic Phoenix app for storing user data quickly became a core part of our client’s workflow.

In this post, I’ll take you through a project that grew from its original purpose- from a service fo … ⌘ Read more

Erlang Solutions: Client Case Studies with Erlang Solutions
At Erlang Solutions, we’ve worked with diverse clients, solving business challenges and delivering impactful results. We would like to share just some of our top client case studies in this latest post with you.

Get a glimpse into how our leading technologies—Erlang, Elixir, MongooseIM, and more—combined with our expert team, have transformed the outcomes for major industry players.

Ignite Realtime Blog: Smack 4.5.0-beta5 released
The Ignite Realtime developer community is happy to announce that Smack 4.5 entered its beta phase. Smack is a XMPP client API written in Java that is able to run on Java SE and Android. Smack’s beta phase started already a few weeks ago, but 4.5.0-beta5 is considered to be a good candidate to announce, as many smaller issues have been ironed out.

With Smack 4.5 we bumped the minimum Java version to 11. Furthermore Smack now requires a minimum And … ⌘ Read more

woodser releases Haveno v1.0.12 with various fixes and improvements
woodser1 has released Haveno2 version 1.0.123 with various improvements, updates, and bug fixes.

Update to monero-project v0.18.3.4 and monero-java v0.8.33
Play sounds for notifications (can be disabled in Settings)
Schedule offers using available and pending funds
Support AppImage installer for Linux
Fix exporting and importing payment accounts across clients
Reclassify mainnet nodes as pub ... ⌘ [Read more](https://monero.observer/woodser-releases-haveno-v1.0.12/)

I know no client support it (yet) - but it could be the future 😅

@2024-10-08T19:36:38-07:00@a.9srv.net Thanks for the followup. I agrees with most of it - especially:

Please nobody suggest sticking the content type in more metadata. 🙄

Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.

Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk (wf endpoint). Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (wf lookup) or RANDOMSTRING@garrido.io on https://webfinger.net