[–] 8 points 15 hours ago (1 child)

Thank you for doing this again! As always, it was a lot of fun, though I feel like I didn't even see half of what the game had to offer 😅 Finally managed to rebuild my ship at some point, but didn't have the time to set off on a voyage yet. Oh well :)

  • source
  • [–] 3 points 15 hours ago (4 children)

    I'm still trying to get used to Lemmy; the main thing confusing me is the federated bit.

    I just want to access Lemmy and its content; how do I do that?

    You should be able to see pretty much anything from any instance. That's kind of the point :)

    Currently I'm just going to old.lemmy.world and using that as a starting point.

    It's worth noting that old.lemmy.world doesn't use my fork of mlmym (yet? I should write to them about this), so you are missing out on a few features, most notably user preferences, which you'll need to go to the normal lemmy.world UI for. But that shouldn't generally be a problem.

    1. I really don't like cloudflare and have it disabled in Javascript. I don't want to leave it enabled for lemmy.world.

    I don't remember right now whether lemmy.world uses cloudflare (it looks like it does, for mlmym at least). There are probably other instances that don't use it, but most will use some kind of anti-bot system. In the end, it's a matter of choosing the option you're most comfortable with :)

    mlmym itself shouldn't need any JavaScript, although some things will be slightly nicer with it enabled (voting, replying, and so on don't require a page reload, for example).

  • source
  • [–] 7 points 2 days ago

    Die Formulierung klingt fast so als bräuchte man es dann nichtmehr weil es von lemmy mit der 1.0 ein neues offizielles Frontend geben könnte? Oder lese ich da zuviel rein. Weiß man bereits was bei 1.0 auf uns zu kommt?

    Es ist nicht so, dass es ab 1.0 ein neues Frontend gibt (lemmy-ui, das Standard-Frontend, wurde halt weiterentwickelt), sondern dass es für die API eine recht große Überarbeitung gab. Aktuell hat Lemmy die API-Version 3, ab 1.0 ist es Version 4. Aus diesem Grund ist es deutlich mehr Arbeit, Lemmy 1.0 zu unterstützen, als es einfach nur für 0.19 am Laufen zu halten. Das ist da wahrscheinlich gemeint.

    Scheint Voyager als Frontend zu nutzen

    Soweit ich weiß, ist Voyager einfach der Name der Test-Instanz (voyager.lemmy.ml). Das Frontend ist weiterhin lemmy-ui :)

  • source
  • parent
  • context
  • [–] 1 point 6 days ago (2 children)

    still haven't figured out the top bar being empty in most cases tho..

    Do you happen to have set your listing type to local in the preferences? (“show posts from [local] communities by default”)

    I was made aware of an issue with that today – basically, non-local communities are filtered out from the list when that is set, but the list only includes the top twenty communities in the first place, so it just ends up empty. Version 26.3.3 should fix this :)

  • source
  • parent
  • context
  • [–] 3 points 6 days ago (5 children)

    Nice! I don't know if you've done so yet, but I recommend enabling some options by default: SHOW_UNREAD_COMMENTS (this one is really useful!), LANGUAGE_TAGS, SHOW_CONTROVERSIAL, and, if you want it, EMBED_METADATA. They're just environment variables, set to 1 to enable.

    If you have any questions or problems, feel free to reach out to me!

  • source
  • parent
  • context
  • [–] 8 points 6 days ago (7 children)

    Everything I've done was written entirely by me, as I don't use AI on principle. I'm fairly sure it was used by some people to contribute to the FHF fork (I've seen CLAUDE.md added to gitignore), and the readme and docs did have that AI-generated “feel” to it, if that makes sense. That's mostly why I reverted them to what it looked like in rystaf's version in that commit. I couldn't tell whether AI had also been used for code, so I left that unchanged.

  • source
  • parent
  • context
  • view more: next ›