ÖVP und SPÖ haben laut Angaben aus den Parteien Gespräche über eine allfällige Regierungszusammenarbeit aufgenommen. „Es laufen Gespräche darüber, ob eine Zusammenarbeit und der Abschluss für ein Regierungsübereinkommen möglich sind oder nicht“, hieß es heute aus der ÖVP.
Zurück zum Start. Ob sie wohl dieses Mal was zusammenbringen, was meint ihr?
Nichtmal jeder 20. Strom- und Gaskunde in Österreich hat letztes Jahr den Tarif gewechselt. Ich weiß nicht, wie die Zahlen in anderen Ländern sind, aber bitte prüft eure Verträge und wechselt alle paar Jahre.
377.840 Haushalte und Unternehmen haben 2024 ihre Strom- und Gaslieferanten gewechselt. „Die Wechselzahlen sind im Vergleich zum Jahr 2023 weiter gestiegen, auch wenn nach wie vor viel Luft nach oben ist“, sagte E-Control-Vorstand Wolfgang Urbantschi…
Nachdem die Kinder ausgezogen sind, steht bei vielen älteren Menschen Wohnraum leer. Das birgt ein großes Potenzial für den Wohnungsmarkt, sagen Experten. Doch in der Praxis gibt es Hürden.
Meiner Meinung nach sollte es günstiger sein, Eigentum zu kaufen und zu verkaufen. Die Gebühren (Grundbuch, Grunderwerbssteuer) sind viel zu hoch und sind schnell mal im Bereich eines Jahresgehalts. Da wird ein "Downsizing" unattraktiv.
Dem argentinischen Staatschef wird Betrug vorgeworfen, nachdem er anscheinend auf sozialen Medien Werbung für eine Kryptowährung machte, deren Wert später einbrach. Mit der Aktion bescherte er Investoren Millionenverluste.
Nachdem er den Beitrag gelöscht hatte, sagte Milei auf X, dass er nichts von der Entwicklung der Währung gewusst habe und beschuldigte seine politischen Gegner, den Vorfall auszunutzen.
Da hab ich einen krassen Vorschlag: keine Werbung machen für Investments, deren Hintergründe man nicht kennt?
Fixing PaperlessNGX Email Processing Issues After Restart
When running PaperlessNGX in Docker, I encountered an issue where certain emails were not processed after restarting the Paperless container in the middle of a batch processing operation. Paperless saw the emails in the inbox but incorrect
ly marked them as already processed.
Identifying the Issue
The first step to diagnose the issue was to check the mail.log file within Paperless. The log provided information on which emails were skipped from processing, including their unique IDs. For example: [2025-02-17 09:50:03,084] [DEBUG] [paperless_mail] Skipping mail '321' subject 'Email from Epson WF-4830 Series' from 'scanner@example.com', already processed.
Logging into the Database
To access the Paperless database running inside a Docker container, I used the following command: docker compose exec db /bin/bash This command opens a bash shell inside the db
... mehr anzeigen
Fixing PaperlessNGX Email Processing Issues After Restart
When running PaperlessNGX in Docker, I encountered an issue where certain emails were not processed after restarting the Paperless container in the middle of a batch processing operation. Paperless saw the emails in the inbox but incorrect
ly marked them as already processed.
Identifying the Issue
The first step to diagnose the issue was to check the mail.log file within Paperless. The log provided information on which emails were skipped from processing, including their unique IDs. For example: [2025-02-17 09:50:03,084] [DEBUG] [paperless_mail] Skipping mail '321' subject 'Email from Epson WF-4830 Series' from 'scanner@example.com', already processed.
Logging into the Database
To access the Paperless database running inside a Docker container, I used the following command: docker compose exec db /bin/bash This command opens a bash shell inside the db service container, allowing further interaction with PostgreSQL.
Resolving the Issue
To resolve the issue, I connected to the Paperless database, which was running on PostgreSQL. Using the provided email UID from the mail.log, I deleted the corresponding entries from the paperless_mail_processedmail table to allow Paperless to process the email again. psql -U paperless_db_user Here’s the SQL command I used: DELETE FROM paperless_mail_processedmail WHERE uid = '322'; After running this command for every of the reported mails that are skipped, Paperless successfully reprocessed the emails during the next processing cycle.
Conclusion
If you encounter similar issues with PaperlessNGX not processing certain emails after a restart, checking the mail.log and manually deleting the processed mail entries from the database can be an effective solution.
I've recently stopped using tmux in favour of relying fully kitty's built-in windows and tabs, and I'm a fan.
The real killer app for me was the "pass_keys" plugin that allows you to navigate vim and kitty splits all with the same keys. I think there are plugins that allow you to do the same between vim<>tmux<>kitty as well, so it's not like you would need to drop tmux to take advantage of it.
Anyway, so that's been a big shift in my daily workflow. I've been using tmux for well over a decade, and GNU screen before that (I was never able to train myself away from the C-a prefix.
The one thing I miss a lot is being able to quickly detach and re-attach to existing sessions. Especially when doing some work over an ssh connection. But then I can always just shove the terminal into scratch space, or another i3 workspace.
This isn't me trying to sell anyone o
... mehr anzeigen
I've recently stopped using tmux in favour of relying fully kitty's built-in windows and tabs, and I'm a fan.
The real killer app for me was the "pass_keys" plugin that allows you to navigate vim and kitty splits all with the same keys. I think there are plugins that allow you to do the same between vim<>tmux<>kitty as well, so it's not like you would need to drop tmux to take advantage of it.
Anyway, so that's been a big shift in my daily workflow. I've been using tmux for well over a decade, and GNU screen before that (I was never able to train myself away from the C-a prefix.
The one thing I miss a lot is being able to quickly detach and re-attach to existing sessions. Especially when doing some work over an ssh connection. But then I can always just shove the terminal into scratch space, or another i3 workspace.
This isn't me trying to sell anyone on ditching tmux. I love tmux, and if it works for your flow then it's perfect for you. More just curious what kinds of setup other people have.
Is there some hot new thing that I've missed that blows both kitty and tmux and i3 out of the water? Idk, but I'm always on the lookout. :p
Nein, ich werde und wurde nicht gefragt. R. Z.: Sie haben einmal mehr untersagt, ihre Werke so auszustellen, daß Sonnenlicht oder auch nur Tageslicht auf sie fallen könnte, und […]
Früher dominierten Bands die deutschen Single-Charts, heute sind es Solo-Künstler. Die Gründe sind vielfältig und zeigen: Das Musikbusiness hat sich grundlegend verändert. Ist das das Ende einer Pop-Ära?
Wen interessieren die Charts, wenn man einfach nur gute Musik hören will? Unkommerzielle und gute Bands gibt es wahrlich genug. Auch ganz ohne „Hochformat“.
Charts sind ja zum einen die Verkaufszahlen. Wenn sich Bands weniger verkaufen und weniger erfolgreich sind, dann ist das auch für dich relevant, weil es perspektivisch weniger Bands geben wird. Dann gründet keiner eine und alle machen die Solokarriere.
Die Bands die ich höre vermarkten sich grösstenteils selbst, und ich kaufe auch lieber direkt auf den Bandseiten als bei z.B Amazon, da hat der Künstler mehr von
Wenn so viele Wähler*innen Geschmack daran finden, dann kann der sog. Autoritarismus gar nicht genug untersucht werden. Die meisten Medien haben Probleme, das zu tun. Wo sind also die Perlen im Heuhaufen? Wer wie ich welche entdeckt, muss sie freilich auch lesen lernen. Denn die meisten sind nicht perfekt, sondern von Menschen und ihren Interessen gemacht. Selten decken die sich mit meinen. (ARTE / ZDF)
Wenn so viele Wähler*innen Geschmack daran finden, dann kann der sog. Autoritarismus gar nicht genug untersucht werden. Die meisten Medien haben Probleme…
LGR retrospective on the HP Mini 1000, one of the more popular PCs from the short-lived era of the netbook! If you could even call it an era. In hindsight, it was all a bit silly, even though the 45nm processors making it possible were quite exciting at that point in time. So join me in reviewing the Mini 1000 that I had back in 2009 (or close to it) and putting it through its paces 16 years later!
LGR retrospective on the HP Mini 1000, one of the more popular PCs from the short-lived era of the netbook! If you could even call it an era. In hindsight, i...
In diesem Beitrag erläutere ich, warum es wichtig ist, dass bei Block Themes wie Twenty Twenty-Five die Farben global in der Farbpalette festgelegt und/oder in der theme.json definiert werden. Das Szenario: Die Farbe für einen Hintergrund (blau) bei einem Block Pattern auf haurand.com entsprach nicht dem Farbspektrum unseres Corporate Design und musste geändert werden.
Ab 2027 gibt es in der EU einen CO₂-Emissionshandel für den Verkehr. Der ADAC erwartet deutliche Preiserhöhungen an der Zapfsäule – und fordert Entlastung durch ein Klimageld.
Die neue Bundesregierung müsse sehr schnell Entlastungsmaßnahmen beschließen, wenn sie die Akzeptanz für Klimaschutzmaßnahmen erhalten wolle, so Reinicke. Über ein Klimageld müssten Teile der Einnahmen aus dem CO₂-Preis rückerstattet werden, insbesondere an Verbraucher mit niedrigem Einkommen.
Sowas haben wir in Österreich. Je nach Region gestaffelt werden die Einnahmen der CO2 Steuer verteilt. Als Familie haben wir im letzten Jahr ~900€ auf diesem Weg bekommen.
Tykwer war das verdammt größte Genie des Planeten, als er den Film gegen Ende des letzten Jahrtausends abgeliefert hat. An dem würde er, für den Rest seines Lebens und auf ewig gemessen werden. Und für die Potente hätte ich, ohne zu überlegen, meine damals vielversprechende Karriere als Taxifahrer sofort an den Nagel gehängt…
Tykwer war das verdammt größte Genie des Planeten, als er den Film gegen Ende des letzten Jahrtausends abgeliefert hat. An dem würde er, für den Rest seines…
Sending much love and solidarity to all the public health workers who have been inexplicably fired from government agencies today. The world is far less safe as a result.
Mitmachen und einmischen: Für Solidarität und soziale Gerechtigkeit. Gegen Klimawandel, für mehr Demokratie und eine gerechte Verteilung des Reichtums.
Daran denke ich noch immer herum. Vor über acht Jahren, am 07. November 2016 nämlich, veröffentlichte ich in meinem Blog einen Text, in dem ich über Ursache und Wirkung […]
Die Kölner Critical Mass wird jeden letzten Freitag im Monat gefahren. Treffpunkt ist um 17:30 Uhr am Rudolfplatz unter dem Hahnentor, los geht es dann üblicherweise spätestens um 18:00 Uhr. #CMKöln
We have exclusive renders of the upcoming Pixel 9a, which is slated to launch on March 19. It'll sport a flat camera bump and the largest battery ever in
Dieses kleine bescheidene Textstück hat sich zur Aufgabe gemacht einigen, hoffentlich nicht wenigen politischen Akteuren dieses Landes eine kurze und klare Frage zu stellen. Und zwar nur jenen welchen die Grundlagen einer funktionierenden Demokratie noch etwas wert sind:
Was ist dir wichtiger, die eigene Macht oder eine unabhängige Demokratie für uns alle?
An die Macht zu kommen, diesmal hier und jetzt, oder ein für alle mal ein klares Zeichen zu setzten das in diesem Land rechtsradikale, menschenverachtende Strömungen keinen Platz haben?
Die Realität der letzten Wochen und Monate hat allen eindeutig vor Augen geführt das Netzwerke, soziale Vernetzung im Netz, nicht auf zentral verwalteten Plattformen stattfinden kann, denn die Macht über die Inhalte und ihre Verbreitung liegt immer beim Anbieter. Und das das einzige was dem Nachfragenden bleibt der Zweifel ist. Zweifel ob das was er sieht und das was die anderen sehen manipuliert wurde oder spezifisch dazu da ist, explizit nur ihm präsentiert zu werden, um nur dich z
... mehr anzeigen
Dieses kleine bescheidene Textstück hat sich zur Aufgabe gemacht einigen, hoffentlich nicht wenigen politischen Akteuren dieses Landes eine kurze und klare Frage zu stellen. Und zwar nur jenen welchen die Grundlagen einer funktionierenden Demokratie noch etwas wert sind:
Was ist dir wichtiger, die eigene Macht oder eine unabhängige Demokratie für uns alle?
An die Macht zu kommen, diesmal hier und jetzt, oder ein für alle mal ein klares Zeichen zu setzten das in diesem Land rechtsradikale, menschenverachtende Strömungen keinen Platz haben?
Die Realität der letzten Wochen und Monate hat allen eindeutig vor Augen geführt das Netzwerke, soziale Vernetzung im Netz, nicht auf zentral verwalteten Plattformen stattfinden kann, denn die Macht über die Inhalte und ihre Verbreitung liegt immer beim Anbieter. Und das das einzige was dem Nachfragenden bleibt der Zweifel ist. Zweifel ob das was er sieht und das was die anderen sehen manipuliert wurde oder spezifisch dazu da ist, explizit nur ihm präsentiert zu werden, um nur dich zu manipulieren.
Es sind nur noch wenige Tage bis zur bevorstehenden Wahl. Zu glauben jetzt noch, auf den letzten Metern, in den letzten Momenten entscheidendes mit schlagenden Argumenten zu erreichen mag dem guten Willen entspringen, und auch auf das gute im Menschen hoffen. Es ist aber, und das wissen alle im tiefsten Inneren, nicht mehr als eine Illusion. Eine Illusion erschaffen durch die allgemeingültig erscheinende Realität auf dem eigenen Bildschirm. Eine Realität, konstruiert nur für dich, für Sie und ihn. Virtuell und so illusorisch, wie die völlig andere Realität auf dem nächsten Bildschirm gleich neben an.
Und dennoch, und das ist der Ursprung dieses Aufrufs, gibt es bereits eine echte etablierte Alternative. Eine Alternative welche uns allen die Grundlagen unserer freien Entscheidungsfindung und unserer freien Meinungsäußerung wieder in unser aller Hände legt. Eine Option welche bereits eben diese Grundlage einer jeden unabhängigen Demokratie im hier und jetzt funktionstüchtig konstruiert hat.
Die dezentralen Netzwerke, unsere Netzwerke, beruhend auf dem #activityPub Protokoll machen dies möglich, und das einzige was es braucht seid ihr. Das einzige was es braucht ist das du endgültig die Entscheidung triffst mit uns allen und möglichst prominent die sinkenden Schiffe der monopolistischen Anbieter zu verlassen, gemeinschaftlich aufzubrechen in eine unabhängige weil dezentrale Zukunft. Und zwar jetzt, noch vor der Wahl. Jetzt, wenn die Aufmerksamkeit aller Akteure noch auf dem Geschehen im hier liegt und sich nicht bereits abgewendet hat. Abgewendet ins Reich der Auguren der nach der Wahl bestehenden Mehrheiten und den damit verbundenen Vorhersagereien und Spekulationen.
Die dezentralen Netzwerke stehen, selbst eure eigenen Parteien haben bereits eigene Knotenpunkte, eigene Instanzen errichtet. Das einzige was fehlt bist du, seid ihr.
Das einzige was fehlt ist ein Schildchen an euren alten abhängigen Netzwerkprofilen. Schildchen auf denen klar und unmissverständlich steht:
"#Gemeinschaftlich für eine freiheitliche Grundordnung. Profil Aufgrund von unhaltbaren Umständen geschlossen. Wir gehen #zusammen, ich warte auf euch auf der anderen Seite. euer XYZ"
I'm looking to finally get my spouse and I both onto a non-G email service with a custom domain. Having storage and calendars to replace Drive is the deal-maker with the spouse.
I've been using Proton as my alt email for years, but all the new crypto bells and whistles just seems sus from a business management perspective. I get it, they're Swiss, but still.
But looking at Mailbox.org, their 2FA situation seems bonkers. That's the dealbreaker for me.
All I really need is IMAP, webmail, and actual security without feeling like I'm going to be doing this all again in 5 years to get out from under another crypto bro.
I having issue with dolphin not showing folder icons correctly, most hidden folders are small and all linked folder are also small, If anyone know how to fix this please help
ActivityStreams Vocabulary defines a Follow activity, and ActivityPub defines its side effects of manipulating a followers collection, but ActivityPub does not specify a full algorithm for how to follow something. This FEP aims to provide guidance on which objects can be followed:
The object MUST have a followers collection present.
If the object does not have an inbox, then you MAY recurse upwards through attributedTo until you find a resource with an inbox. The maximum recursion depth SHOULD be 1.
A Follow activity can then be constructed for that object and delivered to the discovered inbox. Ad
ActivityStreams Vocabulary defines a Follow activity, and ActivityPub defines its side effects of manipulating a followers collection, but ActivityPub does not specify a full algorithm for how to follow something. This FEP aims to provide guidance on which objects can be followed:
The object MUST have a followers collection present.
If the object does not have an inbox, then you MAY recurse upwards through attributedTo until you find a resource with an inbox. The maximum recursion depth SHOULD be 1.
A Follow activity can then be constructed for that object and delivered to the discovered inbox. Additional requirements for the structure of the Follow activity are out-of-scope.
Requirements
In order to follow an object, we use a Follow activity. But in order to use this Follow activity, we need to know the following:
What can be followed?
Where do we send the Follow for that object?
At the time of writing, current software practices within the fediverse enforce a limit on what can be followed. For example, Mastodon currently limits follows to actors that can be mapped to their internal concept of "accounts", and these "accounts" are in turn limited to being any of the five "actor types" described in [AS2-Vocab]: Person, Group, Organization, Application, Service.
Consequently, other software which does not have such a conceptual limit is forced to declare their actors as one of the five types, or else Mastodon users will not be able to follow their actors. [ActivityPub] says that there is no specified mapping between "users" and "actors", but Mastodon's interpretation of "actors" as "users" de facto disallows following anything but a strict subset of resources.
We may therefore express Mastodon's requirements as follows:
The actor MUST have a type of any of Person, Group, Organization, Application, Service.
The actor MUST have an inbox where the Follow will be sent.
A proposed modified requirement and algorithm are as follows:
The object MUST have a followers collection present.
If the object does not have an inbox, then you MAY recurse upwards through attributedTo until you find a resource with an inbox. The maximum recursion depth SHOULD be 1.
Algorithm
Given an object O and a recursion limit L, a general algorithm for following it can be expressed like so:
(1) Initialize a variable INBOX.(2) If O.followers is not present, return an error OBJECT_CANNOT_BE_FOLLOWED.(3) If O.inbox is present, set INBOX to the referenced IRI.(4) If INBOX is unset, then initialize a variable R whose initial value is O.(5) While INBOX is unset:(5.1) Check that L > 0. If false, return an error MAX_RECURSION_LIMIT.(5.2) Dereference R.attributedTo and set the variable R to this referenced resource.(5.3) If R.inbox is present, set INBOX to the referenced IRI.(5.4) Set the variable L to the value L - 1.(6) Initialize a document ACTIVITY:(6.1) ...whose actor is yourself(6.2) ...whose type is Follow(6.3) ...whose object is O(7) Make an HTTP POST request whose target is INBOX and whose body is ACTIVITY.
Additional requirements for the ACTIVITY can be defined at a protocol level, but the exact protocol and those requirements are out-of-scope for this FEP. The scope of this FEP is limited to determining which objects can be followed, and where to send the Follow.
References
James M Snell, Evan Prodromou, [Activity Vocabulary][AS2-Vocab], 2017
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.
In theory, being able to follow arbitrary object could be useful in certain cases, but that blurs the line between actors and objects, and in my opinion, creates more problems than it solves. Furthermore, ActivityPub doesn't doesn't support this use case. According to section 6.5 Follow Activity, only actors can be followed:
The Follow activity is used to subscribe to the activities of another actor.
trwnh:
ActivityPub says that there is no specified mapping between “users” and “actors”, but Mastodon’s interpretation of “actors” as “users” de facto disallows following anything but a strict subset of resources.
Again, ActivityPub (overview):
In ActivityPub, a user is repr
... mehr anzeigen
trwnh:
Followable objects
In theory, being able to follow arbitrary object could be useful in certain cases, but that blurs the line between actors and objects, and in my opinion, creates more problems than it solves. Furthermore, ActivityPub doesn't doesn't support this use case. According to section 6.5 Follow Activity, only actors can be followed:
The Follow activity is used to subscribe to the activities of another actor.
trwnh:
ActivityPub says that there is no specified mapping between “users” and “actors”, but Mastodon’s interpretation of “actors” as “users” de facto disallows following anything but a strict subset of resources.
Again, ActivityPub (overview):
In ActivityPub, a user is represented by "actors" via the user's accounts on servers. User's accounts on different servers correspond to different actors.
Mastodon might be not right about hard-coding the list of actor types, but mapping users to actors is literally what specification tells us to do.
but mapping users to actors is literally what specification tells us to do.
mapping users to actors is fine mapping actors to users is not. the state machine works using actors as the basic unit of computation, which do not have to correspond to users. silverpill:
In theory, being able to follow arbitrary object could be useful in certain case
In practice, subscribing to topics is far more useful than subscribing only to people. Limiting subscriptions only to people just causes other entities to lie and say their resources are people too. See also: the use of Group to describe things that are not groups of people.
In practice, subscribing to topics is far more useful than subscribing only to people. Limiting subscriptions only to people just causes other entities to lie and say their resources are people too.
I didn't say that subscriptions are limited to people. Actors can be organizations and applications too, and in Mastodon all actors are represented as "users" and "accounts". This is a very reasonable decision.A topic can be represented by application actor. This is already possible, you don't need to re-define Follow activity for that.
Nothing is a "new interpretation", it's an existing pattern that interactions sometimes go to attributedTo.inbox. For example when you Like something, if it doesn't have an object.inbox you check the object.attributedTo.inbox and send it there. What this FEP does is generalize the behavior of "crawl up attributedTo until you find an inbox". silverpill:
in Mastodon all actors are represented as “users” and “accounts”. This is a very reasonable decision.
It's unreasonable because actors don't have to be users. Actors can be anything. The spec explicitly notes this. A network of actors where actors are only users is not workable because various implementers are already doing things that don't represent users... they're just lying and calling them users, because they have to lie in order to be compatible with the incorrect interpretations and incorrect assumptions. silverpill:
A topic can be represented by application actor.
Some people are against multi-typing, so there's pushback there as well.
Multi-typing is not necessary, it can be an Application without a second type, or an object with a non-standard type but duck-typed as actor.
Anyway, there is a bigger problem. This FEP doesn't explain what "following" means if Follow.object is not an actor. ActivityPub spec says that Follow is used to subscribe to actor's activities, but what follower is supposed to receive from an object? Objects don't perform activities.
Regarding topic subscriptions, I already talked about my preferred solution in another thread. Now there is a formal proposal: codeberg.org/fediverse/fep/src…
This FEP doesn't explain what "following" means if Follow.object is not an actor. ActivityPub spec says that Follow is used to subscribe to actor's activities, but what follower is supposed to receive from an object?
The AS2 specification describes it.
the actor is interested in any activity performed by or on the object
In the case of following a non-actor, the "on the object" is the key phrase. When some actor performs an activity on the object, that activity may be delivered to the object's followers collection (subject to authorization, some activities may be considered private-ish).
The ActivityPub spec focuses on the "performed by the object" part, but doesn't prohibit the "on the object". trwnh:
Activities related to that object, as decided by the attributedTo actor?
Note that attributedTo is not required to be an actor. AS2 says this explicitly.
Ident
... mehr anzeigen
silverpill1:
This FEP doesn't explain what "following" means if Follow.object is not an actor. ActivityPub spec says that Follow is used to subscribe to actor's activities, but what follower is supposed to receive from an object?
The AS2 specification describes it.
the actor is interested in any activity performed by or on the object
In the case of following a non-actor, the "on the object" is the key phrase. When some actor performs an activity on the object, that activity may be delivered to the object's followers collection (subject to authorization, some activities may be considered private-ish).
The ActivityPub spec focuses on the "performed by the object" part, but doesn't prohibit the "on the object". trwnh:
Activities related to that object, as decided by the attributedTo actor?
Note that attributedTo is not required to be an actor. AS2 says this explicitly.
Identifies one or more entities to which this object is attributed. The attributed entities might not be Actors. For instance, an object might be attributed to the completion of another activity.
I'd think any activity performed on the non-actor object by an authorized actor would be delivered to the followers collection.
EDIT: I think they have recently modified it but FunkWhale supports (or did support) following a music Library object, which is not an actor, so there is an implementation precedent for this type of behavior. IIUC, they changed, or are changing it, to be more interoperable with the Mastoverse.
As you may be aware, Quote Posts are an often-requested feature for Mastodon, but this is something we are careful to implement properly, offering a proper framework for users to consent to being quoted.
Of course, no mechanism will be airtight, there will always be ways to quote someone else, by manually repeating their words, using screenshots and so on. Nevertheless, providing a framework for consent, and adding friction in the absence of consent, is worthwhile. Many existing social network services which feature Quote Posts also offer users at least some control over who can Quote them (on the most basic end, Twitter does not allow people to quote someone who blocked them, while Bluesky, Tumblr and formely the now defunct Cohost allow users to opt out of being quoted, and Bluesky allows to “detach“/revoke individual quotes). We strongly think that such mechanisms are useful, even if there are always ways around them.
Our goal with Quote Posts is allow people to quote users who have consented to it, notifying them in the process, and a
... mehr anzeigen
Hi!
As you may be aware, Quote Posts are an often-requested feature for Mastodon, but this is something we are careful to implement properly, offering a proper framework for users to consent to being quoted.
Of course, no mechanism will be airtight, there will always be ways to quote someone else, by manually repeating their words, using screenshots and so on. Nevertheless, providing a framework for consent, and adding friction in the absence of consent, is worthwhile. Many existing social network services which feature Quote Posts also offer users at least some control over who can Quote them (on the most basic end, Twitter does not allow people to quote someone who blocked them, while Bluesky, Tumblr and formely the now defunct Cohost allow users to opt out of being quoted, and Bluesky allows to “detach“/revoke individual quotes). We strongly think that such mechanisms are useful, even if there are always ways around them.
Our goal with Quote Posts is allow people to quote users who have consented to it, notifying them in the process, and allowing seamless display and navigation of such quotes. We also want to allow users to later revoke individual quotes if they need to, or change their quoting policy after the fact so that e.g. a post getting viral does not lead to an unmanageable amount of quotes and notifications.
To this end, we are proposing the following draft, which we will shortly adapt into one or more FEPs.
Thanks @trwnh for their reviews and suggestions, particularly around using result and instrument to split concerns and avoid requiring new server-side side-effects.
Keep in mind this is not final. In particular, we are considering re-using GoToSocial's interaction policies instead of our custom acceptsQuotesFrom property if they get fixed to address our concerns.
There is also an opportunity to change the representation of quotes themselves, though we used the combination of FEP-e232 and https://misskey-hub.net/ns#_misskey_quoterel attribute for compatibility with existing implementations.
FEP-xxxx: Quote posts and quote control
Summary
This is a work-in-progress document describing Mastodon's proposed way of representing quote posts, users' choices regarding whether their posts can be quoted and by whom (quote policies), and a mechanism for servers to verify compliance with such policies.
This document describes protocol considerations, which do not necessarily translate directly to User Experience considerations. For instance, the use of the approval mechanism described in this document does not imply that the user's approval is manual.
Requirements
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this specification are to be interpreted as described in [RFC-2119].
In the remaining of this document, “quoted object” refers to the object being quoted, “original author” to its author, and “quote post” refers to the object quoting the “quoted object”.
Representation of a quote post
A “quote post” is represented as an object with an Object Link (FEP-e232) to a “quoted object” using https://misskey-hub.net/ns#_misskey_quote as a link relation.
Users may not want their posts to be quoted, or not by everyone. Therefore, we offer a way to declare quote policies using a new acceptsQuotesFrom (http://joinmastodon.org/ns#acceptsQuotesFrom) attribute.
The author of the object, as well as mentioned users, can always quote the object, regardless of whether they appear in acceptsQuotesFrom.
To advertise a policy of disallowing all quotes, acceptQuotesFrom MUST contain the object author's identifier as its single value. This is because an empty array is equivalent to a missing property under JSON-LD canonicalization.
acceptsQuotesFrom SHOULD be restricted to individual actors, the special public collection https://www.w3.org/ns/activitystreams#Public, the author's followers collection, and the author's following collection.
Example
{ "@context": [ "https://www.w3.org/ns/activitystreams", { "toot": "http://joinmastodon.org/ns#", "acceptsQuotesFrom": { "@id": "toot:acceptsQuotesFrom", "@type": "@id" } } ], "acceptsQuotesFrom": "https://example.com/users/alice/followers", "type": "Note", "id": "https://example.com/users/alice/statuses/1", "attributedTo": "https://example.com/users/alice", "to": "https://www.w3.org/ns/activitystreams#Public", "content": "I allow my followers to quote this post"}
Approval stamps
In order to enforce a policy, we rely on approval stamps, a mechanism used to tell third-party servers that a quote is approved, regardless of the current state of the policy.
Quote approval stamps are objects of the type QuoteAuthorization (http://joinmastodon.org/ns#QuoteAuthorization).
The object attribute MUST reference the accepted quote post, the target attribute MUST reference the quoted object, and the attributedTo MUST correspond to the author of the quoted object.
A QuoteAuthorization object MUST be dereferenceable by all parties allowed to see the original post, and MAY be publicly dereferenceable. It MUST NOT embed its object as to avoid possible information leaks. For the same reason, it MUST NOT embed its target object if the server is unable to verify that the party dereferencing the object has permission to see the quoted object.
When a third-party attempts to dereference the QuoteAuthorization, the target MAY be inlined if the third-party has permission to access the quoted object. This is so that the third-party does not have to perform a second request to access the quoted object.
Example of QuoteAuthorization
The following stamp can be used to prove that actor https://example.com/users/alice has accepted https://example.org/users/bob/statuses/1 as a quote of her post https://example.com/users/alice/statuses/1: { "@context": [ "https://www.w3.org/ns/activitystreams", { "toot": "http://joinmastodon.org/ns#", "QuoteAuthorization": "toot:QuoteAuthorization" } ], "type": "QuoteAuthorization", "id": "https://example.com/users/alice/stamps/1", "attributedTo": "https://example.com/users/alice", "object": "https://example.org/users/bob/statuses/1", "target": "https://example.com/users/alice/statuses/1"}
Verifying a QuoteAuthorization
To be considered valid for a particular quote post, the QuoteAuthorization object referenced in quoteApproval MUST satisfy the following properties:
its object is the quote post under consideration
its target property is the quoted object
its attributedTo property is the author of its object
the authenticity of the object can be asserted
Revoking a QuoteAuthorization
An approval stamp can be revoked by Deleteing the stamp.
Quote request activity
The Quote (http://joinmastodon.org/ns#Quote) activity type is introduced to request approval for a quote post.
The Quote activity uses the object property to refer to the quoted object, and the instrument property to refer to the quote post.
When receiving a Quote activity, the original author decides (either manually or automatically) whether the quote is acceptable. Software that automatically accepts quotes on the author's behalf should notify the author of such quotes according to their notification settings.
The receiving end MAY inspect the instrument of the Quote itself to decide whether it is acceptable.
If the quote post is considered acceptable, the original author MUST reply with an Accept activity with the Quote activity as its object, and a QuoteAuthorization as its result.
If the quote post is considered unacceptable, the authority SHOULD reply with a Reject activity with the Quote activity as its object.
In order to get approval, the quote post author MUST send a Quote (http://joinmastodon.org/ns#Quote) activity to the author of the quote post, with the quoted object as its object property and the quote post as its instrument.
The quote post SHOULD be inlined in the instrument property and, if not, it SHOULD dereferenceable by the recipient at this point, as the author of the quoted object may want to inspect it to decide whether to accept the quote.
The quote post author MAY wait until they receive an Approve or Reject activity before sending the post's Create activity to its intended audience.Doing so is possible for ActivityPub servers that implement the current proposal, and avoids having to issue an Update soon afterwards the Create for the quote post.It is however not possible to implement for ActivityPub clients, which will likely need to issue a Create before the Quote activity.
Rejection
If the author of the quote post receives a Reject activity from the quoted object's author to their Quote activity, they MUST consider the quote post to be explicitly rejected.
If the implementation waits for the Accept before issuing a Create, this MAY translate as the inability to publish the quote post.
Otherwise, it MAY translate as a Delete to outright remove the quote post, or an Update to remove the quote part from the post.
Acceptance
If the author of the quote receives an Approve activity, they MUST add a reference to its result in the approvedBy property of the relevant object link.
Depending on whether they already sent a Create activity to the quote post's intended audience, they SHOULD send a Create activity or an Update activity with the updated approvedBy property.
When processing a quote post from a remote actor, a recipient MUST consider them unapproved unless any of those conditions apply:
the author of the quote post and that of the original post are the same (same attributedTo)
the author of the quote post is mentioned in the original post
approvedBy exists, can be dereferenced and is a valid QuoteAuthorization activity for this object
Revocation of a quote post
Revoking a previously-accepted quote post
The original author may want to perform /a posteriori/ moderation of the quote posts, or block a quote poster in particular.
To do this, the original actor MUST Delete the QuoteAuthorization. They SHOULD send the Delete activity to the quote post's author and any recipient it has reasons to think has accessed the quote post.
The original author MUST NOT embed the object nor the target of the QuoteAuthorization, so as to avoid potential information leakage.
Handling a revocation
Upon receiving a Delete activity for a previously-verified QuoteAuthorization, third-parties MUST check that the Delete is valid and MUST subsequently consider the quote post unapproved.
Additionally, if the recipient owns the quote post, it MUST forward the Delete to the audience of the quote post.
Opportunistic re-verification of quote approvals
Because getting revocation properly forwarded depends on the good will of the revoked post's author, it may be necessary to have other means of checking whether an approval has been revoked.
For this reason, recipients SHOULD re-check the approvedBy document when an already-known quote post is accessed for the first time in a given period of time.
Server behavior considerations
This proposal has been made with great care to not require new server behavior, allowing ActivityPub clients to implement this proposal without requiring generic ActivityPub server software to implement additional logic.
In particular, this is the reason the approval stamp is a separate object rather than the Accept itself. Indeed, nothing in the ActivityPub specification would cause a Reject or Undo activity to invalidate the Accept activity itself, which means it would not be suitable as an approval stamp.While ActivityPub does not technically forbid Accept activities to be the target of a Delete activity, we have found no precedent for that, and we anticipate that deleting activities might not be correctly handled across the fediverse.For this reason, we opted to use a separate object that can be directly managed by an ActivityPub client, for instance by issuing a Create activity ahead of sending the Accept activity, and that can be deleted with the usual mechanism.
An alternative approach we considered is using a dedicated endpoint to check for approval of a quote. This would effectively allow externalizing approval verification to a separate mechanism, but while this would not require new server behavior, this would still require a new server component to be specified, which is why we opted for the mechanism described in this specification instead.
Security considerations
Servers not implementing this FEP will still be able to quote the post and provide no dogpiling-reducing friction. There is unfortunately nothing we can do about that.
Effectively revoking quote posts relies on the participation of the quote poster's server to effectively reach the audience of the quote post, so an ill-intentioned server could quote post then refuse to forward the revocation. Still, this can arise on well-intentioned servers too, so the feature remains useful. Opportunistic re-verification of quote approvals should also help.
By not adding a hash or copy of the reply in the QuoteAuthorization object, malicious actors could exploit this in a split horizon setting, sending different versions of the same activity to different actors. This is, however, already a concern in pretty much all contexts in ActivityPub, and enshrining that information in the QuoteAuthorization object would have many drawbacks:
significantly more complex implementation
inability to change the JSON-LD representation after the fact
possibly leaking private information if the QuoteAuthorization object is publicly dereferenceable
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.
Clarify advisory nature of interactionPolicy.
Redefine default behavior when interactionPolicy is null, and add defaults per key.
Include section on type hinting.
Include section on always sending ...
Menschen, die das Ende der Normalität wünschen. „Also das reicht jetzt. Es sollte wirklich langsam Frühling werden.” Ich hörte diese Worte, als ich heute aus der Straßenbahn stieg, knapp […]…
The Medito app is a (unsurprisingly) meditation/mindfulness app. Sort of the free software alternative to Headspace. I haven't used it in a long time and was curious to see how it was doing, but I saw this: - it's only available on IzzyOnDroid now, I believe it used to be on F-droid at some point - the available release is 2 years old
So I thought, maybe the app was sadly just archived, but no, it's actually still under development, it's just that no releases have been published on GitHub for 2 years (2.0.48 clearly titled "Deprecated"), instead the Play Store releases keep being pushed out as recently as 3 February 2025 (3.2.0). Oh and the issues tab has been disabled, which seems very shady to me. So I wonder what the heck went down with this excellent app, it may still be considered "free software", also featuring the best licence (AGPL), but it looks like it has become unfriendly towards the community, I wonder why
Stammtisch für Polyamorie und alternative Beziehungsformen.
Der Grazer PolyTisch bietet eine wunderbare Gelegenheit, Menschen kennenzulernen, welche unterschiedlichste offenere Beziehungsformen leben oder sich dafür interessieren. Es nehmen durchschnittlich um die 50 Menschen teil und man wird gut vernetzt. Die Gespräche entstehen in dieser sehr offenen und herzlichen Atmosphäre ganz von selbst. Jede/r die/der Interesse an diesen Themen hat, ist herzlich willkommen.
Der Stammtisch ist unmoderiert, aber gut betreut. | Offener Stammtisch, keine Anmeldung notwendig!
Open Access and Open Data: Japanese visitors at TIB
On 31 January 2025 we welcomed two guests from Japan to the TIB. Chifumi Nishioka is an associate professor at Kyoto University and a member of the working group organized by the Japanese Ministry of Education, Culture, Sports, Science and Technology (MEXT) in order to discuss the future of scholarly communication. She was accompanied by Mami Hayashi of Chuo University Library. They were on the way to attend the Berlin Open Access Conference and stopped over in Hannover to learn about TIB’s activities concerning open access and research data management. The Japanese guests together with TIB colleagues at the TIB Science/Technology si
... mehr anzeigen
Open Access and Open Data: Japanese visitors at TIB
On 31 January 2025 we welcomed two guests from Japan to the TIB. Chifumi Nishioka is an associate professor at Kyoto University and a member of the working group organized by the Japanese Ministry of Education, Culture, Sports, Science and Technology (MEXT) in order to discuss the future of scholarly communication. She was accompanied by Mami Hayashi of Chuo University Library. They were on the way to attend the Berlin Open Access Conference and stopped over in Hannover to learn about TIB’s activities concerning open access and research data management. The Japanese guests together with TIB colleagues at the TIB Science/Technology site. From left to right: Franziska Altemeier, Nina Düvel, Janna Neumann, Chifumi Nishioka, Mami Hayashi, and Stefan Schmeja.
From Open Access strategies and services to consortia and contracts
Six colleagues from different departments of TIB met with the Japanese colleagues to give short overviews of their topics and to discuss them with our guests. Stefan Schmeja and Nicola Bieg presented open access strategies and services in general as well as the coverage of publication costs in agreements with publishers (for example within TIB’s Consortia). The guests had indicated specifically that they wanted to learn about the impact of the DEAL agreements on Leibniz University Hannover (LUH) and the double role of TIB as university library and national library for science and technology in supporting DEAL. While we noticed similar approaches to open access, there are also differences: Whereas Japanese science policy has put the focus on green open access so far, in Europe diamond open access is favoured in policies on the European, national and institutional levels, including the open access policies of TIB and LUH.
Research data management at TIB
Research data management was the second topic of interest. Johannes Hunold introduced the German National Research Data Infrastructure NFDI in general, the role of TIB in NFDI and NFDI4Chem in particular. Janna Neumann talked about the Research Data Management Services for LUH which include training and consultation and the institutional data repository. Finally, Franziska Altemeier and Nina Düvel presented the Joint Lab Future Libraries & Research Data, which is an institution at the intersection of TIB and Hanover University of Applied Sciences and Arts (Hochschule Hannover, HsH) supporting the implementation of research data management at HsH and Universities of Applied Sciences in general.
The visit ended with a tour of the library. We were very happy to meet our Japanese guests in Hannover and to discuss the promotion of open access and research data management and TIB’s services with them.
So there is this little weird YouTube channel „Yellow Belly Tabletop“ who in their weekly live streams ask really important and weird questions or discuss odd topics like:
Wargaming’s hidden secret: Communal hobby
Now, is communal hobby a „hidden secret“?
No, I don’t think it’s hidden and it’s no secret but it is an aspect of our wargaming hobby that might not be very apparent to new […]
… and follow the tag.
The Japanese guests together with TIB colleagues at the TIB Science/Technology si
Doompickaxe
Als Antwort auf cron • • •Die Hoffnung stirbt zuletzt.
(Aber sie stirbt)
cron
Als Antwort auf Doompickaxe • • •