prologic @twtxt.net

Follow

"Problems are Solved by Method" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@prologic does not follow you (they may not see your replies!)

Recent Twts

Recent twts from prologic

prologic @twtxt.net
 (1d ago)

(#cs6lodq) @andros@twtxt.andros.dev That’s a shame. But here’s the thing about piracy. If I could download a PDF or MP3/OGG of a Book I’d happily pay for this. If I could download an MP3/OGG of some Music I would pay for this. If I could download an MP4 of a Movie I would pay for this.

The reason piracy exists at all is economics and greed. If you make something affordable and convenient, there’s no need to steal.

#qqhnmpq
prologic @twtxt.net
 (2d ago)

👋 Folks that use this pod, I’ll be rolling out an experimental new caching backend to this pod shortly. Stay tuned. Please provide feedback either here via Twtxt or on IRC. Thanks! 🙏

#j6ofzfq
prologic @twtxt.net
 (2d ago)

(#hv7xxjq) There are however a few implications to note:

  • It will be possibly to page through much larger quantities of twts per feed, this is potentially unlimited (depends on disk space)
  • Automated Feeds (bots) like @tiktok@feeds.twtxt.net will now behave/display very differently. You will see all it’s historical Twts, whereas before you’d only see the one because the MemoryCache’s behavior was to “replace” Twts.

I’m hoping everything else remains the same and true to what we’ve collectively built and to spec. Replies work, Forks work, various views, filters and so on still work. I’m developing this new cache in a way that uses a “delegate” pattern and a double read / double write with metrics so I can over time see that none of the “old cache” is used anymore.

#hr7w2nq
prologic @twtxt.net
 (4d ago)

(#lnrgahq) @eapl.me@eapl.me@eapl.me@eapl.me What’s with your client not using the proper syntax for mentions?

$ bat 'https://twtxt.net/twt/lnrgahq' | jq '.text'
"(#4xaabhq) thanks @prologic! 
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of \"is this a problem worth to be fixed?, are we committed to implement a change in our clients?\" 

But that's a fair point. What do the community expect? What do y'all expect?"

🤔

#zmhpw7q
prologic @twtxt.net
 (4d ago)

I wonder if I can do away with the followers follows mutes tables and expect the client to actually filter Twts appropriately before Display? This would simplify the SqliteCache considerably and also mean it would be agnostic of single-user or multi-user as that’s delegated to another layer. Hmmm 🧐

#tk53fqa
prologic @twtxt.net
 (5d ago)

(#zrsxk3a) @bender@twtxt.net I never implemented it actually. That’s why we have the # refresh = metadata field for those that yell loudly enough can add to their feeds. Otherwise yarnd uses WebSub between pods and is fairly dumb. I could never find an “intelligent” way to back-off without hurting freshness.

#7uiit5q