Il primo ministro ungherese Viktor Orbán ha annunciato la reintroduzione dei massimali sui margini di profitto su diversi prodotti alimentari per contrastare l'aumento dei prezzi.

A febbraio l'inflazione alimentare ha raggiunto il 7,1% su base annua, per la la farina addirittura il 44,3%.

Il governo garantirà che il ricarico commerciale non superi il 10% del prezzo all'ingrosso. Tra i prodotti interessati ci sono pollame, latte, olio, burro, uova a zucchero.

La misura entrerà in vigore a metà marzo e durerà fino a metà maggio con possibilità di proroga.

Non è la prima volta che il governo ungherese ricorre a questa misura. Già a cavallo tra il 2022 e il 2023 a causa della spirale inflazionistica - non solo sui prodotti alimentari - che aveva superato il 25% su base annua, era stato imposto il price cap su tutta una serie di prodotti.

Un provvedimento che all'epoca era stato contrastato da diversi economisti e dalla Corte di Giustizia europea che aveva evidenziato come si ponesse in potenziale conflitto con il mercato comunitario.

Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program.

DraconicNEO

• Include image alt text in post search

flamingo-cant-draw

• Add HTML classes to mentions
• Add new setting to block NSFW content

travis-jeans

• Add Verdana and Arimo fonts to Litely and Darkly variables file before Helvetica (Issue 1537)
• Improve colour contrast of the mini-overlay in the top right corner of link or image post thumbnails
• Upvote, downvote, view source, and favorite icons become larger when pressed to improve visibility on grayscale screens
• Improve screenreader accessibility by adding a main element to more pages (issue #2891)

dessalines

• Been working on getting lemmy-ui up to date for 1.0.0 .
• Extracting pagination cursor utils into a trait.

Nutomic

• Removing aggregates tables (fixes #4869)
• Enable english for all users to fix language issues
• Ignore accept-language header if not site languages are specified
• Add more options for image uploads
• Use connection url to configure email (fixes #5472)
• Use version from git to indicate unreleased changes
• Add config option to enable json logging
• Also search url field by default
• Fix federation of unban action (fixes #5454)
• Get rid of Option<Vec<_>> in api structs (fixes #2820)

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

🔍 LIBERATI DALLE TRAPPOLE DI GOOGLE!
È online la Guida Completa a SearXNG: privacy estrema, personalizzazione avanzata e istruzioni passo-passo per riprenderti il controllo delle ricerche!

👉 Scopri come:
✅ Impostare SearXNG su Brave, Chrome, Firefox, Librewolf Edge e Safari
✅ Attivare i motori etici (no tracking!)
✅ Usare l’istanza italiana searxng.devol.it
✅ Iscriversi alla newsletter settimanale
✅ Sostenere @devol per mantenere 30+ servizi alternativi

📖 Leggi, condividi, ribellati:
➡️ newsletter.devol.it/guida-completa-a-searxng-privacy-e-liberta-nelle-tue-ricerche-online

🧠 Perché questa guida?
Perché ogni ricerca su Google finanzia la sorveglianza di massa.
Perché i algoritmi manipolano ciò che pensi.
Perché un web libero si costruisce con scelte quotidiane.

🌟 Condividila con:
- Chi dice "Tanto non ho niente da nascondere"
- Attivisti che lottano contro la censura
- Smanetton* che odiano i servizi intrusivi

💸 PS: Se trovi utile la guida, offri un caffè a @devol@mastodon.uno: ko-fi.com/devol
Servizi liberi sopravvivono solo con il tuo aiuto.

We just released version 4.1.0 of NodeBB. Here are the latest features you can now take advantage of!

As an aside, for the first time in a long while, both @baris and I are working on the same codebase again. Up until version 4 was released, I'd been working on the activitypub branch and periodically merging in the latest changes from develop. It's nice to be home! :house_with_garden:

Improved federation of Group actors :left_speech_bubble:

We've improved the activity synchronization for followed group actors. Local updates/likes/etc. are now federated outward by the category in addition to those from remote users. Thanks to @rimu@piefed.social and @freamon who worked with me on debugging this one.

Mentions and Emoji now federating out in source.content :wave:

Emoji and mentions have been sent out to followers since v4, but that wasn't reflected in the raw markdown content that we also send along. That has been remediated now, and this change improves nodebb-to-nodebb federation.

Video object type now parseable :tv:

NodeBB is now able to ingest Peertube Video objects, and render then in a topic just like other pieces of content. Thanks @deadsuperhero@forum.wedistribute.org for prodding me to get this sorted out!

Ich habe ein bisschen Buch geschrieben!

Ein Kapitel über „IndieWeb und Fediverse“ im Fachbuch „WordPress 6 – Das umfassende Handbuch“, erschienen im @rheinwerkverlag, um genau zu sein.

Im November 2023 fragten mich @florian und @simon, ob ich Zeit und Lust hätte, ein Kapitel über das IndieWeb zu ihrem Buchprojekt beizusteuern.

Und da spätestens seit dem Studium der Plan, ein Buch zu schreiben, auf meiner „Big 5 for Life“-Liste steht, habe ich ohne groß darüber nachzudenken zugesagt.

Ich hatte 2007 so viel Spaß und Motivation beim Bloggen. Dazu kamen die Arbeit an meiner Bachelor-Thesis und ein paar Jahre später mein erster Artikel sowie eine fortlaufende Kolumne in einem Print-Magazin, dass ich mir gut vorstellen konnte, auch mal ein Buch zu schreiben. Zu der Zeit hatte ich auch bereits Kontakt zu Galileo Press (heute Rheinwerk-Verlag), die mich wegen eines Buchprojekts angefragt hatten. Damals standen die Themen „Web Accessibility“, „jQuery“ und „WordPress (evtl.)“ zur Debatte. Microformats, mein damaliges Steckenpferd, wurden leider als „nicht unbedingt […] „ergiebig“ genug“ für ein Buchthema angesehen. 🙂

Jetzt, nachdem ich die 30 Seiten für das Kapitel über „IndieWeb und Fediverse“ geschrieben habe, bin ich froh, klein angefangen zu haben. Ich habe unterschätzt, wie viel Arbeit das ist, aber auch gemerkt, wie viel Spaß es macht! Außerdem war es die perfekte Themenkombination!

Ich hoffe, dass Flo und Simon (und der Rheinwerk-Verlag) mich vielleicht auch eine Überarbeitung für das WordPress-7-Buch (und 8, 9, 10, …) schreiben lassen. Und wer weiß – vielleicht klappt es ja irgendwann doch noch mit einem ganzen Buch. 😉

Vielen Dank nochmal für die Chance, zumindest ein „bisschen Buch“ schreiben zu können!

@simon hatte eine Idee:

Wir starten Ende Februar eine neue kleine Veranstaltungsreihe: den KrautPress Website Club. Gemeinsam mit Matthias Pfefferle werden wir uns einmal im Monat treffen und ganz im Sinne des WordPress-Mottos „democratize publishing“ zusammen über persönliche Websites sprechen.

…und fand die perfekten Worte um mich zu umgarnen 🫶:

Matthias ist im deutschsprachigen Raum, aber vor allem in der WordPress-Welt, eine der Instanzen zum Thema IndieWeb. Mit ihm über kleine Ideen für Websites zu sprechen oder einen unerwarteten Deepdive zu Themen wie Webfinger, .well-known oder Webmentions zu machen, motiviert mich persönlich immer an meinem eigenen Blog zu arbeiten.

Also veranstalten wir am 26. Februar von 17:30-18:30 einen virtuellen KrautPress Website Club (in Anlehnung an den Homebrew Website Club) in dem wir an Simons, eurer und meiner Webseite basteln. Es wird um die Themen Social Web im Allgemeinen und dem IndieWeb und dem Fediverse im Speziellen gehen. Wir werden nicht über SEO oder Web-Shops sprechen 😉

Homebrew Website Club is a growing world-wide network of meetups for everyone who wants to take back their web experience from social media silos, and own their online identities & content, or just want support with blogging!

indieweb.org/Homebrew_Website_…

Wenn ihr dabei sein wollt, einfach in den Kommentaren des KrautPress Posts euer „Interesse bekunden“: krautpress.de/2025/erster-webs…

The Social Web Foundation will be at Fediverse House in Austin, TX on March 9 and 10, at the same time as South by Southwest Interactive. This is the first ever Fediverse event at SXSW, and we can’t wait to reach out to new and old fediversians at the event in downtown Austin. We’ll be coordinating two events at the space, and I’ll also be speaking on stage.

• I’ll be speaking with David Imel, Peter Cottle and Mike Masnick at 10AM at the “Fediverse Corner” roundtable panel. (RSVP)
• We’re organizing a Networking Session and Light Lunch for Fediverse participants and the fedicurious from 11:30AM to 1:30PM on Sunday, March 9. It’s the best place to meet up with Fediverse-involved people during South by. (RSVP)
• We’ll be having a deeper dive into ActivityPub and Fediverse technology at the Developer Meetup from 2PM to 3PM on March 9. We’ll have short presentations, and I’ll be doing a book signing for “ActivityPub: Programming for the Social Web“. (RSVP)

There are other great talks at Fediverse House during the two-day event; I’m especially glad to see Fediverse stalwart Cory Doctorow talking about publishing in the Fediverse. (RSVP)

Please use the RSVP links to register your interest, but don’t let it keep you from coming by. The more the merrier!

A conversational context is what the ForumWG uses to describe what you might see as a reply tree or comment thread. One of the short-to-medium term goals of the ForumWG is to get conversational backfill working reliably.

What this means — conversational backfill means that when you encounter a post/status/note/etc. (e.g. you're mentioned or boosted/shared something), there is a reliable and comprehensive way to retrieve the entire conversation around it, so you are not interacting with the object on its own, but in its proper context with all its sibling replies.

We plan to achieve this with a combination of a top-down (FEP-driven) and bottom-up (implementor-first) approach. While this sounds incongruent, top-down approaches tend to overcomplicate and bottom-up approaches tend to violate the protocol (unintentionally of course :joy:.)

There are a number of independent top-down efforts to achieve this:

• FEP-7888: Demystifying the context property
• FEP-171b: Conversation Containers
• FEP-76ea: Conversation Threads

These FEPs are in the R&D phase.

State of the Top-Down approach

At this time, the ForumWG is only recommending the following:

• Publishers SHOULD use context for grouping related objects in a thread (but this is not the only way to use context).

There is general agreement over:

• A context SHOULD resolve to a resource.

There are concerns over:

• What that resource is (as:OrderedCollection, a new type, something else?)
• What is included in that context (plain objects or activities)

State of the Bottom-Up approach

The bottom-up approach is results-oriented, and while certain implementors may follow certain FEPs, the overarching goal is "cross-compatible conversational backfill".

Separately, these implementors are (or have signalled interest in) implementing conversational backfill:

• FEP 7888
  
  • NodeBB (@julian) and Discourse (@angusmcleod@mastodon.social)
    
    • Attaches context to objects
    • context resolves to an OrderedCollection containing objects
    • Two-way conversation backfill is tested and working (7888 only).

    
    

  • WordPress (@pfefferle@mastodon.social) and Frequency (@jesseplusplus@mastodon.social)
    
    • Attaches context to objects
    • context resolves to an OrderedCollection containing objects
    • Outgoing conversational backfill is tested and working — others can backfill an entire conversation from these implementors.

    
    

  • Lemmy (@nutomic@lemmy.ml) and PieFed (@rimu@mastodon.nzoss.nz)
    
    • Have signalled interest (neither positive nor negative) in conversational backfill and are waiting and watching at this time.

    
    

  
  

• FEP 171b
  
  • Mitra (@silverpill@mitra.social)
    
    • Attaches context to activities
    • context resolves to an OrderedCollection containing activities
    • Incoming conversational backfill is tested and working — Mitra can backfill an entire conversation from FEP 7888 and 171b implementors (:tada: nice!)

    
    

  • Hubzilla (@scott@authorship.studio) and Streams (@mikedev@fediversity.site)
    
    • Attaches context to activities
    • context resolves to an OrderedCollection containing activities
    • Outgoing conversational backfill is tested and working (against Mitra)

    
    

  
  

What's Next

This thread will likely contain updates and discussion from related parties about their implementations and what they wish to do next. In the cruelest irony of ironies, because conversational backfill is not ubiquitous yet, you will need to "View Original URL" in order to see all of the replies.

The ForumWG will meet again on 6 March 13h00 EST where all of this will be discussed, as well as planning out the future focus items for the ForumWG.

If you are an implementor, there is no reason you cannot join the fray. Boost this post, reply to it, join the conversation(al context)!!

If you're not an implementor, boost me anyway :stuck_out_tongue:

Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program.

travis-jeans

• colorList includes CSS variables so theme developers can change the comment left border color (issue 2890)

dessalines

• Fix matrix id import. #5063
• Add ability to view your own sent reports.
• Use rust:1.81 for CI.
• Adding ability to resend verification email.
• Show comments for hidden communities.
• When verifying email, add note about waiting for approval.
• Adding a can_mod field to CommentView, PostView, and CommunityView.
• Adding a variable time_range_limit, rather than having many post sorts like TopSixHours
• Adding blurhash to image_details.
• Adding listing_type filter for modlog.
• Fix corepack bug.

Nutomic

• Show posts/comments from followed communities despite instance block
• Simplify slur regex
• Deleted user shouldnt break federation outbox (fixes #5441)
• Reduce usage of async_trait
• Rate limit changes (fixes #5287)
• Allow sending report only to admins (fixes #2414)
• Also remove private messages when banning user with "remove content"
• Ignore follow requests from kbin, mbin for private communities
• Fix hash check for pictrs binary
• Enable emails in Chinese
• Cors policy should allow any origin by default (fixes #5405)
• Merge functions for formatting local urls

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

Ibis is a federated encyclopedia which uses the ActivityPub protocol, just like Mastodon or Lemmy. If you want to start a wiki for a TV series, a videogame, or an open source project then Ibis is for you! You can register on an existing instance or install it on your own server. Then you can start editing on the topic of your choice, and connect to other Ibis instances for different topics. Federation ensures that articles get mirrored across many servers, and can be read even if the original instance goes down. Ibis is written in Rust and Webassembly, fully open source to make future enshittification impossible.

This release features a redesigned explore page to browse instances and recently edited articles. Articles now have federated nested comments, as well as more subscription options to get notified about new edits and comments. There are also lots of minor changes and improvements.

Changelog

• New explore page with list of instances which shows the topic, update time and list of recently edited articles
• Implement nested comments for articles
• Users can subscribe to articles, in order to
  get notified about new edits and comments
• Settings for instance name and topic
• Much better error handling
• Add HTML title tag for all pages
• Icons
• Make diff view readable in dark mode (thanks @Earthgames)
• Basic about page
• Show pending edits which have not federated yet
• Various bug fixes

The next major version 0.3.0 will include federation with Lemmy, Mastodon and other compatible Fediverse platforms. The plan is to treat each Ibis instance as a community, with articles as posts. This way users on Lemmy and compatible platforms can directly browse, read and comment on wiki articles.

To follow Ibis development subscribe to !ibis@lemmy.ml or join the Matrix chat. Contributions to the source code are more than welcome.

Ibis is a federated encyclopedia which uses the ActivityPub protocol, just like Mastodon or Lemmy. If you want to start a wiki for a TV series, a videogame, or an open source project then Ibis is for you! You can register on an existing instance or install it on your own server. Then you can start editing on the topic of your choice, and connect to other Ibis instances for different topics. Federation ensures that articles get mirrored across many servers, and can be read even if the original instance goes down. Ibis is written in Rust and Webassembly, fully open source to make future enshittification impossible.

This release features a redesigned explore page to browse instances and recently edited articles. Articles now have federated, nested comments, as well as more subscription options to get notified about new edits and comments. There are also lots of minor changes and improvements.

Changelog

• New explore page with list of instances which shows the topic, update time and list of recently edited articles
• Implement nested comments for articles
• Users can subscribe to articles, in order to
  get notified about new edits and comments
• Settings for instance name and topic
• Much better error handling
• Add HTML title tag for all pages
• Icons
• Make diff view readable in dark mode (thanks @Earthgames)
• Basic about page
• Show pending edits which have not federated yet
• Various bug fixes

The next major version 0.3.0 will include federation with Lemmy, Mastodon and other compatible Fediverse platforms. The plan is to treat each Ibis instance as a community, with articles as posts. This way users on Lemmy and compatible platforms can directly browse, read and comment on wiki articles.

To follow Ibis development subscribe to !ibis@lemmy.ml or join the Matrix chat. Contributions to the source code are more than welcome.

Ibis is a federated encyclopedia which uses the ActivityPub protocol, just like Mastodon or Lemmy. If you want to start a wiki for a TV series, a videogame, or an open source project then Ibis is for you! You can register on an existing instance or install it on your own server. Then you can start editing on the topic of your choice, and connect to other Ibis instances for different topics. Federation ensures that articles get mirrored across many servers, and can be read even if the original instance goes down. Ibis is written in Rust and Webassembly, fully open source to make future enshittification impossible.

This release features a redesigned explore page to browse instances and recently edited articles. Articles now have federated, nested comments, as well as more subscription options to get notified about new edits and comments. There are also lots of minor changes and improvements.

Changelog

• New explore page with list of instances which shows the topic, update time and list of recently edited articles
• Implement nested comments for articles
• Users can subscribe to articles, in order to
  get notified about new edits and comments
• Settings for instance name and topic
• Much better error handling
• Add HTML title tag for all pages
• Icons
• Make diff view readable in dark mode (thanks @Earthgames)
• Basic about page
• Show pending edits which have not federated yet
• Various bug fixes

The next major version 0.3.0 will include federation with Lemmy, Mastodon and other compatible Fediverse platforms. The plan is to treat each Ibis instance as a community, with articles as posts. This way users on Lemmy and compatible platforms can directly browse, read and comment on wiki articles.

To follow Ibis development subscribe to !ibis@lemmy.ml or join the Matrix chat. Contributions to the source code are more than welcome.

Ich habe einen neuen Podcast! 🎉

…naja, nicht ganz ☺️

Aber ich darf (neben Courtney Robertson, Dave Lockie und Robert Jacobi) eine Show auf @dothewoo.io hosten!

Knapp 17 Jahre nach der ersten und fast 14 Jahre nach der letzten Episode des OpenWebPodcasts darf ich wieder mit Gästen über das Fediverse, das IndieWeb, das OpenWeb im Allgemeinen und diesmal speziell (aber nicht zwingend) im Kontext von WordPress sprechen.

Same Same But Different: Der Titel ist erschreckend ähnlich (obwohl ich damit nichts zu tun hatte und Bob den OpenWebPodcast nicht einmal kannte), die Themen sind auch gleich (ich bin leider inselbegabt) mit dem neuen Fokus auf WordPress und auch bei den Gästen wird es vielleicht Überschneidungen geben.

Was wirklich neu ist: Der Podcast ist auf Englisch – und genau davor hatte/habe ich bisher den größten Respekt.

Die erste Episode ist schon „im Kasten“ und sollte in den nächsten zwei Wochen live gehen (ich glaube es wird sogar ein Video geben).

Ein riesiges Dankeschön vor allem an @alex, dass er als mein erster Gast das Versuchskaninchen gespielt hat ☺️

(wobei ich mir nicht mehr ganz sicher bin, ob ich das vorher wirklich erwähnt hatte… 🤔)

Es ist auf jeden Fall eine großartige Folge, in der wir über die noch großartigeren (WordPress-)Projekte von Alex sprechen.

Danke auch nochmal an Bob (@BobWP), dass er dem fediverse einen festen Platz in seinem Podcast eingeräumt hat!

Ihr könnt DoTheWoo übrigens auch über ActivityPub auf Mastodon oder jeder anderen fediverse Plattform eurer Wahl abonnieren! Folgt einfach @[url=https://dothewoo.io/@dothewoo.io]dothewoo.io@dothewoo.io[/url] oder klickt @dothewoo.io

Just wrapped up a call with @pfefferle@mastodon.social and @jesseplusplus@mastodon.social to review their implementations of FEP 7888, specifically in relation to conversational backfill.

:heavy_check_mark: individual objects serve a context property
:heavy_check_mark: that context property is a URL that resolves

One of the concerns raised was related to the OrderedCollection of items served by the context. Specifically, if the items presented in the collection were not in chronological order, NodeBB failed at importing some of the items as the inReplyTo referenced an object that did not exist.

The solution to this was to ensure that the collection items were in chronological order from oldest to newest. Once fixed:

:heavy_check_mark: the context resolved to an OrderedCollection containing objects
:heavy_check_mark: NodeBB was able to pull in the entire conversation

NodeBB used to guard against this by ordering all received items by chronological order, but I realized that while this worked 99%+ of the time, there are some fun (ahem...) individuals who send objects with timestamps way in the future.

Personally I think removing the sorting just to fix one edge case was premature. At the same time, I think specifying that the OrderedCollection be sorted in chronological order should be a requirement.

cc @trwnh@mastodon.social