#dev 2023-03-31
2023-03-31 UTC
# 
[0x3b0b] <[snarfed]> "that is indeed a common norm..." <- It's something that seems to come up tangentially every time someone tries to figure out a solution for Fediverse search, partly because: some of the people opposed to it seem to have what *to me* looks like either a conceptual disconnect between how public their posts *actually are* and how public they mean them to be; a different but partly overlapping subset of people are strongly
# [0x3b0b] concerned about protecting the people who *don't realize* how public some of what they post is; and some people - including instance admins - seem to expect a level of control over content *that has been federated to another server* that I don't personally think is *realistic*, whether it is *reasonable* or not.
# [0x3b0b] But yeah, my reason for requesting API access was straight up "I finally got to where almost anything I post on Twitter is posted to my website first, as most people should, and API access would make that enough easier to do that it's potentially the difference in whether I post anything to Twitter" so...
gRegor and geoffo joined the channel
[jacky], geoffo, wagle, gerben, mro, IWSlackGateway and pharalia joined the channel
# 
bkil I found this article excellent, although I would arrive at a different end conclusion. He threw out the baby along with the bathwater with ditching the whole backfeed concept due to the way he tried to hold onto having access the profile pictures and names in private. I would just stick to forwarding (05 embedding) everything anonymously until consented to if I wer him (although, I suggest just sticking to a dynamical Reader concept that waves away all such
# bkil About your specific comment on federation. Note that if you federate over the Fediverse it does not mean you automatically surrender and all content and rights to said content along with it. This misunderstanding probably stems from conditioning by silos. Providing federated communication technologies such as The Fediverse, NNTP, SMTP, SIP, XMPP or Matrix means just that: allowing for people to interact with you without having to register on _your_ property. It
# bkil doesn't mean that they want to "gift" away everything (such as signing a fine prints about your first born son). Many companies have a policy for including a reminder about that in the email footer of every employee so that nobody forgets this.
# bkil Similarly you can't just "steal" posts from random news websites from their Atom feed and republish them as your own.
# bkil Another thread. I agree that Reader is the way to go - also the direction I am heading towards. How come there is so low success rate and buzz in this area? Is there something better on the horizon perhaps that I should know of? https://indieweb.org/reader
# bkil I also find it peculiar that numerous articles within the wiki and within pages linked from there as recently as 2022 deal with UX & workflow nitpicks that have already solved by better Fediverse servers decades ago. I mean, these views had already existed in Friendica, Hubzilla and Diaspora from the start I think https://fasiha.github.io/yoyogi/about https://indieweb.org/wiki/index.php?title=reader&action=historysubmit&type=revision&diff=84908&oldid=75778
# bkil Same thing about https://indieweb.org/reply-context
# IWDiscordRelay <capjamesg#4492> I don't know what to say about this: https://twitter.com/elonmusk/status/1641680913661607936
# 
@elonmusk Algorithm goes open source at noon Pacific Time (twitter.com/_/status/1641680913661607936)
[KevinMarks] joined the channel
# bkil capjamesg Loqi aaronpk https://www.theregister.com/2023/02/22/twitter_algorithm_to_be_open/ [...] Section 230 of the Communications Decency Act states service providers hosting third-party content can't be held liable for whatever its users upload. Issue whether that section of the CDA immunizes Google when they make targeted recommendations. Tech industry giants don't want to lose this case, as it could mean they're held liable for the behavior of their
# bkil algorithms.
holiday_medley and [snarfed] joined the channel
# [snarfed] bkil re sgreger's GDPR article, did you read dgold's reply? unlike sgreger, he's an actual working GDPR lawyer, and he disagreed with many of sgreger's legal/GDPR claims. https://ascraeus.org/micro/1525556293/
[manton], geoffo, [schmarty] and [tantek] joined the channel
# 
capjamesg James Bot now has robust instructions: https://github.com/capjamesg/llm-chatbot
[aciccarello] joined the channel
# 
[manton] [capjamesg] That looks cool! Is it similar to services like https://chatthing.ai/? I’ve been wondering if that would work for documentation search.
# IWDiscordRelay <capjamesg#4492> It looks similar.
# IWDiscordRelay <capjamesg#4492> My solution is open source and thus a lot more flexible if you want to dive into the weeds.
# IWDiscordRelay <capjamesg#4492> The README should give you all you need to get it set up.
# IWDiscordRelay <capjamesg#4492> Everything is queryable via an API, so you could disable the front-end.
jonnybarnes joined the channel
# IWDiscordRelay <capjamesg#4492> https://cdn.discordapp.com/attachments/866577430886350869/1091420895857361058/Screenshot_2023-03-31_at_18.56.18.png
# IWDiscordRelay <capjamesg#4492>
lagash_ joined the channel
# 
[schmarty] Awaiting the patches to our social readers (jkjkjk) 😂 https://github.com/twitter/the-algorithm
# capjamesg This image from the accompanying blog is cool: https://cdn.cms-twdigitalassets.com/content/dam/blog-twitter/engineering/en_us/open-source/2023/twitter-recommendation-algorithm/simclusters.png.img.fullhd.medium.png
# capjamesg tbh they are behind IG on this: https://about.instagram.com/blog/engineering/designing-a-constrained-exploration-system :P
# [snarfed] the issues are hilarious: https://github.com/twitter/the-algorithm/issues . "What’s scala" "Don’t remove" "Why use scala?" "Why scala 2?" "Someone explain scala" "Scala"
# [snarfed] my favorite so far: https://github.com/twitter/the-algorithm/issues/3
barnaby joined the channel
# 
barnaby there’s surprisingly little elno-specific code https://github.com/twitter/the-algorithm/search?q=elon
[campegg], [tw2113_Slack_], holiday_medley and billbennettnz joined the channel
# [0x3b0b] <bkil> "About your specific comment on..." <- I'm definitely not talking about surrendering the content or any content rights. "Control" might not have been the right word. I'm talking about people who seemed to have the impression that they could be comfortable about what was happening to their public and unlisted posts because they trusted their instance admins and their followers, who didn't seem to recognize what level of trust that
# [0x3b0b] That and the fact that I very nearly decided I'd have to defederate my website from one instance because I found out its terms of service say that "Content on this instance must not be archived or indexed wholesale by automated means by any user or service" and at least at whatever wee hour of the morning I came across that, my train of thought had me convinced that the database holding my instance's copies of content federated to me
# 
[tantek] all this applies to /reply-context use-cases also