LoqiAn algorithm in general is a series of steps used to to automatically perform computations and other operations to produce a result; on the IndieWeb many standards have user-centric algorithms for peer to peer site interactions; social media silos have user-exploitative algorithms for advertising and reinforcing addictive behaviors https://indieweb.org/algorithm
aciccarello[m]Given that the post refers to the algorithmic feed as a "shadow ban" I'm also skeptical
ambroisie, gRegorLove, ShadowKyogre, nertzy, jjuran, jackyonweb, jacky, opal, a_chou, KartikPrabhu, nolith2, dbohdan, lahacker, jetter, samwilson1 and [Murray] joined the channel; ShadowKyogre and jacky left the channel
[Ana_Rodrigues]I can see how that could be true - I mostly use the bookmark function now and many times I bump into posts with thousands of likes but not a single comment. The bookmarks are easy to access again whilst the “liked” posts and hidden away.
[Ana_Rodrigues]Now that “power point type” of posts on instagram are growing, I suppose that people want to save them to refer to them later instead of liking it and outing themselves (if the topic of the post is very personal). I do that…
Zegnat!tell [Murray] not sure if this was that you were thinking of, but treora has been to IndieWebCamps and builds WebMemex, which includes features like a full offline archive of pages (e.g. see https://blog.webmemex.org/2017/07/10/keep-all-the-gems/) … though cannot find that on the wiki right now either :o
[Murray]Zegnat: thanks, definitely something different but potentially useful in a different way, will check it out :thumbsup: (PS I believe "memex" is broadly used but niche term so not surprised its being used for a few different things; I know I've seen it crop up in a talk adactio gave a year or so ago as well)
[Murray]using replies was how I'd thought about it in my head; I guess the weird bit being that you'd need to post each instance, get the Twitter url, then post the next one with the correct reply URL. For a static site user (like me) I think that might be too big of a headache 😄 Doable, though...
[snarfed]I haven’t seen many people post threads literally on their site like this, ie as a series of separate reply posts. I doubt may people here have decent UXes for that on their site, esp anywhere near Twitter’s
[snarfed]also not sure it’s something we want to optimize for or recreate literally. an alternative would be posting normal full-length posts, and then customizing them into threads just for Twitter, a la https://brid.gy/about#silo-content
[Murray]I think that's how most threads would work for me, not that they're something I do often: it's an article split up into chunks. In that case, I'd agree that just posting a normal article would make sense
treoraZegnat et al.: FYI WorldBrain's Memex (= getmemex.com) has some shared history with my WebMemex project; we collaborated for some months, then went in somewhat different directions; I focussed on web page snapshotting for a while, and got distracted with other things; WorldBrain's version added more and more features and got a lot closer to what I had in mind for WebMemex.
[Murray]jacky: I agree that most threads are Twitter-specific, I guess I just see the examples I posted as something a little bit different. Related content, all sharing a specific theme, posted over a long period of time. That feels like a use for threads on my site 🤷
[Murray]yeah, I have something similar to that for tags and categories already, I guess here it's about having just a single page where everything is kept because I explicitly don't want them to be connected to other posts