[Matrix] works and I have to say, I'm not really liking it all that much π
[Matrix] works and I have to say, I'm not really liking it all that much π
The thing is the experience is as @david rightly said, extremely slow. I'm seeing huge amounts of Disk and Network traffic joining any room. And I"m seeing Join times of 2-person rooms (Private Chats) of up to 30s.
The thing is the experience is as @david rightly said, extremely slow. I'm seeing huge amounts of Disk and Network traffic joining any room. And I"m seeing Join times of 2-person rooms (Private Chats) of up to 30s.
[Matrix] homeserver is now working (no changes, just some issue with key validation and caching) π₯³ I can be reached at @james:mills.io π -- Still unsure of [Matrix] in the first place, but I will give credit where credit is due. At least it was orders of magnitude simpler to stand up than any XMPP/Jabber "thingy", clients "just worked"β’ for it and (after some mishaps) Federation works too. I also have to recognize that it also doesn't require my to poke dozens of random ports and holes through my firewall for it to work. π #Matrix
[Matrix] homeserver is now working (no changes, just some issue with key validation and caching) π₯³ I can be reached at @james:mills.io π -- Still unsure of [Matrix] in the first place, but I will give credit where credit is due. At least it was orders of magnitude simpler to stand up than any XMPP/Jabber "thingy", clients "just worked"β’ for it and (after some mishaps) Federation works too. I also have to recognize that it also doesn't require my to poke dozens of random ports and holes through my firewall for it to work. π #Matrix
Perhaps it's time to get serious about encrypted feeds? π€
Perhaps it's time to get serious about encrypted feeds? π€
yarnd Pod yourself locally if you'd like to do testing outside of the "production network" π
-- I honestly don't mind myself, but of course others _might_ -- So that's something to consider...
yarnd Pod yourself locally if you'd like to do testing outside of the "production network" π
-- I honestly don't mind myself, but of course others _might_ -- So that's something to consider...
yarnd's Web Interface -- in the Cache. You can see this by any "Yarn" view (/conv/<hash> routes). But we choose to remain with a Timeline view which you can either choose to have as a "List" or "Flat" in your Settings
yarnd's Web Interface -- in the Cache. You can see this by any "Yarn" view (/conv/<hash> routes). But we choose to remain with a Timeline view which you can either choose to have as a "List" or "Flat" in your Settings
You can see this here which will explain why you saw what you did.
You can see this here which will explain why you saw what you did.
yarnc log sub-command that reads your local twtxt.txt file and display each Twt along with it's Date/Time and Hash?That would need to go hang-in-hand with fleshing out "local feed" support with "sync to Pod" at the same time for that to make sense, but if this is what you mean, yes I approve π
yarnc log sub-command that reads your local twtxt.txt file and display each Twt along with it's Date/Time and Hash?That would need to go hang-in-hand with fleshing out "local feed" support with "sync to Pod" at the same time for that to make sense, but if this is what you mean, yes I approve π
=> https://git.mills.io/yarnsocial/yarn/issues/861=
=> https://git.mills.io/yarnsocial/yarn/issues/861=
Problem is, by the time you do that, it's too late. A client (whether it be twtr, tt, jenny or yarnd) would have seen it already, hashed it, cached it and archived it.
Problem is, by the time you do that, it's too late. A client (whether it be twtr, tt, jenny or yarnd) would have seen it already, hashed it, cached it and archived it.
> Should i ask the obvious question ?
What's the question?
twtr is an independent implementation of Twtxt + Yarn.social extensions created by and maintained by @<~duriny https://envs.net/~duriny/twtxt.txt> πyarnc is a command-line client for the Yarn.social yarnd API of what we call "Pods". I have a strong desire however for it to also be somewhat closer to twtr in the sense that you can use it for managing a local twtxt.txt file with "sync" to your Yarn.social account on whatever Pod you choose.Does this help clear things up? π€
> Should i ask the obvious question ?
What's the question?
twtr is an independent implementation of Twtxt + Yarn.social extensions created by and maintained by @<~duriny https://envs.net/~duriny/twtxt.txt> πyarnc is a command-line client for the Yarn.social yarnd API of what we call "Pods". I have a strong desire however for it to also be somewhat closer to twtr in the sense that you can use it for managing a local twtxt.txt file with "sync" to your Yarn.social account on whatever Pod you choose.Does this help clear things up? π€
yarnd API via curl? Would that help here with complete examples? π€
yarnd API via curl? Would that help here with complete examples? π€
Content-Type of application/json to the /api/v1/<rpc> endpoint of any pod.
Content-Type of application/json to the /api/v1/<rpc> endpoint of any pod.
=> https://git.mills.io/yarnsocial/yarn/issues/808=
=> https://git.mills.io/yarnsocial/yarn/issues/808=
I've think we've gone down too many wrong paths in the last couple of decades especially π’
PS: Just reply to your feed and preserve the Twt Subject Hash with
(#rlwgvtq) at the start π
I've think we've gone down too many wrong paths in the last couple of decades especially π’
PS: Just reply to your feed and preserve the Twt Subject Hash with
(#rlwgvtq) at the start π
> Twtxt is dead, long live Yarn.social!
π€ π
> Twtxt is dead, long live Yarn.social!
π€ π
yarnc is lacking and in need of some additional features π> very funny project you have here
When you say "funny", what do you mean? π
yarnc is lacking and in need of some additional features π> very funny project you have here
When you say "funny", what do you mean? π
tt needs to grow similar support? π€
tt needs to grow similar support? π€
jq for all your JSON needs? π€
jq for all your JSON needs? π€
yarnd some week or so ago as well -- But I don't use this very much, because the "Flat view" collapses long threads so it's not a problem.
yarnd some week or so ago as well -- But I don't use this very much, because the "Flat view" collapses long threads so it's not a problem.
> either need to follow fewer people or I need to somehow rework my clientβs UX.
I _think_ you should focus on the later π That particular Yarn you're tlaking about with over ~50 Twts I didn't even notice until last night sometime before bed π
The UX(s) of
tt and jenny (correct me if I'm wrong) don't collapse threads by default right? π€~
> either need to follow fewer people or I need to somehow rework my clientβs UX.
I _think_ you should focus on the later π That particular Yarn you're tlaking about with over ~50 Twts I didn't even notice until last night sometime before bed π
The UX(s) of
tt and jenny (correct me if I'm wrong) don't collapse threads by default right? π€~
If there's a way to abuse a system, someone will find a way to do so.
Sad but true, assholes are everywhere π’
If there's a way to abuse a system, someone will find a way to do so.
Sad but true, assholes are everywhere π’
> Maybe NASA would have listened.
> Maybe NASA would have listened.
I have some catching up to do, I want to read every Twt in this Yarn π€£
I have some catching up to do, I want to read every Twt in this Yarn π€£
\i2028 characters in them and replace with \n π