Hi! I am a stranger on this instance, I have read a lot of warnings about the "tankie triad", but wanted to see for myself and keep an open mind.

I watched this video, and it made me want to take a deep dive into socialism/communism, with
as much objectivity as I can.
youtu.be/BeRjTtKFlVM

I understand how capitalism works, and I have doubts that it is a sustainable system for society long term, but social democracy has been a good way of keeping capitalism in-check in Norway. So even if capitalism is not ideal, it is in theory possible to tax the rich more and keep the whole thing going in the future. I also understand the exploitation and the extraction of surplus value, rent seeking etc.

Other capitalist countries such as the US is currently struggling with basic human needs. And that is "the shining beacon of capitalism".

In Norway it has for a long time been common to use the US as an example of what not to do.

What I am interested in learning is how society would operate and function under socialism / communism. More about the differences. Preferably from less dry sources than The Capital from Marx. Where can I learn more? Preferably a bit entertaining.

It is important to me that it is historically accurate and factually correct.

Look forward to your replies 😊

This is a chance for any users, admins, or developers to ask anything they'd like to myself, @nutomic@lemmy.ml , SleeplessOne , or @phiresky@lemmy.world about Lemmy, its future, and wider issues about the social media landscape today.

NLNet Funding

First of all some good news: We are currently applying for new funding from NLnet and have reached the second round. If it gets approved then @phiresky@lemmy.world and SleeplessOne will work on the paid milestones, while @dessalines and @nutomic will keep being funded by direct user donations. This will increase the number of paid Lemmy developers to four and allow for faster development.

You can see a preliminary draft for the milestones. This can give you a general idea what the development priorities will be over the next year or so. However the exact details will almost certainly change until the application process is finalized.

Development Update

@ismailkarsli added a community statistic for number of local subscribers.

@jmcharter added a view for denied Registration Applications.

@dullbananas made various improvements to database code, like batching insertions for better performance, SQL comments and support for backwards pagination.

@SleeplessOne1917 made a change that besides admins also allows community moderators to see who voted on posts. Additionally he made improvements to the 2FA modal and made it more obvious when a community is locked.

@nutomic completed the implementation of local only communities, which don't federate and can only be seen by authenticated users. Additionally he finished the image proxy feature, which user IPs being exposed to external servers via embedded images. Admin purges of content are now federated. He also made a change which reduces the problem of instances being marked as dead.

@dessalines has been adding moderation abilities to Jerboa, including bans, locks, removes, featured posts, and vote viewing.

In other news there will soon be a security audit of the Lemmy federation code, thanks to Radically Open Security and NLnet.

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. Recurring donations are ideal because they allow for long-term planning. But also one-time donations of any amount help us.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency

Disclaimer: I'm not an instance admin, just a user. I hope it's okay to post here.

Problem

I had several photos which wouldn't post for some reason. After poking around a bit, I found out that my home server has an upload size limit of 5 MB.

Now, an upload size limit is perfectly reasonable. Storage is expensive, and Lemmy is primarily designed for link aggregation and discussion, not file hosting.

However, the way Lemmy currently behaves when it encounters a large file is not ideal, and varies depending on the app/UI.

At best, you get a cryptic error message like {"data":{"msg":"Exceeded maximum dimensions","files":null},"state":"success"} or {"data":{"files":null,"msg":"Too many pixels"},"state":"success"}, and at worst, your webpage/app stalls for an indefinite amount of time.

Solution?

Obviously, it would be prudent to improve the comprehensibility of the error messages, but if there were a way to automatically compress large images to below the size limit, that would eliminate the error messages in the first place.

I believe most instances use Pict-rs to host images, is that correct?

I came across these discussion threads in the Lemmy and Pict-rs source code repositories:

• Allow resize to be set in config to reduce max image size, pictrs does support this #2416
• Support pre-processing uploaded media #3
• support resizing to a maximum area #6

Has anyone implemented automatic image compression on their Lemmy instance? If so, would they be willing to share their methods with other instance admins?

This feature would make things smoother for users, especially for new users who might not be aware of the upload size limit and just think "Lemmy doesn't work, I guess I'll go back to Reddit".

Wanted to start a convo with @johnonolan@mastodon.xyz from Ghost and @angus@socialhub.activitypub.rocks from Discourse about AP resource discovery.

A common use case from fediverse users is to be linked out to a site, and attempt to "bring it in" to their local instance/app of choice. This is done by taking the browser URL and pasting it into their site/app's search bar, or equivalent.

For example:

• Ghost: activitypub.ghost.org/warp-fac…
• Discourse: any forum topic

For context, last night I discovered that Ghost's latest blog post didn't make it into NodeBB, due to a bug on my end. I attempted to resolve it via URL but there was no AP resource at that URL. I ended up having to query the instance actor (which I happened to already know), and looking at the outbox.

To my knowledge there is no way to find a Discourse post or topic's AP resource ID without having a local Discourse account.

Would it be possible for you to send back an HTTP 301 Moved Permanently (or similar) if the Accepts header contains one of the AP-related types?

N.B. This probably has some overlap with @evan@cosocial.ca's HTTP Discovery Task Force, a 308 is recommended there.

Se hai intenzione di partecipare alla conferenza openSUSE 2025 2025 dal 26 giugno – 28, ci sono importanti requisiti per il visto di cui dovresti essere a conoscenza.

Se non sei cittadino di un paese Schengen, dovresti verificare i requisiti per il visto e le esenzioni per l'ingresso in Germania. Alcuni partecipanti potrebbero anche aver bisogno di una lettera di invito formale che spieghi la natura della visita. Un elenco alfabetico dei paesi che richiedono una lettera di invito è disponibile sul sito web del Ministero degli Esteri federale. Se hai bisogno di una lettera del genere, invia un'e-mail a ddemaio@opensuse.org il prima possibile.

Il Travel Support Program non copre il costo per ottenere un visto. I partecipanti sono responsabili di eventuali spese relative al visto.

La conferenza si svolgerà a Norimberga, in Germania.

Il bando è ancora aperto. Considera l'idea di presentare un discorso per la conferenza prima del 30 aprile. Le persone possono inviare discorsi in base alla seguente durata e argomenti:

Le presentazioni possono essere presentate per il seguente periodo di tempo:
Discorsi lampo (10 minuti)
Breve conversazione (30 minuti)
Discorso virtuale (30 minuti)
Lunga conversazione (45 minuti)
Officina (1 ora)
Per la conferenza sono elencate le seguenti tracce:
Nuvola e contenitori
Comunità
Sistemi integrati e Edge Computing
Nuove Tecnologie
Open Source
openSUSE
Open Source per le aziende: oltre il codice nel percorso di sostenibilità
I volontari che desiderano aiutare con l'organizzazione della conferenza sono incoraggiati a inviare un'e-mail a ddemaio@opensuse.org o a partecipare a riunioni settimanali della comunità.

Le conferenze necessitano di sponsor per sostenere eventi guidati dalla comunità per mantenere gli eventi liberi e aperti ai nuovi membri contributori. Le aziende possono trovare informazioni sulla sponsorizzazione o donare alla Geeko Foundation per assistere con i fondi che andranno alla conferenza.