**
🧮 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
🧮 USERS:1 FEEDS:6 TWTS:44560 BLOGS:3 ARCHIVED:107759 CACHE:15365 FOLLOWERS:23 FOLLOWING:44
@prologic@twtxt.net @movq@www.uninformativ.de
Exactly, you see correct UTF-8 encoded version (even with content-type: text/plain leaving out charset declaration).
After following utf8test twtxt myself I now see that jenny does not handle it as UTF-8 when charset is missing from HTTP header, just like @quark@ferengi.one has observed.
So should jenny treat twtxt files always as UTF-8 encoded? I’m not sure about this.
**
🧮 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:1 FEEDS:6 TWTS:44559 BLOGS:3 ARCHIVED:107383 CACHE:15350 FOLLOWERS:23 FOLLOWING:44
My thoughts about pagination (paging)
Following the discussion about pagination (paging) I think that’s the right thing to do.
Fetching the same content again and again with only a marginal portion of actually new twts is unbearable and does not scale in any way. It’s not only a waste of bandwidth but with increasing number of fetchers it will also become a problem for pods to serve all requests.
Because it’s so easy to implement and simple to understand, splitting twtxt file in parts with next and prev pointers seems a really amazing solution.
As in RFC5005 there should also be a meta header pointing to the main URL, e.g. current or baseurl or something like that. This way hashes can calculated correctly even for archived twts.
**
🧮 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:1 FEEDS:6 TWTS:44558 BLOGS:3 ARCHIVED:106992 CACHE:15325 FOLLOWERS:23 FOLLOWING:44
**
🧮 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
🧮 USERS:1 FEEDS:6 TWTS:44557 BLOGS:3 ARCHIVED:106371 CACHE:15079 FOLLOWERS:23 FOLLOWING:44
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:1 FEEDS:6 TWTS:44555 BLOGS:3 ARCHIVED:106018 CACHE:14922 FOLLOWERS:23 FOLLOWING:44
**
🧮 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:1 FEEDS:6 TWTS:44554 BLOGS:3 ARCHIVED:105912 CACHE:14907 FOLLOWERS:23 FOLLOWING:44
D~d>1m and then fetched by !jenny -f. This brings back all deleted twts. Isn't lastmods used to skip older twts?
I’m curious, what is your use case for deleting twts?
Not just deleting, also sorting into other folders is impossible.
It also doesn’t scale in the long term. When I cannot delete twts then I have a full copy of every twtxt I follow - forever. That’s a waste of bandwidth and disk space.
**
🧮 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:1 FEEDS:6 TWTS:44553 BLOGS:3 ARCHIVED:105763 CACHE:14865 FOLLOWERS:23 FOLLOWING:44
**
🧮 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:1 FEEDS:6 TWTS:44552 BLOGS:3 ARCHIVED:105647 CACHE:14845 FOLLOWERS:23 FOLLOWING:44
**
🧮 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
🧮 USERS:1 FEEDS:6 TWTS:44551 BLOGS:3 ARCHIVED:105499 CACHE:14827 FOLLOWERS:23 FOLLOWING:44
**
🧮 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:1 FEEDS:6 TWTS:44550 BLOGS:3 ARCHIVED:105434 CACHE:14813 FOLLOWERS:23 FOLLOWING:44
@prologic@twtxt.net
Kind of a pickle. I would say, if the user isn’t following the feed, then @something and @something@example.com doesn’t get linked.
FOLLOW: @xuu@txt.sour.is from @quark@ferengi.one using jenny/latest
**
🧮 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:1 FEEDS:6 TWTS:44548 BLOGS:3 ARCHIVED:105327 CACHE:14831 FOLLOWERS:22 FOLLOWING:44
**
🧮 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:1 FEEDS:6 TWTS:44547 BLOGS:3 ARCHIVED:105017 CACHE:14595 FOLLOWERS:22 FOLLOWING:44
@adi@f.adi.onl
Just like your highschool girlfriend in Afghanistan “doesn’t need saving”, right? I think it is a language issue you are having, as English isn’t your mother tongue.
QAnon followers are cultist nuts. Some of them wanting out are finding that it is a hard thing to do (did you read the article?). Saying that “they don’t need to escape” is a silly thing to say, at the very least. To me, it just doesn’t make sense.
**
🧮 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:1 FEEDS:6 TWTS:44546 BLOGS:3 ARCHIVED:104831 CACHE:14471 FOLLOWERS:22 FOLLOWING:44
**
🧮 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
🧮 USERS:1 FEEDS:6 TWTS:44545 BLOGS:3 ARCHIVED:104759 CACHE:14454 FOLLOWERS:22 FOLLOWING:44
FOLLOW: @xuu@txt.sour.is from @stackeffect@twtxt.stackeffect.de using jenny/latest
I spent a couple of hours today looking for interesting people to follow, and subsequently engage with, on twtxt without much luck. Finding twtxt.txt files is easy. Finding them active, or talking about interesting things is the challenge.
🧮 USERS:1 FEEDS:6 TWTS:44543 BLOGS:3 ARCHIVED:104685 CACHE:14430 FOLLOWERS:21 FOLLOWING:44
🧮 USERS:1 FEEDS:6 TWTS:44542 BLOGS:3 ARCHIVED:104584 CACHE:14407 FOLLOWERS:21 FOLLOWING:44
🧮 USERS:1 FEEDS:6 TWTS:44541 BLOGS:3 ARCHIVED:104519 CACHE:14401 FOLLOWERS:21 FOLLOWING:44
🧮 USERS:1 FEEDS:6 TWTS:44540 BLOGS:3 ARCHIVED:102630 CACHE:13418 FOLLOWERS:21 FOLLOWING:44
@movq@www.uninformativ.de I hear you. I am very selective of who to follow. I mean, I would drop @prologic@twtxt.net, which is the noisiest one, but he is the boss, and if I want to interact–even once or twice a week–I must follow him. 🤣
🧮 USERS:1 FEEDS:6 TWTS:44539 BLOGS:3 ARCHIVED:102490 CACHE:13353 FOLLOWERS:21 FOLLOWING:44
FOLLOW: @xuu@txt.sour.is from @vain-test@www.uninformativ.de using jenny/latest
@laz@tt.vltra.plus You can delete quark, and rename/refollow quark2 as quark. The other isn’t coming back. I am the only Ferengi around here… for now. We are always expanding, following our very wise “Rules of Acquisition”. 😂
It’s Tuesday, but somehow I have a Thursday kind of feeling… Whatever. I’m following an online auction for a couple of PDAs. The starting price is more than I’d be willing to pay, but there isn’t a single bidder yet. I hope that last, because the seller will put the ad out for a lower price if it does!
🧮 USERS:1 FEEDS:6 TWTS:44537 BLOGS:3 ARCHIVED:102406 CACHE:13349 FOLLOWERS:20 FOLLOWING:44
@prologic@twtxt.net I changed base URL (like, completely), but I am still honouring the old one, pointing it to the new one with 301. Maybe that’s what’s happening with the older posts. I could drop out the 301 completely, but that will break following, right?
Well, I have changed URLs, so this post might not get through, or break follows, or break everything. So, yeah.
🧮 USERS:1 FEEDS:6 TWTS:44536 BLOGS:3 ARCHIVED:102325 CACHE:13334 FOLLOWERS:20 FOLLOWING:44