Skip Navigation
AMD disables "Anti-Lag+" in all supported games with new graphics drivers
  • The AMD devs must have experimented with injection and test played with the new drivers before release. I wonder why this wasn't caught by Valve then.

    I thought what should have happened was either the dev would get banned, or contacted by Valve and get told they technique should not be used, before driver release, and they could have worked with Valve to fix their code and/or VAC.

  • (CONCLUDED) VOTE: Help decide the future of the Episode Discussion thread bot!
  • I think at least some people do not watch every episode that is released ASAP, so having multiple threads for multiple episodes that are released at once is useful for not spoiling the latter episodes, so that's not spamming IMO.

    That said, even on Reddit where there were more users, those multiple-episode-at-once (or whole series-at-once like netflix) animes tends to get lower discussion participation, especially the episodes in the middle so I understand where you are coming from.

  • (CONCLUDED) VOTE: Help decide the future of the Episode Discussion thread bot!
  • How about a way to request the bot to create a post if it stopped (e.g. due to no one participating in previous episodes)? It would both lower the barrier of entry for people who want to talk about an episode and keep the post format consistent.

  • Nippon TV to Acquire Studio Ghibli as Subsidiary
    www.animenewsnetwork.com Nippon TV to Acquire Studio Ghibli as Subsidiary

    NTV would be largest shareholder of Ghibli with 42.3% share

    Nippon TV to Acquire Studio Ghibli as Subsidiary

    The Nippon TV (NTV) television broadcasting company announced on Thursday that it has decided to acquire 42.3% of the shares of world-famous animation studio Ghibli. This transaction, once completed, would make NTV the largest shareholder of the Ghibli, and turn the studio into a subsidiary of Nippon TV.

    26
    /kbin project management costs, financing, future plans
  • I felt slightly frustrated when I tried some Lemmy apps and they only offer a few largest instances in the initial setup and leave people to discover/find smaller instances by themselves.

    It is understandable that they don't want to present a thousand choices and confuse people, or get people to sign up for an instance that disappears a week later. Also, larger instances tend to get a snowball effect by receiving more donations / volunteers and scale better, other nodes are also more likely to help them if there are e.g. federation problems.

    However this effectively promotes an centralized ecosystem that both depends on and burdens a small number of key instances.

  • Is kbin.social still having federation issues?
  • Thank you for looking into it. I tried subscribing again and it went through, and several threads just got through to kbinMeta over there, so I'll cautiously say it seems to be fixed now.

    Glad to hear federation is being worked on, it does feel it needs to be more robust to live up to the promise that one gets the same experience no matter which instance (local or remote) one view a magazine from. (I'm not being critical, interoperability is always a hard problem no matter which stage of development it is)

    Again, thanks for the good work and for bringing kbin to us!

  • /kbin meta @kbin.social 1Fuji2Taka3Nasubi @kbin.social
    Is kbin.social still having federation issues?

    I ask because I made an account on https://lemmy.zip and the kbin.social magazines there seems to have incomplete contents. e.g. kbinMeta@kbin.social there only have one thread from 25 days ago. RedditMigration@kbin.social there seemed more up-to-date but number of comments are still less than what I can see directly on kbin.social.

    Another indication of trouble is that when I try to subscribe to a kbin.social magazine (like kbinMeta@kbin.social) it is stuck on Subscribe Pending seemingly forever and does not transition to subscribed/joined status.

    At first I thought it is a configuration problem on lemmy.zip or some recent version Lemmy incompatibility with kbin, but I was able to subscribe to fedia@fedia.io there fine and it seems to be getting updated contents.

    So somehow traffic is not flowing smoothly between kbin.social and lemmy.zip.

    @ernest, I hate to bother you but are you seeing something like this with other instances?

    7
    Episode Discussion | Star Trek: Strange New Worlds | 2x04 "Among the Lotus Eaters"
    • Still somewhat annoyed that there is no seat belt on the shuttle, even if it is to maintain continuity with TOS. M'Benga looked like he was going to bang his head and get a concussion when they were landing.

    • La'an: They won't see us coming.
      Zac: We totally saw you from the other side of the planet a hemisphere away.

    • What was Zac trying to accomplish? He lured them there with the Starfleet Delta, but he was not going to hitch a ride home. He expected whatever ship that comes to inspect to... forget and go away, or suffer some disastrous result when the crew become unable to function? Why not just stay low and be king if he wasn't planning to leave?

  • Locked
    should locking and forced "merger" of communities be allowed?
  • I wonder if one day Lemmy supports migration of communities whether this would become a problem. Do the mod own the subscriber list and can move it from one server to another without subscriber consent? Assuming the community on the original server will be deleted after migration, perhaps the migration process can include each subscriber given a (one-click) choice to move or unsubscribe. In addition there is the question whether mods are free to hand over a community to new mods if they want to.

  • Does it seem like we’re mixing two concepts, having servers for users and content?
  • Currently there are (is?) content-only servers like https://lemmit.online/ .

    I have been thinking perhaps the idea can be carried further and we can separate the user-facing front end and the back end.

    Imagine having multiple front end servers (e.g. fe1.site, fe2.site, ... fe5.site) all connecting to the same user database and the same back end server which serves the communities and contents etc (call it be.site for example). A user signs up once and can login to any front end server with the same account, create a community /c/whatever on e.g. fe3 and it will be accessible automatically on fe1-fe5.

    This is in addition to the back end federating with outside servers. Outside sees the community as be.site/c/whatever and users there as be.site/u/whoever. (or maybe make an alias like www.site/c/whatever www.site/u/whoever).

    Additional front end servers can be added to spread the load if there are many users. If done right the users shouldn't even need to choose (or be aware of) which front end server they log on to, it can be automatically load-balanced. Another idea would be that special front end servers can be created to only serve API calls for apps.

    I'm not sure if this will have bottleneck somewhere else, but I think this is an interesting idea to explore.

  • (Controversial) Should lemmy.world close registrations at a certain user count?
  • Would there be any benefit to lemmy.world admins running a lemmy2.world and redirecting new users to sign up there? It would spread the load and federation between the two should be easier due to proximity and having the same admins.

  • InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)1F
    1Fuji2Taka3Nasubi @kbin.social
    Posts 2
    Comments 20