Is it possible to block a community on system level? i.e. !random@kbin.social is a massive nswf spam sink of hundreds kbin.social local accounts. Or should we rather remove/purge it entirely?

As of deep last light (cest), the error was identified and tchncs started to inform other servers about the events they were missing out on. It wasn't processing one of the outgoing queues correctly due to a well hidden typo in a configfile – causing one of the federation senders not identifying itself correctly.

You may run into a few recent messages that can't be decrypted, but otherwise everything federation related should be back to normal.

Sorry about this mess and thanks to everybody who has helped in identifying the issue.

Well hello again, I have just learned that the host that recently had both nvme drives fail upon drive replacement, now has new problems: the filesystem report permanent data errors affecting the database of both, Matrix server and Telegram bridge.

I have just rented a new machine and am about to restore the database snapshot of the 26. of july, just in case. All the troubleshooting the recent days was very exhausting, however, i will try to do or at least prepare this within the upcoming hours.

Update

After a rescan the errors have gone away, however the drives logged errors too. It's now the question as to whether the data integrety should be trusted.

Status august 1st

Well ... good question... optimizations have been made last night, the restore was successful and ... we are back to debugging outgoing federation :(

---

The new hardware also will be a bit more powerful... and yes, i have not forgotten that i wanted to update that database. It's just that i was busy debugging federation problems.

References

• federation issues after restore: https://github.com/matrix-org/synapse/issues/16025
• why we had to restore initially: https://text.tchncs.de/tchncs/about-the-matrix-incident-on-july-26-2023

Just in case we have people here who could not see the infobox on the statuspage due to adblockers :)

Crossgeposted von: https://lemmy.ml/post/2540925

cross-posted from: https://lemmy.ml/post/2540874

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This version brings major optimizations to the database queries, which significantly reduces CPU usage. There is also a change to the way federation activities are stored, which reduces database size by around 80%. Special thanks to @phiresky for their work on DB optimizations.

The federation code now includes a check for dead instances which is used when sending activities. This helps to reduce the amount of outgoing POST requests, and also reduce server load.

In terms of security, Lemmy now performs HTML sanitization on all messages which are submitted through the API or received via federation. Together with the tightened content-security-policy from 0.18.2, cross-site scripting attacks are now much more difficult.

Other than that, there are numerous bug fixes and minor enhancements.

Support development

@dessalines and @nutomic are working full-time on Lemmy to integrate community contributions, fix bugs, optimize performance and much more. This work is funded exclusively through donations.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. No one likes recurring donations, but they’ve proven to be the only way that open-source software like Lemmy can stay independent and alive.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency (scroll to bottom of page)

Upgrade instructions

Follow the upgrade instructions for ansible or docker. There are no config or API changes with this release.

This upgrade takes ~5 minutes for the database migrations to complete.

You may need to run sudo chown 1000:1000 lemmy.hjson if you have any permissions errors.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Für deine/eure klasse Arbeit hier!

Hoffe, du/ihr habt die Nacht gut überstanden. ;-)

Mit meiner neuen 'F-Droid' App auf Android 'Thunder' für Lemmy, klappt es hier besonders gut. 😃

see also https://status.tchncs.de/status/tchncs

Erwähnung von tchncs.de auf Golem (3. Seite)!

All of a sudden mentioning an ActivityPub e.g. Mastodon group does not create its Lemmy community posting anymore, see https://social.tchncs.de/@erAck/110758480657084086 That worked before..

Hi there! Last time I posted here, my problem was solved quickly so I'll try one more time. :)

I would like to migrate/mirror one of my reddit subs on here including a lot if not all posts. This would mean the following things in excalating order:

• Make a bot crosspost every new post on the sub
• Copy seed content (like 50 or 100 posts?)
• Copy the entire sub history

I have read that this can strain an instance (at least the last one I suppose) and I would like to know if it is ok to do so and if I need any help from someone with high permissions. Optimally, I'd do point three but 1 or 2 would be good as well.

Have a good one! :)

Hi there! Not sure if this is the right place to ask but I tried to upload an icon and a banner to a community I recently made. It's throwing this error: {"data":{"msg":"Error interacting with filesystem","files":null},"state":"success"} both on firefox and chrome. I filed an issue on github with the frontend but I thought maybe it's just me making an error that is known here. Mods: Feel free to delete if this is the wrong place to post.

Have a great day! :)

Werden eigentlich Downvotes federiert, oder stammen alle Downvotes, die ich sehe, von der Instanz hier?

This instance was updated a little while ago.

You might have heard of the recent security incident on some instances – that specific xss fix had been added to this instance in advance. However, there are no custom emojis yet, which was the source of that incident. But .... I'll likely add some soon. :)

Creating a community also creates a corresponding ActivityPub Group, like for example for !libreoffice there's also @libreoffice@discuss.tchncs.de. But, its description stays whatever was entered first for the community and doesn't get updated on changes. Any way to force that?

Is this also fixed on tchncs? Beehaw went offline to fix it, so I assume this is pretty important.

BTW thank you for hosting this instance!

If not, then it is time to do it now, before it is too late.

Crossgeposted von: https://lemmy.ml/post/1808829

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This release includes major improvements to performance, specifically optimizations of database queries. Special thanks to @phiresky, @ruud, @sunaurus and many others for investigating these. Additionally this version includes a fix for another cross-site scripting vulnerability. For these reasons instance admins should upgrade as soon as possible.

As promised, captchas are supported again. And as usual there are countless bug fixes and minor improvements, many of them contributed by community members.

Upgrade instructions

Follow the upgrade instructions for ansible or docker.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for almost three years. This is largely thanks to support from NLnet foundation.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. No one likes recurring donations, but they've proven to be the only way that open-source software like Lemmy can stay independent and alive.

Has this instance already blocked threads ? If not, is there any appetite for that ?

I suspect that this will be an important consideration for many users choice-of-instance in the future.

Die aktuellen Erfahrungen der Lemmy Instanz Lemmy.world mit dem RC10 der 18.1 sehen sehr vielversprechend bezüglich der Serverauslastung aus.

Lemmy.world status update 2023-07-05

cross-posted from: https://lemmy.world/post/1061471

Another day, another update.

More troubleshooting was done today. What did we do:

• Yesterday evening @phiresky@phiresky@lemmy.world did some SQL troubleshooting with some of the lemmy.world admins. After that, phiresky submitted some PRs to github.
• @cetra3@lemmy.ml created a docker image containing 3PR's: Disable retry queue, Get follower Inbox Fix, Admin Index Fix
• We started using this image, and saw a big drop in CPU usage and disk load.
• We saw thousands of errors per minute in the nginx log for old clients trying to access the websockets (which were removed in 0.18), so we added a return 404 in nginx conf for /api/v3/ws.
• We updated lemmy-ui from RC7 to RC10 which fixed a lot, among which the issue with replying to DMs
• We found that the many 502-errors were caused by an issue in Lemmy/markdown-it.actix or whatever, causing nginx to temporarily mark an upstream to be dead. As a workaround we can either 1.) Only use 1 container or 2.) set ~~proxy_next_upstream timeout;~~ max_fails=5 in nginx.

Currently we're running with 1 lemmy container, so the 502-errors are completely gone so far, and because of the fixes in the Lemmy code everything seems to be running smooth. If needed we could spin up a second lemmy container using the ~~proxy_next_upstream timeout;~~ max_fails=5 workaround but for now it seems to hold with 1.

Thanks to @phiresky@lemmy.world , @cetra3@lemmy.ml , @stanford@discuss.as200950.com, @db0@lemmy.dbzer0.com , @jelloeater85@lemmy.world , @TragicNotCute@lemmy.world for their help!

And not to forget, thanks to @nutomic@lemmy.ml and @dessalines@lemmy.ml for their continuing hard work on Lemmy!

And thank you all for your patience, we'll keep working on it!

Oh, and as bonus, an image (thanks Phiresky!) of the change in bandwidth after implementing the new Lemmy docker image with the PRs.

Edit So as soon as the US folks wake up (hi!) we seem to need the second Lemmy container for performance. So that's now started, and I noticed the proxy_next_upstream timeout setting didn't work (or I didn't set it properly) so I used max_fails=5 for each upstream, that does actually work.

I am not familiar with the legal situation this instance's server and owner is in, are there any actions a user could take that could expose the operators to legal liability? Could the instance face problems if someone posts a link to pirated content? What about general discussion of piracy? Or any other possibly legally problematic content?

At the moment I don't have the means to provide financial support but still wanted to say thank you for providing this instance, a place for those wanting to join the fediverse but not wanting to join the major instances. Once I have the financial means again I'll definitely consider supporting!

Thank you for your commitment..

"Beim nächsten Cryptocafe am 19.07.2023 um 19 Uhr in der Alten Mu (Raum C20) starten wir mit einem Vortrag von Ulf zum Thema: "Angriffe mit generativer KI"

Ihr seid herzlich eingeladen!"

Hört sich interessant an, ich werde versuchen, da zu sein...

cross-posted from: https://lemmy.world/post/465785

Android

• Jerboa Official Android client.

  • Currently latest version (v0.0.35) works only with v0.18 Lemmy instances. Download v0.0.34 from Github releases until instances switch to new Lemmy
  • Community: !jerboa@lemmy.ml
  • Github: link
  • Google play: link

---

• Thunder app

  • Community: !thunder_app@lemmy.world
  • Github: link

---

• Liftoff

  • Community: !liftoff@lemmy.world
  • Github: link
  • Playstore: link

---

• Summit

  • Community !summit@lemmy.world
  • Google play: link

---

• Connect for Lemmy

  • Community !lemmyconnect@lemmy.ca
  • Google play: link

---

• Sync for Lemmy (Announced)

  • Community: !syncforlemmy@lemmy.world

---

• Lemming

  • Community: !lemming_app@lemmy.world
  • Github link

---

• Lemmotif

  • Community: !lemmotif@lemmy.world
  • Playstore: link

---

• Artemis (Announced)

  • Community: !ArtemisApp@kbin.social

---

• Lemmy Fennec

  • Github: link

---

• Beyond (No release yet)

  • Community: https://lemmy.world/post/355285

---

• Warami (No release yet)

  • Github: link

---

• Slide for Lemmy (Announced)

  • Community: !slide@feddit.uk

---

• Lemmur (Abandoned)

  • Github: link

---

---

IOS

• Memmy for IOS

  • Community: !memmy@lemmy.ml
  • Github: link
  • Testflight: link

---

• Thunder app

  • Community: !thunder_app@lemmy.world
  • Github: link
  • Testflight: link

---

• Mlemapp

  • Community: !mlemapp@lemmy.ml
  • Github: link
  • Testflight: link

---

• Liftoff

  • Community: !liftoff@lemmy.world
  • Github: link
  • Testflight: link

---

• Olympus

  • Community !olympusapp@sh.itjust.works
  • Testflight link

---

• Artemis (Announced)

  • Community: !ArtemisApp@kbin.social

---

• Cavy (No development?)

  • Github: link

---

• Ares (No release yet)

  • Github: link

---

• Beyond (No release yet)

  • Community: https://lemmy.world/post/355285

---

• Morpha

  • Community: !morpha@vlemmy.net
  • Github: link

---

---

Linux

• Lemoa GTK client

  • Github: link

---

• Liftoff

  • Community: !liftoff@lemmy.world
  • Github: link

---

• Lemonade GTK4 client

  • Github: link

---

• NeonModem

  • Website: link
  • Github: link

---

---

Windows

• Liftoff

  • Community: !liftoff@lemmy.world
  • Github: link

---

MacOS

• Liftoff

  • Community: !liftoff@lemmy.world
  • Github: link
  • Testflight: link

---

---

Web based

• Slemmy

  • Github: link
  • Website: https://slemmy.libdb.so/

---

• Wefwef

  • Github: link
  • Website: https://wefwef.app

---

• Createlab

  • Github: link
  • Website: https://createlab.io/

---

• sx-lemmy

  • Github: link
  • Website: https://sx-lemmy.vercel.app/

---

---

Browser extensions

• Mullem

  • Firefox addon: link