FOLLOW: @xuu@txt.sour.is from @ullarah@txt.quisquiliae.com using yarnd/0.8.0@80999ab
**
🧮 USERS:3 FEEDS:6 TWTS:244 BLOGS:0 ARCHIVED:59505 CACHE:2209 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:244 BLOGS:0 ARCHIVED:59505 CACHE:2209 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:243 BLOGS:0 ARCHIVED:59317 CACHE:2248 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:243 BLOGS:0 ARCHIVED:59317 CACHE:2248 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:242 BLOGS:0 ARCHIVED:59044 CACHE:2254 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:242 BLOGS:0 ARCHIVED:59044 CACHE:2254 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:241 BLOGS:0 ARCHIVED:58799 CACHE:2235 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:241 BLOGS:0 ARCHIVED:58799 CACHE:2235 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:240 BLOGS:0 ARCHIVED:58477 CACHE:2205 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:240 BLOGS:0 ARCHIVED:58477 CACHE:2205 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
@fastidious@arrakis.netbros.com (#twksmyq) IPv6 because localhost -> ::1 is preferred on linux over ol’ 127.0.0.1
Now this is very useful.. it means when yarn is doing an HTTP request to itself its not closing the connection. that could mean a http.Response Body is not getting closed.
**
🧮 USERS:3 FEEDS:6 TWTS:239 BLOGS:0 ARCHIVED:58235 CACHE:2177 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:239 BLOGS:0 ARCHIVED:58235 CACHE:2177 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:238 BLOGS:0 ARCHIVED:57986 CACHE:2166 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:238 BLOGS:0 ARCHIVED:57986 CACHE:2166 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
FOLLOW: @xuu@txt.sour.is from @meff@yarn.meff.me using yarnd/0.7.2@a4ee171
**
🧮 USERS:3 FEEDS:6 TWTS:237 BLOGS:0 ARCHIVED:57505 CACHE:2082 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:237 BLOGS:0 ARCHIVED:57505 CACHE:2082 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:236 BLOGS:0 ARCHIVED:57311 CACHE:2109 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:236 BLOGS:0 ARCHIVED:57311 CACHE:2109 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:235 BLOGS:0 ARCHIVED:57056 CACHE:2114 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:235 BLOGS:0 ARCHIVED:57056 CACHE:2114 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
FOLLOW: @xuu@txt.sour.is from @darch2@yarn.algorave.dk using yarnd/0.6.2@86938ca
**
🧮 USERS:3 FEEDS:6 TWTS:234 BLOGS:0 ARCHIVED:56804 CACHE:2094 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:234 BLOGS:0 ARCHIVED:56804 CACHE:2094 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:233 BLOGS:0 ARCHIVED:56550 CACHE:2066 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:233 BLOGS:0 ARCHIVED:56550 CACHE:2066 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:232 BLOGS:0 ARCHIVED:56318 CACHE:2033 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:232 BLOGS:0 ARCHIVED:56318 CACHE:2033 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:231 BLOGS:0 ARCHIVED:56056 CACHE:2038 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:231 BLOGS:0 ARCHIVED:56056 CACHE:2038 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:230 BLOGS:0 ARCHIVED:55821 CACHE:2086 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:230 BLOGS:0 ARCHIVED:55821 CACHE:2086 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:229 BLOGS:0 ARCHIVED:55620 CACHE:2133 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:229 BLOGS:0 ARCHIVED:55620 CACHE:2133 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:228 BLOGS:0 ARCHIVED:55428 CACHE:2134 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:228 BLOGS:0 ARCHIVED:55428 CACHE:2134 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
“Browservice” brings modern web browsing to 1990s computers
Take a look at this: “What am I looking at?” That, right there, is Windows 3.11 (Windows for Workgroups)… loading up the Google Cloud VM manager. A website that requires a modern web browser. But, that isn’t a modern web browser. That is Internet Explorer 4.0. On Windows 3.11. Seriously. ⌘ Read more
jenny -f. Have now jennys cache under revision control, automatically commiting changes after each fetch. Let's see if this helps finding a (possible) bug.
@movq@www.uninformativ.de Your scenario would produce observed behaviour, agreed. On the other side I’m sure I’ve set very URL in lasttwt > 1630000000.0 (manually, in my editor).
But I can’t reproduce any weird behaviour right now. I’ve tried to “blackhole” twt.nfld.uk temporarily. That does not have any effect.
I’ve also tried to force twt.nfld.uk to deliver an empty twtxt. That does not have any effect either.
So I guess everything is fine with jenny.
I have wrapped jenny into some shell script to versionize ~/.cache/jenney. This way I have better data if anything unexprected is showing again.
**
🧮 USERS:3 FEEDS:6 TWTS:227 BLOGS:0 ARCHIVED:55228 CACHE:2173 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:227 BLOGS:0 ARCHIVED:55228 CACHE:2173 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:226 BLOGS:0 ARCHIVED:54944 CACHE:2124 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:226 BLOGS:0 ARCHIVED:54944 CACHE:2124 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:225 BLOGS:0 ARCHIVED:54681 CACHE:2086 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:225 BLOGS:0 ARCHIVED:54681 CACHE:2086 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
@movq@www.uninformativ.de I just observed unexpected old twts coming back.
It looks like lasttwts is reset to -5364619200.0 every time no new content wasfetched for example if if-modified-since did not produce new twts?
@movq@www.uninformativ.de Not that easy to test when pods honor if-modified-since ;-)
I’ve almost only timestamps -5364619200.0…
Diff looks good to me!
**
🧮 USERS:3 FEEDS:6 TWTS:224 BLOGS:0 ARCHIVED:54447 CACHE:2059 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:224 BLOGS:0 ARCHIVED:54447 CACHE:2059 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:223 BLOGS:0 ARCHIVED:54236 CACHE:2108 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:223 BLOGS:0 ARCHIVED:54236 CACHE:2108 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
Don’t miss step 0 (I should have made this a separate point): having a meta header promising appending twts with strictly monotonically increasing timestamps.
(Also, I’d first like to see the pagination thingy implemented.)
In jenny I would like to see “don’t process previously fetched twts” AKA “Allow the user to archive/delete old twts” feature implemented ;-)
**
🧮 USERS:3 FEEDS:6 TWTS:222 BLOGS:0 ARCHIVED:54048 CACHE:2122 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:222 BLOGS:0 ARCHIVED:54048 CACHE:2122 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:221 BLOGS:0 ARCHIVED:53815 CACHE:2111 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:221 BLOGS:0 ARCHIVED:53815 CACHE:2111 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:220 BLOGS:0 ARCHIVED:53495 CACHE:2116 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:220 BLOGS:0 ARCHIVED:53495 CACHE:2116 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
Ignite Realtime Blog: Push Notification Openfire plugin 0.9.0 released
I’m happy to be able to announce that we’ve released version 0.9.0 of the Push Notifications plugin for Openfire!
This version does not bring new functionality. It does fix a bug that older versions of this plugin had, when running on Openfire 4.6.4 or later.
For other release announcements and news follow us on Twitter
1 post - 1 participant
�� … ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:219 BLOGS:0 ARCHIVED:53234 CACHE:2064 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:219 BLOGS:0 ARCHIVED:53234 CACHE:2064 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:218 BLOGS:0 ARCHIVED:52943 CACHE:2028 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:218 BLOGS:0 ARCHIVED:52943 CACHE:2028 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:217 BLOGS:0 ARCHIVED:52648 CACHE:2015 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:217 BLOGS:0 ARCHIVED:52648 CACHE:2015 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:216 BLOGS:0 ARCHIVED:52412 CACHE:2110 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:216 BLOGS:0 ARCHIVED:52412 CACHE:2110 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:215 BLOGS:0 ARCHIVED:52195 CACHE:2122 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:215 BLOGS:0 ARCHIVED:52195 CACHE:2122 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
@prologic@twtxt.net
Thank you, that’s the correct one.
Still I have this in my logs (first access of “eleven” by yarnd):
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “GET /eleven.txt HTTP/2.0” 200 344 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “HEAD /avatar.png HTTP/2.0” 200 0 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
And I guess without avatar.png sitting there I would have seen even more requests like /eleven.txt/avatar.png.
I’ve copied stackeffect.png to avatar.png to make yarnd happy when accessing stackeffect.txt.
So in this setup yarnd fetched eleven.txt along with avatar.png which belongs to another twtxt. This feels buggy.
**
🧮 USERS:3 FEEDS:6 TWTS:214 BLOGS:0 ARCHIVED:51989 CACHE:2112 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:214 BLOGS:0 ARCHIVED:51989 CACHE:2112 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:213 BLOGS:0 ARCHIVED:51744 CACHE:2131 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:213 BLOGS:0 ARCHIVED:51744 CACHE:2131 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:212 BLOGS:0 ARCHIVED:51483 CACHE:2109 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:212 BLOGS:0 ARCHIVED:51483 CACHE:2109 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:211 BLOGS:0 ARCHIVED:51248 CACHE:2099 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:211 BLOGS:0 ARCHIVED:51248 CACHE:2099 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
**
🧮 USERS:3 FEEDS:6 TWTS:210 BLOGS:0 ARCHIVED:51012 CACHE:2089 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:210 BLOGS:0 ARCHIVED:51012 CACHE:2089 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
OpenBSD 7.0 \o/
OpenBSD 7.0, get it while is hot, folks! 🐡
@quark@ferengi.one If so, @movq@www.uninformativ.de, not quite https://www.uninformativ.de/git/jenny/commit/4a02eeec58317107c07e759733312d168e319f17.html#h0-0-5... Markdown needs single new lines for many things. Bulleted, numbered, code, etc. need them.
@movq@www.uninformativ.de I am getting this when I run it on cron (extra lines in between becuase otherwise jenny will make them a mash):
Traceback (most recent call last):
File “/home/quark/jenny/jenny”, line 565, in
if not retrieve_all(config):
File “/home/quark/jenny/jenny”, line 373, in retrieve_all
refresh_self(config)
File “/home/quark/jenny/jenny”, line 294, in refresh_self
process_feed(config, config[‘self_nick’], config[‘self_url’], content)
File “/home/quark/jenny/jenny”, line 280, in process_feed
fp.write(mail_body)
File “/usr/lib/python3.8/encodings/iso8859_15.py”, line 19, in encode
return codecs.charmap_encode(input,self.errors,encoding_table)[0]
UnicodeEncodeError: ‘charmap’ codec can’t encode character ‘\U0001f4e3’ in position 31: character maps to