Alexia ΘΔ

I am still trying hard to figure out how we could bring the usual tumblr reblogging ux onto here but none of the solutions quite work

replies are the closest but fedi doesn't usually yap in tags in replies (outside of wafrn)

quotes could work, but to display a rewoot-chain we'd have to go like…

  • load post
  • load "rewooted" (quoted) post
  • load quoted post in quoted post…
  • keep going until you reach the final post

which um…isn't particularly fast. and we'd rather keep the site operating well rather than doing stuff like this


#wafrn #wafrnDev #struggling-to-figure-this-out #nerds-u-gotta-assemble-here-rn-I-swear
Mar 17 at 11:40pmWeb
Show threadF3715HMar 17
@alexia also this can essentially result in hour-long cloggings and excessive traffic unless that's all cached server-sided, which then results in even more storage and traffic at said server.
Show threadKett‮Mar 17
i don't think the tumblr UX meshes well with inter-communicating with other social media sites which are decidedly twitter-like, it'd be matter of hiding information on the wafrn side (per-"reblog" statistics) which would still exist elsewhere in fedi and bsky
Show threadBolet modo Sombrero de paja 🏴‍☠️  Mar 17

Well that recursiveness is something we already have when showing threads. Rewoot chains could work if we allow rewoots of rewoots, but that would not capture all.

I remember talking with someone here about the real implications of tags and what tagging something meant in Tumblr. It's the little UX details that make the difference

Show threadkopper Mar 18
@alexia you can have postgres handle the recursion on the database end with a recursive cte
Show threadkopper Mar 18
@alexia I'm surprised you're not using those for replies but thinking it through y'all prolly flatten those to just the topmost post
Show threadAlexia ΘΔMar 18
whatever sensible design you're thinking of, chances are we don't do that because Jank :3