🧮 USERS:1 FEEDS:2 TWTS:85 ARCHIVED:17666 CACHE:1009 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:750 ARCHIVED:268461 CACHE:69152 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:84 ARCHIVED:17609 CACHE:1009 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:749 ARCHIVED:264735 CACHE:66938 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:83 ARCHIVED:17510 CACHE:1048 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:746 ARCHIVED:261274 CACHE:66183 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:82 ARCHIVED:17308 CACHE:1052 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:744 ARCHIVED:255786 CACHE:58383 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:81 ARCHIVED:16749 CACHE:1017 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:743 ARCHIVED:253195 CACHE:56116 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:80 ARCHIVED:16669 CACHE:1001 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:742 ARCHIVED:249955 CACHE:44385 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:79 ARCHIVED:16630 CACHE:996 FOLLOWERS:13 FOLLOWING:14
An ageing rose cries. My first graphical media twt!
🧮 USERS:2 FEEDS:6 TWTS:741 ARCHIVED:246331 CACHE:44428 FOLLOWERS:28 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:78 ARCHIVED:16599 CACHE:1008 FOLLOWERS:13 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:739 ARCHIVED:242423 CACHE:42687 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:76 ARCHIVED:16511 CACHE:1031 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:738 ARCHIVED:238940 CACHE:42308 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:75 ARCHIVED:16448 CACHE:1043 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:737 ARCHIVED:235371 CACHE:40109 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:74 ARCHIVED:16356 CACHE:1033 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:730 ARCHIVED:231627 CACHE:42604 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:72 ARCHIVED:14717 CACHE:1037 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:729 ARCHIVED:228952 CACHE:41633 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:71 ARCHIVED:14406 CACHE:960 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:726 ARCHIVED:225454 CACHE:38342 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:70 ARCHIVED:13913 CACHE:780 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:725 ARCHIVED:221878 CACHE:38816 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:69 ARCHIVED:13589 CACHE:790 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:723 ARCHIVED:218043 CACHE:35638 FOLLOWERS:27 FOLLOWING:680
🧮 USERS:1 FEEDS:2 TWTS:68 ARCHIVED:12501 CACHE:814 FOLLOWERS:12 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:721 ARCHIVED:131812 CACHE:17882 FOLLOWERS:27 FOLLOWING:50
🧮 USERS:1 FEEDS:2 TWTS:66 ARCHIVED:12445 CACHE:821 FOLLOWERS:11 FOLLOWING:14
🧮 USERS:2 FEEDS:6 TWTS:720 ARCHIVED:131610 CACHE:17779 FOLLOWERS:27 FOLLOWING:50
🧮 USERS:1 FEEDS:2 TWTS:61 ARCHIVED:12227 CACHE:749 FOLLOWERS:11 FOLLOWING:13
🧮 USERS:2 FEEDS:6 TWTS:719 ARCHIVED:131437 CACHE:17713 FOLLOWERS:27 FOLLOWING:50
🧮 USERS:1 FEEDS:2 TWTS:60 ARCHIVED:12166 CACHE:766 FOLLOWERS:11 FOLLOWING:13
🧮 USERS:2 FEEDS:6 TWTS:718 ARCHIVED:131169 CACHE:17549 FOLLOWERS:27 FOLLOWING:50
🧮 USERS:1 FEEDS:2 TWTS:59 ARCHIVED:12063 CACHE:776 FOLLOWERS:11 FOLLOWING:13
🧮 USERS:1 FEEDS:6 TWTS:714 ARCHIVED:128102 CACHE:14765 FOLLOWERS:26 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:57 ARCHIVED:11979 CACHE:827 FOLLOWERS:11 FOLLOWING:13
🧮 USERS:1 FEEDS:6 TWTS:713 ARCHIVED:127922 CACHE:14685 FOLLOWERS:26 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:56 ARCHIVED:11899 CACHE:832 FOLLOWERS:11 FOLLOWING:13
🧮 USERS:1 FEEDS:6 TWTS:711 ARCHIVED:127716 CACHE:14579 FOLLOWERS:26 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:54 ARCHIVED:11797 CACHE:843 FOLLOWERS:10 FOLLOWING:13
🧮 USERS:1 FEEDS:6 TWTS:708 ARCHIVED:127427 CACHE:14401 FOLLOWERS:26 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:50 ARCHIVED:11564 CACHE:823 FOLLOWERS:10 FOLLOWING:12
@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!
🧮 USERS:1 FEEDS:6 TWTS:706 ARCHIVED:127220 CACHE:14272 FOLLOWERS:25 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:49 ARCHIVED:11465 CACHE:839 FOLLOWERS:10 FOLLOWING:12
🧮 USERS:1 FEEDS:6 TWTS:705 ARCHIVED:126932 CACHE:13951 FOLLOWERS:25 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:48 ARCHIVED:11312 CACHE:838 FOLLOWERS:10 FOLLOWING:12
🧮 USERS:1 FEEDS:6 TWTS:701 ARCHIVED:126616 CACHE:13737 FOLLOWERS:25 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:47 ARCHIVED:11134 CACHE:840 FOLLOWERS:10 FOLLOWING:12
🧮 USERS:1 FEEDS:6 TWTS:698 ARCHIVED:126308 CACHE:13511 FOLLOWERS:25 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:45 ARCHIVED:10941 CACHE:810 FOLLOWERS:9 FOLLOWING:12
🧮 USERS:1 FEEDS:6 TWTS:691 ARCHIVED:126044 CACHE:13187 FOLLOWERS:25 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:44 ARCHIVED:10800 CACHE:778 FOLLOWERS:9 FOLLOWING:12
Howth (2010)
🧮 USERS:1 FEEDS:6 TWTS:688 ARCHIVED:125695 CACHE:12698 FOLLOWERS:25 FOLLOWING:49
🧮 USERS:1 FEEDS:2 TWTS:41 ARCHIVED:10607 CACHE:768 FOLLOWERS:9 FOLLOWING:12
🧮 USERS:1 FEEDS:6 TWTS:676 ARCHIVED:125180 CACHE:10027 FOLLOWERS:25 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:40 ARCHIVED:10383 CACHE:700 FOLLOWERS:9 FOLLOWING:12
Hmmm so… We seem to have a few pods offline in the network 😂 Also 😢
- @jlj@twt.nfld.uk’s twt.nfld.uk => 504 Gateway Time-out
- @adi@f.adi.onl’s f.adi.onl => 200 OK but doens’t appear to be a pod anymore?! 🤔
- @eldersnake@yarn.andrewjvpowell.com’s personal pod => offline due to lack of Solar/Battery power? 😅
- @lohn@tw.lohn.in’s personal pod => 503 Service Unavailable
It’s a bad day for Yarn.social 🤣
Good thing it’s all decentralised 😉
🧮 USERS:1 FEEDS:6 TWTS:668 ARCHIVED:124723 CACHE:13955 FOLLOWERS:25 FOLLOWING:46
🧮 USERS:1 FEEDS:2 TWTS:35 ARCHIVED:10220 CACHE:650 FOLLOWERS:8 FOLLOWING:12
🧮 USERS:1 FEEDS:6 TWTS:662 ARCHIVED:124594 CACHE:13671 FOLLOWERS:24 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:31 ARCHIVED:8745 CACHE:747 FOLLOWERS:8 FOLLOWING:10
@jlj@twt.nfld.uk Lol! Fantastic that your grandma has been able to live to that age! My grandfather made it to 96, quite healthy and happy, and actually walking around by himself until the end. Best wishes of health!
🧮 USERS:1 FEEDS:6 TWTS:661 ARCHIVED:124463 CACHE:12661 FOLLOWERS:24 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:27 ARCHIVED:8654 CACHE:720 FOLLOWERS:8 FOLLOWING:10
🧮 USERS:1 FEEDS:6 TWTS:660 ARCHIVED:124286 CACHE:10259 FOLLOWERS:24 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:25 ARCHIVED:8268 CACHE:685 FOLLOWERS:8 FOLLOWING:9
🧮 USERS:1 FEEDS:6 TWTS:657 ARCHIVED:124059 CACHE:8773 FOLLOWERS:23 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:24 ARCHIVED:8158 CACHE:641 FOLLOWERS:8 FOLLOWING:9
yarnd, the mobile app nor API support this anyway...
@movq@www.uninformativ.de i believe the delete of any twt was a tech limitation with retwt parser not knowing where in the file a twt came from. lextwt tracks the bytes in file where a twt was read from. which could be used to delete a twt from file.. in theory.
yarnd, the mobile app nor API support this anyway...
@movq@www.uninformativ.de i believe the delete of any twt was a tech limitation with retwt parser not knowing where in the file a twt came from. lextwt tracks the bytes in file where a twt was read from. which could be used to delete a twt from file.. in theory.
yarnd, the mobile app nor API support this anyway...
I am in the camp of wishing i could delete arbitrary twts.
yarnd, the mobile app nor API support this anyway...
I am in the camp of wishing i could delete arbitrary twts.
👋 Q&A: Let’s discuss the removal of Editing and Deleting your last Twt. This is something @fastidious@twtxt.net has raised to me on IRC and something I find quite a valid approach to this. Over time I believe the utility and value of “Editing” and “Deleting” one’s last Twt isn’t as valuable as we’d like and increased complexity and introduces all kinds of side-effects that are hard to manage correctly. I vote for the removal of this feature from yarnd, the mobile app nor API support this anyway…
🧮 USERS:1 FEEDS:6 TWTS:651 ARCHIVED:123454 CACHE:6499 FOLLOWERS:23 FOLLOWING:45
🧮 USERS:1 FEEDS:2 TWTS:16 ARCHIVED:6605 CACHE:541 FOLLOWERS:5 FOLLOWING:8
🧮 USERS:1 FEEDS:6 TWTS:44582 ARCHIVED:122836 CACHE:10043 FOLLOWERS:23 FOLLOWING:45
@darch@twtxt.net
Getting this when trying to use it:
error executing template timeline: template: timeline:131:43: executing "twt" at <formatForDateTime>: wrong number of args for formatForDateTime: want 2 got 1
🧮 USERS:1 FEEDS:6 TWTS:44581 ARCHIVED:122474 CACHE:9991 FOLLOWERS:23 FOLLOWING:45
🧮 USERS:1 FEEDS:6 TWTS:44580 ARCHIVED:122069 CACHE:11727 FOLLOWERS:23 FOLLOWING:45
I think something has caused my feed to be in a bad state and is now unpardable😥
I can read this on jenny, but the twt isn’t making it to my own pod. Something has gone really wrong, me thinks.
🧮 USERS:1 FEEDS:6 TWTS:44578 ARCHIVED:120748 CACHE:10544 FOLLOWERS:23 FOLLOWING:45
@prologic@twtxt.net Its not FormatText stripping out the lines. That formats with \n newlines so when unmarshalling it tries to parse the text and sees that as the end of twt. LiteralText keeps the newlines as \u2028
@prologic@twtxt.net Its not FormatText stripping out the lines. That formats with \n newlines so when unmarshalling it tries to parse the text and sees that as the end of twt. LiteralText keeps the newlines as \u2028
@prologic@twtxt.net make the text field twt.LiteralText() instead of twt.FormatText() and you should be good. https://i.imgur.com/FIpSnkj.png
@prologic@twtxt.net make the text field twt.LiteralText() instead of twt.FormatText() and you should be good. https://i.imgur.com/FIpSnkj.png
🧮 USERS:1 FEEDS:6 TWTS:44574 ARCHIVED:120245 CACHE:6137 FOLLOWERS:23 FOLLOWING:45
multi.
line.
twt..
multi.
line.
twt..
multi
line
twt
multi
line
twt
🧮 USERS:1 FEEDS:6 TWTS:44571 ARCHIVED:117826 CACHE:19109 FOLLOWERS:23 FOLLOWING:45