[-] wintermute@feddit.de 70 points 10 months ago* (last edited 10 months ago)

Gibt es irgendein Update oder Lebenszeichen, dass daran gearbeitet wird, den Laden wieder auf Vordermann zu bringen?

Ich bin dran, nach dem 19.2 Update läuft der Server am Limit, 5000 Instanzen sind out of sync, ich habe ihn gerade rescaled um den Prozess zu beschleunigen, danach sollte es endlich wieder flüssiger laufen, also bitte habt noch etwas Geduld.

1
Downtime (feddit.de)
submitted 10 months ago* (last edited 10 months ago) by wintermute@feddit.de to c/main@feddit.de

Leider gab es technische Probleme mit dem Server, weshalb ich ein ca. 24h altes Backup einspielen musste, um die Kiste wieder ans Laufen zu bringen. Tut mir wirklich Leid ¯\(ツ)

42
submitted 11 months ago by wintermute@feddit.de to c/main@feddit.de

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

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 is very large with almost 400 commits since 0.18.5. As such we can only give a general overview of the major changes in this post, and without going into detail. For more information, read the full changelog and linked issues at the bottom of this post.

Improved Post Ranking

There is a new scaled sort which takes into account the number of active users in a community, and boosts posts from less-active communities to the top. Additionally there is a new controversial sort which brings posts and comments to the top that have similar amounts of upvotes and downvotes. Lemmy's sorts are detailed here.

Instance Blocks for Users

Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn't affect users from the blocked instance, their posts and comments can still be seen normally in other communities.

Two-Factor-Auth Rework

Previously 2FA was enabled in a single step which made it easy to lock yourself out. This is now fixed by using a two-step process, where the secret is generated first, and then 2FA is enabled by entering a valid 2FA token. It also fixes the problem where 2FA can be disabled without passing any 2FA token. As part of this change, 2FA is disabled for all users. This allows users who are locked out to get into their account again.

New Federation Queue

Outgoing federation actions are processed through a new persistent queue. This means that actions don't get lost if Lemmy is restarted. It is also much more performant, with separate senders for each target instance. This avoids problems when instances are unreachable. Additionally it supports horizontal scaling across different servers. The endpoint /api/v3/federated_instances contains details about federation state of each remote instance.

Remote Follow

Another new feature is support for remote follow. When browsing another instance where you don't have an account, you can click the subscribe button and enter the domain of your home instance in the popup dialog. It will automatically redirect you to your home instance where it fetches the community and presents a subscribe button. Here is a video showing how it works.

Authentication via Header or Cookie

Previous Lemmy versions used to send authentication tokens as part of the parameters. This was a leftover from websocket, which doesn't have any separate fields for this purpose. Now that we are using HTTP, authentication can finally be passed via jwt cookie or via header Authorization: Bearer <jwt>. The old authentication method is not supported anymore to simplify maintenance. A major benefit of this change is that Lemmy can now send cache-control headers depending on authentication state. API responses with login have cache-control: private, those without have cache-control: public, max-age=60. This means that responses can be cached in Nginx which reduces server load.

Moderation

Reports are now resolved automatically when the associated post/comment is marked as deleted. This reduces the amount of work for moderators. There is a new log for image uploads which stores uploader. For now it is used to delete all user uploads when an account is purged. Later the list can be used for other purposes and made available through the API.

Cursor based pagination

0.19 adds support for cursor based pagination on the /api/v3/post/list endpoint. This is more efficient for the database. Instead of a query parameter ?page=3, listing responses now include a field "next_page": "Pa46c" which needs to be passed as ?page_cursor=Pa46c. The existing pagination method is still supported for backwards compatibility, but will be removed in the next version.

User data export/import

Users can now export their data (community follows, blocklists, profile settings), and import it again on another instance. This can be used for account migrations and also as a form of backup. The export format is designed to remain unchanged for a long time. You can make regular exports, and if the instance becomes unavailable, register a new account and import the data. This way you can continue using Lemmy seamlessly.

Time zone handling

Lemmy didn't have any support for timezones, which led to bugs when federating with other platforms. This is now fixed by using UTC timezone for all timestamps.

ARM64 Support

Thanks to help from @raskyld and @kroese, there are now offical Lemmy releases for ARM64 available.

Activity now includes voters

Upgrade instructions

Follow the upgrade instructions for ansible or docker. The upgrade should take less than 30 minutes.

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

Pict-rs 0.5 is also close to releasing. The upgrade takes a while due to a database migration, so read the migration guide to speed it up. Note that Lemmy 0.19 still works perfectly with pict-rs 0.4.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

This month we are running a funding drive with the goal of increasing recurring donations from currently €4.000 to at least €12.000. With this amount @dessalines and @nutomic can each receive a yearly salary of €50.000 which is in line with median developer salaries. It will also allow one additional developer to work fulltime on Lemmy and speed up development.

Read more details in the funding drive announcement.

[-] wintermute@feddit.de 49 points 11 months ago

Threads wurde vorsorglich geblockt. Zucker kann mir mal den Berg runter rutschen.

[-] wintermute@feddit.de 47 points 11 months ago

Die beste Unterstützung ist ein respektvollen Umgang miteinander. Leider kommt es in letzter Zeit immer häufiger zu persönlichen Anfeindungen, was für mich persönlich der absolute Motivationskiller ist. Also haltet euch bitte an die Instanzregeln. : )

[-] wintermute@feddit.de 96 points 11 months ago

Defederated. What a waste of resources.

141
submitted 11 months ago* (last edited 11 months ago) by wintermute@feddit.de to c/selfhosted@lemmy.world

Forgejo v1.21 is available and comes with significant improvements to Forgejo Actions and the Forgejo runner. It also brings better user blocking, many documentation improvements, a shortcut button to open new PRs, mail notifications when new users are created and more.

[-] wintermute@feddit.de 44 points 1 year ago

Glad I switched to Forgejo some time ago, never looked back : )

1
submitted 1 year ago by wintermute@feddit.de to c/austria@feddit.de
[-] wintermute@feddit.de 37 points 1 year ago

back then, we all thought they were our normal breakfast spoons until we accidentally found photos of our roommates abusing them as sex toys

82
ich⛪iel (feddit.de)
submitted 1 year ago by wintermute@feddit.de to c/ich_iel@feddit.de
[-] wintermute@feddit.de 60 points 1 year ago

Extremistische Inhalte werden auf feddit.de nicht geduldet 🚫

[-] wintermute@feddit.de 36 points 1 year ago

All I can say is it would be a big, big loss.

Beehaw made me believe in the idea of building a healthy network, especially in the beginnings.
I remember the day I asked Chris to federate with us, we used allow-lists, and maybe this should have been the way to go, considering how much trash has happened in the meantime.

I totally agree with your criticism about the state of the platform itself, slow progress, missing and broken mod-tools etc. unfortunately it seems that development cannot keep up with the speed of growth and the associated demands.

So, imho, you make the Fediverse a better place that's why I hope you stay ;)

25
submitted 1 year ago* (last edited 1 year ago) by wintermute@feddit.de to c/main@feddit.de

geteilt von: https://lemmy.dbzer0.com/post/3480133

As always, I suffer so you don't have to :)

After programming.dev joined the fediseer, I noticed some new non-lemmy instances they censured for loli shit, so I decided to investigate them, as they often tend to be friendly or hostile to each other for various reasons, so you can discover a lot more of them through their blocks and wikis.

So I did just that and want to warn you about the following non-lemmy services which are either

  • Hosting lolicon and shotacon
  • Have been blocked by multiple loli instances for CSAM (MFW the loli creeps think you're too creepy...)
  • Supports pedophilia, bestiality, or call themselves "MAP"

So without further ado

  • posting_lolicon_xxxx
  • lolison_xxx
  • lolison_xxxxxxx
  • pawoo_xxx
  • mstdn_xx
  • youjo_xxxx
  • pedo_xxxxxx
  • baraag_xxxt
  • nnia_xxxxx
  • aethy_xxx
  • headpat_xxxx
  • fedibird_xxx

If you want to see my exact reasons for each censure, you can check them on fediseer through this url: https://fediseer.com/api/v1/censures_given/lemmy.dbzer0.com

108
submitted 1 year ago by wintermute@feddit.de to c/main@feddit.de

Es gab nun eine Weile keine Zwischenfälle mehr, sodass wir uns entschieden haben, die Föderation mit lemmy.world wieder freizugeben.

[-] wintermute@feddit.de 65 points 1 year ago* (last edited 1 year ago)

Die besagen Inhalte wurden auf lemmy.world entfernt und die Signup-Policy angepasst, daher habe ich die Deföderation aufgehoben.
Sollte irgendein verwegenes A*loch auf die Idee kommen solchen Content hier zu posten werde ich nicht zögern den Fall zur Anzeige zu bringen und voll mit den Behörden zu kooperieren, nur damit das klar ist.

EDIT: Es gab einen erneuten Vorfall, also bleibt die Deföderation doch erst einmal bestehen.

99
submitted 1 year ago* (last edited 1 year ago) by wintermute@feddit.de to c/main@feddit.de

Da unsere Mods heute wiederholt eingehendes CSAM von lemmy.word entfernen mussten, ist lemmy.world vorübergehend deföderiert.

[-] wintermute@feddit.de 44 points 1 year ago

Sexismus ist kein Schach-spezifisches, sondern ein gesamtgesellschaftliches Problem.

327
submitted 1 year ago* (last edited 1 year ago) by wintermute@feddit.de to c/main@feddit.de

Heute vor zwei Jahren ist die Instanz online gegangen,
und seit Montag dieser Woche treiben sich hier über 10k Lemmies herum!

Freu' mich über jede/n von euch, der die Instanz mit zu dem macht, was sie heute ist! 🥰

Ein besonderer Dank geht an alle Mods, ohne deren Hilfe all dies nicht möglich wäre!

35
submitted 1 year ago by wintermute@feddit.de to c/de_edv@feddit.de
59
submitted 1 year ago by wintermute@feddit.de to c/main@feddit.de

geteilt von: 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.

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.

371
ich🇷🇺iel (feddit.de)
submitted 1 year ago by wintermute@feddit.de to c/ich_iel@feddit.de

Von: abuse@ hetzner.com

Sehr geehrte(r) ,

wir haben eine Abuse-Meldung von 398-fz@rkn.gov.ru für Ihre IP-Adresse 188.34.203.14 erhalten.

Wir leiten diese Meldung automatisch zur Information an Sie weiter. Sie müssen darauf nicht antworten. Wir erwarten jedoch, dass Sie dies prüfen und potenzielle Probleme beheben.

Bitte beachten Sie, dass dies nur eine automatisch generierte Nachricht ist, auf die Sie nicht antworten müssen.

Mit freundlichen Grüßen

Abuse Team

Hetzner Online GmbH Industriestr. 25 91710 Gunzenhausen Tel: +49 9831 505-0 Fax: +49 9831 505-3 abuse@ hetzner.com www.hetzner.de

Registergericht Ansbach, HRB 6089 Geschäftsführer: Martin Hetzner, Stephan Konvickova, Günther Müller

Hinweise zur Verarbeitung Ihrer personenbezogenen Daten im Rahmen der Kommunikation mit Ihnen finden Sie unter: www.hetzner.de/datenschutzhinweis

На основании требования Генерального прокурора Российской Федерации или его заместителя о принятии мер по ограничению доступа к информационным ресурсам от 15.06.2021 № 27-31-2021/Ид6832-21 направляется уведомление о нарушении порядка распространения информации, размещённой по следующим URL-адресам: https://feddit.de/post/405318

Провайдер хостинга или иное лицо, обеспечивающее размещение данного информационного ресурса в сети «Интернет», обязаны:

  1. незамедлительно с момента получения настоящего уведомления проинформировать владельца информационного ресурса о необходимости незамедлительного удаления распространяемой с нарушением закона информации;

  2. по истечении суток с момента получения настоящего уведомления ограничить доступ к указанному информационному ресурсу в случае отказа или бездействия владельца информационного ресурса в удалении распространяемой с нарушением закона информации.

Владелец информационного ресурса обязан в течение суток с момента получения соответствующего уведомления от провайдера хостинга или указанного иного лица удалить распространяемую с нарушением закона информацию.

С уважением, Федеральная служба по надзору в сфере связи, информационных технологий и массовых коммуникаций

Based on the requirement of the Prosecutor General of the Russian Federation or his deputy to take measures to restrict access to information resources dated 15.06.2021 № 27-31-2021/Ид6832-21 a notification is sent about a violation of the distribution of information posted at the following URLs: https://feddit.de/post/405318

The hosting provider or another person ensuring the placement of the specified information resource on the Internet is obliged:

  1. immediately after receiving this notice, inform the owner of the information resource about the need to immediately delete the information disseminated in violation of the law;

  2. in case of refusal or inaction of the owner of the information resource to delete the information disseminated in violation of the law, after 24 hours from the date of receipt of this notification, restrict access to the specified information resource.

The owner of the information resource is obliged to delete information disseminated in violation of the law within 24 hours from the date of receipt of the relevant notification from the hosting provider or another person.

Sincerely, The Federal service for supervision of communications, information technology, and mass media

[-] wintermute@feddit.de 40 points 1 year ago
[-] wintermute@feddit.de 49 points 1 year ago

Ich bin persönlich strikt gegen eine Föderation, egal mit welchem Big-Tech Dienst.
Aber die Instanz ist letztlich für euch da, und wenn eine Mehrheit der Community die Daten gerne bei Meta & Co. sehen möchte, dann...

view more: next ›

wintermute

joined 3 years ago
MODERATOR OF