pull down to refresh

Oh, my idea was just based on time (fetch older items less often), but basing it on the last change to engagement immediately made a lot more sense! My idea turned out to be a proxy metric for this, haha

That is exactly where I started off. Then I ran into updates for old contentious posts becoming hot again coming along too slowly. (Posts were the main item.)

Or maybe I can get @k00b to merge something, since I'm not dealing with a mega-corporation's API like it sounds in your case 👀

That is by far the best outcome. It takes away the need of priority rotation and guessing.

Back then, I was dealing with Facebook on the other end. The tool was based on Workspace which was a (now discontinued) clone of Facebook's code for businesses to use as intranet. A neat idea, but it didn't make it.
Even though I was writing the tool for a huge and prestigious customer, we couldn't convince them to assign resources to add such a feed.

Anyway, that's my bit in adding to your plea for @koob to help the man out. :)

4375 sats \ 4 replies \ @ek OP 11 Aug

not sure how bad that actually would be

reply
132 sats \ 2 replies \ @k00b 11 Aug

You want a most recently zapped feed? We discussed something like this yesterday. /recent/zaps perhaps.

reply
115 sats \ 1 reply \ @ek OP 11 Aug

Yes, I think that would be the most reasonable solution, as an overlap between internal and external interests

reply
55 sats \ 0 replies \ @k00b 11 Aug

Shouldn't be too bad with the right index.

reply
123 sats \ 0 replies \ @Kruw 11 Aug

Brilliant meme.

reply