@Felix (re Social Media Subscriptions) Yeah I agree! I was mostly commenting on the astonishment of advertising models ๐ I plan to do something similar to Micro.blog with twtxt.net like paid hosted instances. ๐
matched #akdkyuq score:10.98
Search by:
Search by 1 mentions:
@Felix (re UA strings) Hah! Yeah I built a feature into twtxt such that the backend automatically picks these up and posts to a special feed @twtxt and updates your account's "Followers". Its quite neat :) Also hi @kas ๐
matched #rzpaz5q score:7.76
Search by:
Search by 3 mentions:
@Felix (re polling interval) Yeah you're probably right. I developed this thing quickly (_as you know_) and am iterating quickly. What I'd like to do is have a sort-of back-off internal algorithm where feeds are only polled based on the frequency of their updates. Make sense?
matched #hoh2bra score:10.98
Search by:
Search by 1 mentions:
@Felix (re polling) The problem is I borrowed a fair bit of the "feed cache and fetching" code from @quite 's twet (_which I also spent a bit helping improve_). I _think_ the feed cache would have to be refactored somewhat for this (_plus other benefits_)
matched #tutwhaa score:8.96
Search by:
Search by 2 mentions:
@kas @Felix (re permalinks) I must have missed this. I am _thinking_ about this for twtxt.net but I was thinking of a different solution. The instance's global feed cache hashing each entry and referencing this. If subsequent fetches we still preserve the old ones...
matched #gmprgpq score:8.96
Search by:
Search by 2 mentions:
@kas @Felix (re permalinks) If a feed entry changes it gets a new hash of course, but we still preserve the hash and content of the older one. This way on twtxt.net we can _link_ to and ref individual Twt(s) (_ofc only works here_).
matched #o4jnb4a score:8.96
Search by:
Search by 2 mentions: