prologic

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 (twtxt.net) 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
 (11 minutes ago)

(#5hkhcda) @thecanine In color? Yes 🤔 Did you update it from the Web or Mobile app? 🤔 If the later I may have forgotten to add some code on the backend 😂


#yyvxmeq
prologic
 (1 hour ago)

(#turq4ga) Unfortunarely it didn’t come with the C19-C20 cable I needed to go from the UPS to my Tripp Lite PDU 🤦‍♂️ 😥


#5hssf3a
prologic
 (4 hours ago)

(#5hkhcda) … To support feed authors that don’t bother with cache busting their advertised avatar. Which (btw @lyse) can be done as simply as:

# avatar = https://url/to/my/avatar#yyyymmdd

I’ve made sure it’s as simple as possible 🤣


#dpadw5q
prologic
 (4 hours ago)

(#5hkhcda) Hmmm 🤔 His feed metadata shows:

# avatar      = https://twtxt.net/user/thecanine/avatar

Which suggests to me he in fact has not changed it yet…

My own shows:

# avatar      = https://twtxt.net/user/prologic/avatar#2dlw72pr7zocas7hdm6bpucrojeuucstut6455rlw56jjoxkiuxa

And yours:

# avatar      = https://arrakis.netbros.com/user/fastidious/avatar#ts5f7glaewmsy2hpuduhqjenqxnavwpaahbozngbghf6m5ya2v5a

So I don’t think there’s a bug at all. What is missing however is occasionally re-fetching advertised avatars once per day anyway…


#vdly5gq
prologic
 (5 hours ago)

(#jfzqbma) Yeah 🤣

Intel’s 12th-generation Alder Lake mobile processors.

But I’m willing to bet Apple’s is somehow better and this has to be a marketing piece 😂


#e4ef3qa
prologic
 (6 hours ago)

(#3ezvila) In addition, supporting “Range” requests should be possible from a client’s perspective with fallback options to do a full request. I don’t think this needs to be part of the spec at all. The way I would implement this is to keep track of the last position, and re-fetch from that position minus a few hundred bytes just to be sure, throw away any initial garbage. I’d probably also try to detect if the feed is append-only or prepend and track this too (somewhere). If the Metadata preamble changes, seeking back a bit should in theory work or fallback.


#22aayga
prologic
 (6 hours ago)

@lyse@lyse.isobeef.org @movq@www.uninformativ.de I propose that we extend the Metadata spec once more and borrow from JSON API cursor pagination and for feed author’s that wish to rotate or truncate their feed (feeds.twtxt.net already does at ~1MB, and soon yarnd will also at some point); Then one can optionally provide # next = <link> and # prev = <link> Metdata in their feed to link to previous/older versions of their feed. I think this is the easier way to implement this that works no matter how you host or the client used.


#3ezvila
prologic
 (7 hours ago)

(#3dstcya) Let’s talk about this on IRC or here some time. I want to implement Range requests too but we’re probably going to have to build a Twtxt v2 spec that insists Twts are appended to start with.


#nk3dwva
prologic
 (19 hours ago)

(#fvdkerq) Sorry this was wrong:

This then gets used to form the “Base URL” of all media as well as the /support and /abuse page links in the app

I meant to say:

This then gets used to form the “Base URL” of all avatars as well as the /support and /abuse page links in the app


#n2skteq
prologic
 (19 hours ago)

(#fvdkerq) @eldersnake@yarn.andrewjvpowell.com Fuck that’s what I was afraid of! @aman wrote this bit of code 😂 The idea here was to preserve the logged in Pod URI that could be access across multiple parts of the codebase using a service pattern. This then gets used to form the “Base URL” of all media as well as the /support and /abuse page links in the app. But damn we screwed this up 🤣 I will fix ASAP! But at least there’s a work-around 😅


#hvufgdq
prologic
 (19 hours ago)

(#fvdkerq) @eldersnake@yarn.andrewjvpowell.com Q: when you enter the Pod URL when logging in via the mobile app, do you enteryarn.andrewjvpowell.com or https://yarn.andrewjvpowell.com? 🤔 (it should not matter at all, but it might depending on my hunch and some code I’m aware of that has been written recently)


#qwydu3q
prologic
 (21 hours ago)

(#fvdkerq) @thecanine I can confirm that hitting the “View Raw” button on any of the large files in the dist/ folder managed by Git LFS downloaded as-is (no .zip for me) Hmmm 🤔 Strange 🤔 Some kind of Gitea / content-negotiation?


#acjzd4a
prologic
 (21 hours ago)

(#fvdkerq) Since you actually have a proper Android device physically in hand, I don’t suppose you could plug it into your PC, setup Flutter, clone the codebase (most of which I know you’ve already done) and do something like flutter run and run a live attached debug version on your phone and maybe you might see wtf is going on? 🤔 This is normally my workflow, but on my iPhone as I don’t have any other device 😢


#4xt5gcq