Gilgo Beach murders: Blueprint of crimes leads prosecutors to lay 2 more charges News beach murders island serial killer Heuermann killer
Fr mich liest sich das, als wenn es die Mastodon API an WordPress dranschraubt.
Das hat also nichts mit Fderation zu tun, sondern damit, da du eine Mastodon-Smartphone-App ans Blog anhngen und dann mit der Mastodon-App bloggen kannst. Das ist natrlich nur dann sinnvoll, wenn die App nicht hart nur gegen Mastodon gebaut ist und nicht nur Mastodons Features untersttzt, sondern z. B. auch unbegrenzt viele Zeichen und Markdown mit allen Schikanen bis hin zu eingebetteten Inline-Bildern.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
WordPress #
Mastodon #
MastodonAPI #
MastodonApps Are you familiar with
Mike Macgirvin 's creations Friendica Hubzilla The streams repository even
He has been working on some of these points since longer than Mastodon has been around, even since befor the term "Fediverse" was coined.
Safe spaces: I dare say that (streams) can be the safest space in the whole Fediverse. That's because it has the most advanced, most extensive permission settings in the Fediverse. And it's one of the very few Fediverse server applications that actually know permissions.
Portable identity: Has been reality since Mike invented the Zot protocol and nomadic identity in 2011 and first implemented it by forking Friendica into Red and porting it to Zot in 2012. Except for the first Osada, everything Mike made afterwards supported or still supports nomadic identity amongst its own server instances, including Hubzilla and (streams).
Right now, Mike is working on porting both nomadic identity and (streams)' permission model to 100% ActivityPub so that other already existing projects can adopt them. His goal is to go even further and stretch the same identity across server instances of
different projects.
Channels/feeds: Stuff like this should be possible with Hubzilla and (streams) right now already. In their case, "channel" refers to a Fediverse identity, of which one can have multiple separate ones on the same account. But a Hubzilla or (streams) channel can do much, much more than Mastodon-style microblogging, even more than what a Friendica account can do. It can serve as a discussion group/forum, complete with moderation, even with
multiple moderators. It can also serve as a news aggregator, and a Hubzilla channel can even act as a fully automatic reposter for one or multiple sources of various kinds, including RSS or Atom feeds.
In general, if you think something should be developed in the Fediverse, ask whether Hubzilla or (streams) already has it implemented.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams)Nicht , aber hier neu
"Three years after their initial bouts with , patients whod once been hospitalized with the virus remained at 'significantly elevated' risk of death or worsening health from COVID complications, according to a paper published May 30 in Nature Medicine."
To add to your table:
supports nodeinfo 2.0 and 2.1.
Examples from a stable release, just to show that they can differ, depending on how a hub is configured:
Example from a development release:
However, it looks like nodeinfo can be turned off entirely by the hubmin. At least hubzilla.org has a blank nodeinfo page.
always has a blank nodeinfo page. Most nodeinfo code has intentionally been removed. It understands nodeinfo, but it seems to send something else instead which it only understands itself, which is limited in what information it offers, and which isn't parsed by Fediverse stats/instance-listing websites.
By the way: Both Hubzilla and (streams) support both OAuth and OAuth2 both as a client and as a server. However, Hubzilla's documentation is painfully outdated in this regard parts of it still refer to Red, so they were last touched before the name change to Red Matrix. And (streams) doesn't have any documentation.
Also, Hubzilla and (streams) are the only Fediverse server applications with full, i.e. both server-side and client-side support for OpenWebAuth single sign-on.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
OAuth #
OAuth2 #
Nodeinfo When it comes to describing images, Mozilla is still thinking in dimensions for either static websites or commercial/scientific blogs or corporate American social media, namely no more than 150-200 characters.
They've had their own Mastodon instance for a while now, but it seems nobody at Mozilla actually follows any other Mastodon user. Otherwise they'd know a thing or two about Mastodon's high standards for image descriptions.
Do my image posts ever make it over to Misskey, or does it actually reject posts over 10,000 characters or so Because there are Mastodon users who don't even find
these overwhelming, and I probably write the longest image descriptions in the whole Fediverse.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta One solution that hasn't been mentioned yet: Get yourself a Bluetooth hardware keyboard that's large enough for touch-typing but compact enough to take it with you if you have a bag or something.
I myself wouldn't trust any AI to properly describe my own images, not after actually pitting one against my own hand-written image descriptions twice and seeing it fail miserably. But then again, describing my images in a way that I deem sufficiently is practically impossible for AI unless it's absolutely omniscient.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
AII've got over 500 connections, most of which are on Mastodon. Yet, it feels like I've got much less reach in the Fediverse now than I used to have when I only had some 200 or 300 connections. This can only mean that especially lots of Mastodon users and maybe even entire Mastodon instances have muted, blocked or shadow-banned me. I wouldn't even be surprised if some public Mastodon instances have secretly muted or blocked hub.netzgemeinde.eu as a whole just because of my actions.
I can't really tell from the delivery reports, for one difference between Mastodon and Hubzilla is that Hubzilla rejects blocked or filtered messages at the server level whereas Mastodon accepts them and then discards them before they can be delivered to the muting, blocking or filtering recipient. Otherwise I think I could weed out a whole lot of connections.
And here's a list of reasons for which I've probably been muted, blocked or shadow-banned:
- Posting over 500 characters. Regardless of whether or not I put them behind a Mastodon-style content warning.
- Posting over 500 characters without a Mastodon-style content warning. That's because I simply can't put Mastodon-style content warnings on comments. Still, I'm pretty sure that just about everyone who has ever come across an over-500-character comment from me while using the official Mastodon app has taken countermeasures.
- A summary in the content warning. Mastodon's content warning field is the summary field, but 99% of all Mastodon users don't know.
- More than four hashtags. On Mastodon, more than four hashtags are spam, regardless of whether they're spread across a 150-character toot or a 10,000-character essay or at the very end of the post. Also, Mastodon largely doesn't know the concept of filtering hashtags, it knows filter-generated content warnings even less, and it knows the concept of adding hashtags in order to trigger filters another great deal less.
- A few may still be upset about text formatting, even though I guess many mobile apps still don't show it.
- Talking about virtual worlds, but the Mastodon users in question don't know how to filter.
- Talking about the Fediverse, but actually talking about the Fediverse outside of Mastodon and/or making Mastodon look bad in comparison to non-Mastodon Fediverse projects.
- Questioning Mastodon practices that are set in stone and never discussed on Mastodon such as certain aspects of describing images.
Essentially, this boils down to two points:
- not adopting the entirety of Mastodon's culture as a Hubzilla user
- not abandoning Hubzilla's culture as a Hubzilla user
All because the Fediquette is entirely defined by Mastodon users, most of whom at that point didn't and often still don't know that the Fediverse is more than just Mastodon.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
MastodonCulture #
Fediquette #
Mute #
Muted #
Block #
Blocked #
NotMastodon all decentralized social networks
Certainly not
all of them. How about:
- Hubzilla (part of the Fediverse because it can optionally use ActivityPub, but no Mastodon API support that's where I'm posting from)
- (streams) (part of the Fediverse because it can optionally use ActivityPub and does so by default, but no Mastodon API support)
- Diaspora* (part of the Fediverse by proxy, namely by being federated with Friendica, Hubzilla and GoToSocial which, in turn, can use or are based on ActivityPub)
Also, if "Mastodon" means that the ActivityPub side is only built and tested against Mastodon and only supports Mastodon's features, chances are it might not work with dozens of other Fediverse projects, including but not limited to Pleroma and Akkoma as well as Misskey and its many forks.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Openvibe #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkey #
Forkeys #
Hubzilla #
Streams #
(streams) #
Diaspora* #
NotOnlyMastodon #
FediverseIsNotMastodon #
MastodonIsNotTheFediverseCC:
Franck Muller Long Island Crazy Color Dreams WhiteRG
Frank Muller Exclusively Crazy Hour Edition Design For Mens Now Available & Ready to ship same day # Frank Muller # For Men # Master Quality Island Crazy Color Dreams Non Comparable Original Japanese Power Resurve Automatic Jumping Machinery following Working Jumping Hour Stainless Steel rg Case -Black Genuine Leather Strap White Dial With Luminus Hands Top High End Back Original
It has become next to impossible to discuss content warnings in the Fediverse using hashtags.
#
CW has been hijacked by amateur radio where it stands for continuous wave. The few exceptions are about TV and refer to the CW Network.
#
CWS has recently been hijacked by a commercial advertising account.
#
ContentWarning has recently been hijacked for posts about the eponymous video game.
And both #
ContentWarnings and #
ContentWarningMeta are too long to type on a screen keyboard.
Not to mention that Mastodon is largely falling back into Twitter mannerisms, i.e. neglecting hashtags altogether, and most of the rest of the Fediverse has never had a hashtag culture to begin with.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hashtag #
Hashtags #
HashtagMeta #
CWHashtagMeta Wie detailliert sollten sie sein
Da gibt's keinen Konsens. Das kann ich aus Erfahrung sagen, auch wenn ich fast kein Feedback bekomme.
Ich schreibe die mit Abstand lngsten Bildbeschreibungen im ganzen Fediverse und halte das auch gerechtfertigt. Einige feiern sie tatschlich, auch wenn es bis zu einer Stunde dauert, eine davon zu lesen. Inzwischen wundert mich das regelrecht.
Andere, kurioserweise durchweg ohne nennenswerte Behinderung, sind strikt dagegen und sagen auch mal, absolut jedes Bild lt sich adquat in 200 Zeichen oder weniger beschreiben. Und wer etwas nicht versteht, soll eben fragen oder googlen.
Eigentlich ist auf den Bildern meist noch mehr zu sehen, als ich schreibe. Und ich schreibe tendenziell viel.
Ich versuche tatschlich, alles zu beschreiben, was sich innerhalb des Bildes befindet und nicht komplett verdeckt ist. Allerdings zeigen meine Bilder ein so obskures Nischenthema, da meines Erachtens so detaillierte Beschreibungen gerechtfertigt sind. Nur dauert das eben seine Zeit.
Wenn die BildBeschreibungen nicht wren, wrde ich mehr Fotos zeigen (insbesondere auf pixelfed).
Kenne ich auch. Ich htte eigentlich viel zu zeigen. Aber die Bildbeschreibungen, wie ich sie schreibe, fressen derart Zeit und Energie, da zwischen meinen letzten zwei Bildposts mehr als drei Monate lagen.
Das letzte Mal habe ich mir schon berlegt, was ich zeigen knnte, was interessant ist, aber nicht so aufwendig zu beschreiben. Ich lag mal wieder komplett falsch und schrieb letztlich ber zwei Tage verteilt meine mit Abstand lngste Bildbeschreibung.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
BiBesch #
Bildbeschreibung #
Bildbeschreibungen #
BildbeschreibungenMeta Heat Check: Discussing Heats free agents and Jimmy Butler
does a consistent tree require a central resource to define the tree
The central resource is the actor that started the tree.
Traditionally, all replies go to this actor and this actor alone, and this actor distributes them to all other participants.
The whole tree with all its nodes is ideally owned by the actor who started it.
Does it require everyone have access to all nodes in the tree
Obviously, the actor who started the tree must not be muted or blocked, otherwise the entire tree is inaccessible.
As for comments, I'm not sure what happens when a blocked actor replies, and someone else replies to this reply. Most likely, the reply from the blocked actor will not appear because it still came from the blocked actor the actor who started the tree only forwarded it automatically. But I can't say how replies to a blocked reply are handled.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Threadiverseeven for forums, does the Fediverse really need a consistent tree
Yes, because nodeBB, Flarum, Lemmy, /kbin, Mbin, PieFed, Sublinks, Friendica, Hubzilla, (streams) and everything else that knows what a context is
will interact with each other. They often already do.
It doesn't make sense for each one of them to try and patch incompatibilites with the others one by one, all by themselves, without even talking to each other. That might only cause more incompatibilites, not to mention loads of extra code just to address the quirks of individual projects.
It's better to have one agreed-upon standard.
I understand wanting a consistent tree, so everyone has access to all the posts, but I think the Fediverse focus on safety should override an attempt at consistency
Safety can and certainly will come with consistency.
Look at
Mike Macgirvin 's , the result of 14 years of work that started in 2010 with Mistpark, now known as Friendica. (streams) knows what a context is. (streams) can hold a discussion together. (streams) supports groups/forums. And so did all its predecessors, two of which (Friendica, Hubzilla) are still alive and maintained.
At the same time,
(streams) has to be the safest place in the whole Fediverse. Not necessarily by culture or policy, but by
technology. (streams) has ramped up its permission controls beyond what Hubzilla has to offer, and Hubzilla's permission controls are already extensive. In the meantime, Mastodon and everything else in the Fediverse that's based on ActivityPub doesn't even know what permissions are.
On Mastodon, all you have is mute and block for users or instances. Hubzilla goes much, much further, (streams) goes
even further. Imagine being able to delete posts from a thread that you've started (Hubzilla, (streams)) or even banning users from participating in your thread ((streams)). Imagine being able to define who exactly is allowed to send you posts, who exactly is allowed to see your profile (or which one of your multiple profiles even), who exactly is allowed to comment on your posts, who exactly is allowed to send you DMs etc. etc.
Now comes the consistency part:
Mike is right now working on porting some of (streams)' key technologies to ActivityPub, namely conversation containers, nomadic identity (currently exclusive to Hubzilla and (streams)) and permissions on (streams)' level.
All this is planned to become possible using only ActivityPub with a number of already existing FEPs. This means that any project that mainly or only uses ActivityPub can adopt all these features in the same way as (streams). Even Mastodon could, and the only way that'd stand in the way of adoption would be Gargron's unwillingness to adopt anything developed by someone else.
But if Mastodon did adopt all this, you would be able to moderate your own threads. You would have more power over your own connections and threads
then than Mastodon moderators and admins have
now.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Threadiverse #
Hubzilla #
Streams #
(streams) #
Permissions Find the latitdue and longitude of any place TIL that (streams) has a defined character limit of 24 million characters, but until now, the database limits the size of the object to a bit over 65,000 characters. The latter limit is being raised for new installations, and existing servers can raise that limit, too.
That's over 130 vs 48,000 Mastodon toots or more than 20 vs 8,000 Misskey notes.
Mind you, (streams) counts characters differently from Mastodon. Links aren't always 23 characters, they're as long as the URL plus the link code. The embedding code for in-line images, image URLs and alt-text included, is part of the post text. In general, all BBcode/HTML/Markdown counts into the character count. I'm not sure whether titles and summaries add to the overall character number, but at 24 million characters, that shouldn't make a difference.
Unfortunately, I no longer have the delivery report of the one time I exceeded the 65,000 character limit so I don't know how (streams) handles longer posts from outside.
The long post triggered something we haven't seen before... we allow the post body to be up to 24M, but the obj is capped at 65K. This was acceptable a year ago, but with conversation containers we put the entire post body into the object when sending a collection activity. So you're getting capped at 65K. You can change the item.obj column in the database and make it 'mediumtext'. I'll put this in the install database schema for new installs.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
QuotePost #
QuoteTweet #
QuoteToot #
QuoteBoost #
CharacterLimit #
CharacterLimits This, however, is exactly how
Mike Macgirvin 's creations have been working since Mistpark was launched 14 years ago.
This is how all of Mistpark's offspring works. This is how Friendica works, this is how Hubzilla works, this is how what's in the streams repository works. The thread starter owns the thread. All comments go to the thread starter, and the thread starter distributes them to all participants in the thread, mentioned or not.
Especially in (streams)' case, this goes all the way to moderation. Since the thread starter owns the whole thread including all comments, the thread starter even has moderational power over the thread. The thread starter can both delete comments regardless of who posted them. and ban actors from participating in a thread. On Hubzilla and probably also on Friendica, the thread starter can still delete any comments.
For someone who only knows Twitter and Mastodon, this sounds awfully complicated. In reality, it's an absolute no-brainer because this is exactly how Facebook works.
Also, unlike Mastodon, Mike's creations give you a counter and list of unread activities in your stream in addition to the counter and list of notifications. You know when someone has replied to you even if that someone hasn't mentioned you. You even know when someone has participated in a thread that you've seen before even if you have neither been mentioned nor replied to.
All this makes discussions with more than two participants a great deal more convenient than the Mastodon way. In fact, both Friendica, Hubzilla and (streams) have always had groups/forums as a feature which are nothing but accounts (Friendica)/channels (Hubzilla, (streams)) with particular settings.
Again, this is neither new nor experimental. It predates Mastodon by almost six years, and it has been in daily stable use for longer than Mastodon.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta GPT-4 supera gli analisti finanziari nella previsione degli utili aziendali
ChicagoBooth
Three reasons.
One, there's one Mastodon bot that scrapes cat pictures from various sources, slaps AI-generated alt-text on them with no human interaction, churns them out hourly and adds the #
AltText hashtag because they've got alt-text.
Two, #
AltText should be used for
discussing alt-text rather than
image posts with alt-text which is why hardly any human user puts that hashtag on image posts.
Three, hardly anyone seems to discuss alt-text anymore. That, or more and more Mastodon users have fallen back into Twitter mode and stopped using hashtags altogether. And outside of Mastodon, almost nobody knows about or cares for alt-text anyway.
Thus, the bot-generated cat pictures dominate that hashtag.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hashtag #
Hashtags #
HashtagMeta #
CWHashtagMeta #
AltTextMeta #
CWAltTextMetaAmbience at Hanoi's 1000-year Anniversary
It's technologically impossible to add alt-text to
someone else's media in
someone else's posts. This is extremely unlikely to change, and when that someone else is on certain non-Mastodon instances, this will definitely never change.
The only thing you can do is reply with an alt-text, add one or multiple of these hashtags: #
Alt4U, #
Alt4You, #
AltText4U, #
AltText4You, and hope the user gets the cue and adds the missing alt-text.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta Does it absolutely have to be as close to Mastodon as possible
If not, allow me to introduce you to . Created and developed down under by
Mike Macgirvin and the result of 14 years of evolution, longer than Mastodon has been around.
Main advantage:
no media caching whatsoever. (streams) simply doesn't do that, neither do its predecessors, Friendica and Hubzilla.
Other advantages include nomadic identity, security and permissions on a level unimaginable for your average Mastodon user, many extra features and a smaller server footprint than Mastodon.
Okay, fair warnings, disadvantage #1: It has to re-download media over and over again.
Disadvantage #2: It comes with its own built-in WebDAV cloud storage, and people might be tempted to use it as such.
Disadvantage #3: It handles nothing like Mastodon. I'd say switching from Twitter to Mastodon is easier than switching from Mastodon to (streams), also due to (streams) not trying to mimic Twitter.
Disadvantage #4: no Mastodon API support which means absolutely no mobile apps available whatsoever. You can use it as a PWA instead.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Streams #
(streams)MIDSUMMER SCREAM, the Worlds Largest Halloween and Horror Convention, Launches 2024 App and Schedule
Halloween may be five months away, but the Halloween season begins July 26 to July 28 with MIDSUMMER SCREAM. The worlds largest Halloween and horror convention, has unveiled its official app, which allows attendees to plan and schedule their spook-filled days at this years event and with all there is to do, a schedule is a must....
scream beach july 2024
Lets Get Our First REAL Mage Weapon Terraria #
hair
Wanderer Fr viele, die nur Mastodon kennen, sind Mastodon, Akkoma, Misskey, Friendica, Hubzilla usw. nichts weiter als verschiedene Webinterfaces fr dasselbe System darunter und haben denselben Stellenwert wie Mona, IceCubes, Tusky, Fedilab & Co. fr Smartphones.
Da Friendica unter der grafischen Oberflche vllig anders
funktioniert als Mastodon und Hubzilla sogar
radikal anders, ist vllig unvorstellbar, wenn man bisher nur Mastodon benutzt hat.
Auerdem sind es typischerweise Friendica- und Hubzilla-Nutzer, die immer wieder auf Mastodon erwhnen, da das Fediverse nicht nur Mastodon ist. Und dabei treffen sie dann auf Mastodon-Nutzer, die nichts davon hren wollen.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
NichtNurMastodonWho needs when you have a ...
As for myself: Before users who can't see images find my image descriptions lacking because they've got no idea what whatever my image shows looks like, I add all of this.
Then again, I'm not limited to 1,500 characters in alt-text. I always give a short visual description in alt-text which also mentions that there's a full, detailed description in the post itself. And for posts I don't have any character limit except for the 100,000 characters above which Mastodon rejects external posts.
And this raises a new question: Is it worse if an image description is useless because it lacks information that a reader would love to know or that a reader
needs to know to understand the image Or is it worse if an image description is useless because hardly anyone is willing to spend one hour reading the description of one image
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta Don't skip colours.
You can't write individual descriptions for individual people anyway. You have to satisfy
everyone with
one and the same description.
And not everyone who relies on image descriptions was born blind. In fact, there are
sighted people who need image descriptions (images turned off due to low mobile quota, bad mobile network that won't load images, text-only terminal client that can't even display images as ASCII art). Including colours helps them more than it irritates fully blind people.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMetaZu den Filtern mte eigentlich noch sehr viel mehr geschrieben werden. Erstmal ber die Syntax an sich, die praktisch undokumentiert ist bis auf ein bichen im Code.
Auerdem kann man zumindest in einer Whitelist lose Schlsselwrter nicht mit Filtersyntax mischen. Das ist nirgendwo dokumentiert, sondern vielmehr quasi per leidvoller Eigenerfahrung reverse-engineert. In der Blacklist habe ich das noch nicht getestet.
Das Hauptproblem ist wahrscheinlich: Schlsselwrter sind immer mit
ODER
verknpft. Filtersyntaxzeilen sind aber, wie es scheint, zumindest in der Whitelist mit
UND
verknpft.
Eine bunte Kombination aus Schlsselwrtern und Filtersyntax fhrt dazu, da immer das ausgewertet wird, was am Ende steht. Steht am Ende ein Schlsselwort, werden die Schlsselwrter mit
ODER
verknpft ausgewertet und die Syntaxzeilen gar nicht. Steht am Ende Filtersyntax, werden die Schlsselwrter nicht ausgewertet, dafr aber die Filtersyntax mit
UND
.
Ein Beispiel, das berhaupt nicht funktioniert: Du willst nur Posts durchlassen, die eins von mehreren Schlsselwrtern enthalten. Aber du willst nur Posts filtern, keine Kommentare und keine DMs.
Du kannst DMs ausschlieen mit
itemprivate == 0
, und du kannst die Filterung beschrnken auf den Anfang eines Thread mit
itemthreadtop == 1
. Das kannst du aber nicht mit Schlsselwrtern kombinieren.
Dazu kommt dann auch noch: Wenn du mehrere
body =
-Zeilen hast, sind die auch mit
UND
verknpft, die Posts kommen also nur durch, wenn sie
alle Schlsselwrter enthalten.
Eine
body =
-Zeile mit RegEx geht auch nicht, weil Filtersyntax nicht mit RegEx kombinierbar ist.
Mit einem Schlsselwort geht es. Mit mehreren geht es nicht.
Ich glaube, ich werde mal wieder ein Feature Request einreichen, obwohl Mario kaum dazu kommt, auch nur die Bugs auszubgeln.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Filter #
Filters #
Hubzilla Yes, Diaspora* is two months younger than Mistpark.
But Diaspora* of 2024 is no match for Mistpark of 2010, feature-wise. Mistpark, on the other hand, evolved into Friendica which federated with everything that moved, then into Hubzilla, the nomadic Swiss army knife of the Fediverse, and lastly, into the streams repository which is the home of the technologically most advanced Fediverse software to date.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mistpark #
Friendika #
Friendica #
Hubzilla #
Streams #
(streams)Meine Basis-Contact Roles sind erstmal aufgeteilt in nomadisch und nichtnomadisch und in "darf mir Posts schicken" und "darf mir keine Posts schicken". Das ist nmlich in meiner Channel Role deaktiviert, damit das nicht jeder darf. Ein hlicher Hack eigentlich, aber solange Hubzillas Filter nicht so tun, wie ich will...
Ich habe auch noch zwei mit erweiterten Privilegien. Die hchsten hat die Familien-Role, in der nur meine In-world-Schwester
Juno Rowland ist.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
ContactRole #
ContactRoles #
Hubzilla Ich wrde Blogposts immer verlinken, selbst wenn das Blog selbst im Fediverse ist. Das heit, die meisten Projekte, die Blogposts im Fediverse versenden, machen das automatisch so, da Mastodon nur den Titel (so vorhanden), eine Zusammenfassung (so vorhanden) bzw. die ersten Zeilen und einen Link zum Original anzeigt.
Zum einen kann gerade Mastodon keine Blogposts mit allen Schikanen so darstellen wie im Original. Z. B. entfernt es Inline-Bilder ersatzlos.
Zum anderen gibt's auf Mastodon Leute, die, ohne ein Wort zu sagen, jeden blockieren, von dem ber 500 Zeichen in einem einzigen Post kommen. Manche machen das nur, wenn berlange Posts keine entsprechende Content Warning haben, aber wie willst du die sauber in einen Blogpost einflechten
berall sonst ist es den Leuten egal, wieviele Zeichen du postest. Und einige Serveranwendungen beherrschen in ihren Webinterfaces volles HTML-Rendering, stellen also auch selbst den aufwendigsten Blogpost noch so dar wie im Original.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
Fediquette The eternal question is: Is the Fediverse defined as everything that's decentralised in some way Then e-mail, XMPP, Matrix, OpenSimulator, Vircadia and Overte are parts of the Fediverse, too, and the Fediverse is several decades old. Oh, by the way, Friendica and Hubzilla can directly federate with e-mail.
Is it defined as everything that's connected to anything that uses ActivityPub in some way Then Twitter and Tumblr are/used to be parts of the Fediverse, connected directly to Friendica and Hubzilla.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FediverseDie Standard-Einstellung von Hubzilla ist, dass Beitrge Dritter, mit welchen man nicht verbunden ist, in denen man selbst erwhnt wird, nicht in der Timeline angezeigt, also nicht akzeptiert werden. Damit beschrnkt man den Empfang von Postings durch Erwhnung auf diejenigen Kanle/Nutzer, mit welchen man verbunden ist.
ber die Einstellungen lsst sich der eigene Kanal aber auch so konfigurieren, dass man Postings auch von "Fremden" empfngt, also von Nutzern, die nicht in der Kontaktliste sind. Dies berschreibt die Standard-Berechtigungen fr den Nachrichtenempfang.
Diese Einstellung lsst sich ber "
Einstellungen" (Hauptmen oben links) -> "
Privacy-Einstellungen" -> "
Accept all messages which mention you This setting bypasses normal permissions" vornehmen.
#
FediTips #
FediverseTips #
hubzilla #
hubzillahppchen #
Long #
LongPost #
CWLong #
CWLongPost the snow monkeys of nagano japan (in japan!) it took us 13 years but we finally made it to check out them famous snow apes. itspretty amazing, yo
In such a way that everyone gets what's in the picture Without ever Googling or asking me anything
Then go ahead and give me a good, informative image description of no more than 200 characters that's up there with the best of the best on Mastodon and potential material. One that won't leave any blind user asking, "Yeah, that's fine and dandy, but
what does it look like!"
Without reading my long description or my alt-text first, that is.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
AltTextHallOfFame Interesting how this article doesn't mention the one implementation of federated identity that is in daily stable use right now: , as invented by
Mike Macgirvin in 2011, five years before Mastodon. It is now implemented on from 2015 as well as from 2021.
Currently, nomadic identity requires special protocols, and it's limited to within Hubzilla or within (streams). But Mike is working on implementing it across project borders and using only ActivityPub right now.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
NomadicIdentity