• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle



  • That’s not how it works. Or, rather, that’s not only how it works. Sure, advertisers dream of users who see an ad once and run to buy a product. But ad effects are spread over time. They build brand recognition. They fake familiarity. Say you are in a supermarket and you want to buy a new type of product that you haven’t bought before. Very likely you’ll pick something familiar-sounding, which you heard in an ad. Ads pollute the mind even if the most obvious effects are, well, obvious and easily discarded, more subtle influence remains.



  • Gutting defeated/ousted manager’s projects is an obligatory and unavoidable ritual in corporate environment. Competent or convenient employees are pulled into other teams, pesky/unconvenient ICs are fired since everything can be pinned on the loser. Projects are often dismantled - even profitable ones to remove any possible foothold for a comeback. Shit, now I want to write a corpo book but styled like high school biology textbook.




  • Email is not only 1:(small N). Maillists do exist and and are used to facilitate discussions between a large amount of people via email. They are also often public so anonymous readers and search indexers can use them.

    /all is certainly an interesting thing - default Active sorting calculates a rank based on the score and time of the latest comment, with decay over time. If Threads are connected they would dominate /all. But there can certainly be adjustments, we can create a new sorting style, and make it default. For example:

    • Posts are deprioritized based on MAU or some similar metric. The larger the MAU, the lower the post is ranked assuming the same engagement. If the post got 100 upvotes on an instance with 1000 users, it’s probably a much more interesting post, than the post that got 100 upvotes on an instance with 100 000 000 users.
    • Posts are (de)prioritized based on instance source. For example setting Threads to -1000 would effectively remove it, setting Threads to -50 would allow you to see only super active posts. On the other hand if we want to see more content from less populated instance we might set it (i.e. german lemmy feddit.de) to the score of 100.
    • Instances can provide a limited number or percentage of /all - i.e. after we got 10 posts from Threads, stop getting posts from this instance.

  • I don’t know. I would like to subscribe to someone on Threads from Mastodon (since both are Twitter alternatives), if they don’t have Mastodon account (which let’s be honest they probably don’t). Zuck does not get any of my data (besides what’s available publicly anyway). If Threads decides to go full EEE, I’ll stop getting updates from people on Threads, same as I don’t get updates from people on IG right now. I think proliferation of ActivityPub protocol would be the greatest advantage.

    Moreover, I think we should follow the email architecture - I might use i.e. Proton Mail, but it does not prevent me from sending emails to Gmail, which I think is a bad provider, who collects a lot of user data. In fact if Proton Mail forbade sending email to Gmail I would be really displeased about that.

    The goal is to allow people to choose where they want to go and ActivityPub is what can help with that, unlike blocking Threads.