[DISC] Akuyaku Reijou Level 99: Watashi wa UraBoss desu ga Maou de wa Arimasen - Chapter 18.1
vvvvv @ vvvvv @lemmy.world Posts 17Comments 87Joined 2 yr. ago
I don't even care about ::: spoiler spoiler incest :::
that much, just want to see the fallout if Aka commits. Also anime S3 ending on the last frame of 123 would be glorious.
Binged Oshi no Ko. I read the first chapter when it was first released a few years ago as I like Kaguya, but due to a lack of interest in idols and idol culture did not continue reading. How wrong I was. Following recent, uh, interesting developments decided to try again. And I was not disappointed. The plot is great, and the characters are interesting to follow. I would prefer more focus on the revenge plot, but whatever. Random thoughts:
- Akane is a megamind who would be great in a more serious "battle of the minds" type of work. She really should not let her detective talents go to waste.
- Kana deserves better
- Chapter 123. Don't backtrack, Aka, you hack.
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 am still salty that Cheat Slayer got cancelled.
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.
Some of my favorites, skipping excellent suggestions by @lvxferre@lemmy.ml:
- Villainess level 99 - follows ridiculously OP and socially awkward Eumiella.
- Tearmoon Empire - tensei, not isekai. Good comedy about a princess who went back in time and now tries to prevent her demise.
- The Story of a Villainess Seducing the Heroine - yuri smut.
- My Mom Entered a Contract Marriage - the story from the villainess daughter PoV. We see the usual villainess plot through child eyes. Drawing quality is insane.
- Touch My Little Brother and You're Dead - funny comedy. MC is insane. Everyone has a plan.
I liked the gag on the last page.