#fediversememe — Public Fediverse posts

Ever wondered why the "Facebook alternative" side of the Fediverse is easy to deploy and so lightweight in spite of its feature wealth?

[spoiler=Caution: Image hidden due to eye contact, crying, anger and Japanese profanity]

Explanation:

This image is a collage based on various memes.

The top row makes use of Wojaks, it basically is a Wojak comic. The two Wojaks on the right are Soyjaks, the third one from the left is essentially the same combination of a Soyjak and a Crying Wojak as seen in the Soyjaks vs Chads format. "Baka", as said by the Soyjak in the top right, is Japanese for "idiot" and hints at Misskey, as well as large parts of its target audience, being Japanese. It has become a meme of its own.

The bottom row re-uses the "Moth Lamp" meme. This time, however, "lämp", intentionally spelled with an umlaut as per the meme, does not mean a light source. Instead, it stands for a so-called "LAMP stack" which is the bare minimum Web server equipment.

• L stands for Linux and refers not to the operating system kernel, but to the whole software platform.
• A stands for the Apache HTTP Server.
• M stands for the MySQL database management system, nowadays usually in the shape of the MySQL fork MariaDB.
• P, in this case, stands for the PHP scripting language used for dynamic websites.

The three Fediverse server applications represented as moths in the bottom row, captioned with "LÄMP", are Friendica, a very powerful Facebook alternative created by Mike Macgirvin in 2010, Hubzilla, a very versatile and extremely powerful "federated content management system" which Mike Macgirvin himself created from 2015 out of his own Friendica fork, and the intentionally nameless application in the streams repository from 2021, itself at the end of a long line of forks by Mike Macgirvin again, starting at Hubzilla. None of the four have any exotic or heavy-weight server software requirements. They need JavaScript for parts of the UI, but otherwise, they can run on a bone-stock Web server, requiring remarkably few CPU and RAM resources.

The four projects in the top row, on the other hand, have more exotic and/or heavy-weight requirements.

The one in the top left is diaspora* from later in 2010 than Friendica, the only one in the image that does not support ActivityPub at all (it is only connected to the few Fediverse projects which support its own protocol, including Friendica and Hubzilla). diaspora* and Mastodon next to it are both written in Ruby on Rails. Thus, they require more hardware resources per user identity than the three at the bottom while not even nearly offering the latter's features.

Next to them, Pleroma from 2016 is famous for being much more lightweight than Mastodon while still offering more. But it is written in the fairly exotic Elixir language. Also, it can't use MySQL; it is only compatible with more complex PostgreSQL. In the meantime, Misskey, which dates back to 2014, is entirely based on JavaScript: It is written in Microsoft's TypeScript with Vue.js for the frontend. Let's say there's a reason why the former Firefish fork and now Misskey fork Iceshrimp is currently being re-written from scratch in C# as Iceshrimp.NET.

#Fediverse #diaspora* #Mastodon #Ruby on Rails #Pleroma #Elixir #PostgreSQL #Misskey #JavaScript #TypeScript #Vue.js #Friendica #Hubzilla #(streams) #MySQL #PHP #LAMP stack #Meme #FediMeme #Fediverse Meme #Wojak #Wojak comics #Soyjak #Crying Wojak #Moth #Lämp #Moth lamp #EyeContact #CWEyeContact #Profanity #CWProfanity #Swearing #CWSwearing #Swear word #Crying #CWCrying #Tears #Anger #CWAnger #Sensitive #⚠️

Ever wondered why the "Facebook alternative" side of the Fediverse is easy to deploy and so lightweight in spite of its feature wealth?

[spoiler=Caution: Image hidden due to eye contact, crying, anger and Japanese profanity]

Explanation:

This image is a collage based on various memes.

The top row makes use of Wojaks, it basically is a Wojak comic. The two Wojaks on the right are Soyjaks, the third one from the left is essentially the same combination of a Soyjak and a Crying Wojak as seen in the Soyjaks vs Chads format. "Baka", as said by the Soyjak in the top right, is Japanese for "idiot" and hints at Misskey, as well as large parts of its target audience, being Japanese. It has become a meme of its own.

The bottom row re-uses the "Moth Lamp" meme. This time, however, "lämp", intentionally spelled with an umlaut as per the meme, does not mean a light source. Instead, it stands for a so-called "LAMP stack" which is the bare minimum Web server equipment.

• L stands for Linux and refers not to the operating system kernel, but to the whole software platform.
• A stands for the Apache HTTP Server.
• M stands for the MySQL database management system, nowadays usually in the shape of the MySQL fork MariaDB.
• P, in this case, stands for the PHP scripting language used for dynamic websites.

The three Fediverse server applications represented as moths in the bottom row, captioned with "LÄMP", are Friendica, a very powerful Facebook alternative created by Mike Macgirvin in 2010, Hubzilla, a very versatile and extremely powerful "federated content management system" which Mike Macgirvin himself created from 2015 out of his own Friendica fork, and the intentionally nameless application in the streams repository from 2021, itself at the end of a long line of forks by Mike Macgirvin again, starting at Hubzilla. None of the four have any exotic or heavy-weight server software requirements. They need JavaScript for parts of the UI, but otherwise, they can run on a bone-stock Web server, requiring remarkably few CPU and RAM resources.

The four projects in the top row, on the other hand, have more exotic and/or heavy-weight requirements.

The one in the top left is diaspora* from later in 2010 than Friendica, the only one in the image that does not support ActivityPub at all (it is only connected to the few Fediverse projects which support its own protocol, including Friendica and Hubzilla). diaspora* and Mastodon next to it are both written in Ruby on Rails. Thus, they require more hardware resources per user identity than the three at the bottom while not even nearly offering the latter's features.

Next to them, Pleroma from 2016 is famous for being much more lightweight than Mastodon while still offering more. But it is written in the fairly exotic Elixir language. Also, it can't use MySQL; it is only compatible with more complex PostgreSQL. In the meantime, Misskey, which dates back to 2014, is entirely based on JavaScript: It is written in Microsoft's TypeScript with Vue.js for the frontend. Let's say there's a reason why the former Firefish fork and now Misskey fork Iceshrimp is currently being re-written from scratch in C# as Iceshrimp.NET.

#Fediverse #diaspora* #Mastodon #Ruby on Rails #Pleroma #Elixir #PostgreSQL #Misskey #JavaScript #TypeScript #Vue.js #Friendica #Hubzilla #(streams) #MySQL #PHP #LAMP stack #Meme #FediMeme #Fediverse Meme #Wojak #Wojak comics #Soyjak #Crying Wojak #Moth #Lämp #Moth lamp #EyeContact #CWEyeContact #Profanity #CWProfanity #Swearing #CWSwearing #Swear word #Crying #CWCrying #Tears #Anger #CWAnger #Sensitive #⚠️

Ever wondered why the "Facebook alternative" side of the Fediverse is easy to deploy and so lightweight in spite of its feature wealth?

[spoiler=Caution: Image hidden due to eye contact, crying, anger and Japanese profanity]

Explanation:

This image is a collage based on various memes.

The top row makes use of Wojaks, it basically is a Wojak comic. The two Wojaks on the right are Soyjaks, the third one from the left is essentially the same combination of a Soyjak and a Crying Wojak as seen in the Soyjaks vs Chads format. "Baka", as said by the Soyjak in the top right, is Japanese for "idiot" and hints at Misskey, as well as large parts of its target audience, being Japanese. It has become a meme of its own.

The bottom row re-uses the "Moth Lamp" meme. This time, however, "lämp", intentionally spelled with an umlaut as per the meme, does not mean a light source. Instead, it stands for a so-called "LAMP stack" which is the bare minimum Web server equipment.

• L stands for Linux and refers not to the operating system kernel, but to the whole software platform.
• A stands for the Apache HTTP Server.
• M stands for the MySQL database management system, nowadays usually in the shape of the MySQL fork MariaDB.
• P, in this case, stands for the PHP scripting language used for dynamic websites.

The three Fediverse server applications represented as moths in the bottom row, captioned with "LÄMP", are Friendica, a very powerful Facebook alternative created by Mike Macgirvin in 2010, Hubzilla, a very versatile and extremely powerful "federated content management system" which Mike Macgirvin himself created from 2015 out of his own Friendica fork, and the intentionally nameless application in the streams repository from 2021, itself at the end of a long line of forks by Mike Macgirvin again, starting at Hubzilla. None of the four have any exotic or heavy-weight server software requirements. They need JavaScript for parts of the UI, but otherwise, they can run on a bone-stock Web server, requiring remarkably few CPU and RAM resources.

The four projects in the top row, on the other hand, have more exotic and/or heavy-weight requirements.

The one in the top left is diaspora* from later in 2010 than Friendica, the only one in the image that does not support ActivityPub at all (it is only connected to the few Fediverse projects which support its own protocol, including Friendica and Hubzilla). diaspora* and Mastodon next to it are both written in Ruby on Rails. Thus, they require more hardware resources per user identity than the three at the bottom while not even nearly offering the latter's features.

Next to them, Pleroma from 2016 is famous for being much more lightweight than Mastodon while still offering more. But it is written in the fairly exotic Elixir language. Also, it can't use MySQL; it is only compatible with more complex PostgreSQL. In the meantime, Misskey, which dates back to 2014, is entirely based on JavaScript: It is written in Microsoft's TypeScript with Vue.js for the frontend. Let's say there's a reason why the former Firefish fork and now Misskey fork Iceshrimp is currently being re-written from scratch in C# as Iceshrimp.NET.

#Fediverse #diaspora* #Mastodon #Ruby on Rails #Pleroma #Elixir #PostgreSQL #Misskey #JavaScript #TypeScript #Vue.js #Friendica #Hubzilla #(streams) #MySQL #PHP #LAMP stack #Meme #FediMeme #Fediverse Meme #Wojak #Wojak comics #Soyjak #Crying Wojak #Moth #Lämp #Moth lamp #EyeContact #CWEyeContact #Profanity #CWProfanity #Swearing #CWSwearing #Swear word #Crying #CWCrying #Tears #Anger #CWAnger #Sensitive #⚠️

Ever wondered why the "Facebook alternative" side of the Fediverse is easy to deploy and so lightweight in spite of its feature wealth?

[spoiler=Caution: Image hidden due to eye contact, crying, anger and Japanese profanity]

Explanation:

This image is a collage based on various memes.

The top row makes use of Wojaks, it basically is a Wojak comic. The two Wojaks on the right are Soyjaks, the third one from the left is essentially the same combination of a Soyjak and a Crying Wojak as seen in the Soyjaks vs Chads format. "Baka", as said by the Soyjak in the top right, is Japanese for "idiot" and hints at Misskey, as well as large parts of its target audience, being Japanese. It has become a meme of its own.

The bottom row re-uses the "Moth Lamp" meme. This time, however, "lämp", intentionally spelled with an umlaut as per the meme, does not mean a light source. Instead, it stands for a so-called "LAMP stack" which is the bare minimum Web server equipment.

• L stands for Linux and refers not to the operating system kernel, but to the whole software platform.
• A stands for the Apache HTTP Server.
• M stands for the MySQL database management system, nowadays usually in the shape of the MySQL fork MariaDB.
• P, in this case, stands for the PHP scripting language used for dynamic websites.

The three Fediverse server applications represented as moths in the bottom row, captioned with "LÄMP", are Friendica, a very powerful Facebook alternative created by Mike Macgirvin in 2010, Hubzilla, a very versatile and extremely powerful "federated content management system" which Mike Macgirvin himself created from 2015 out of his own Friendica fork, and the intentionally nameless application in the streams repository from 2021, itself at the end of a long line of forks by Mike Macgirvin again, starting at Hubzilla. None of the four have any exotic or heavy-weight server software requirements. They need JavaScript for parts of the UI, but otherwise, they can run on a bone-stock Web server, requiring remarkably few CPU and RAM resources.

The four projects in the top row, on the other hand, have more exotic and/or heavy-weight requirements.

The one in the top left is diaspora* from later in 2010 than Friendica, the only one in the image that does not support ActivityPub at all (it is only connected to the few Fediverse projects which support its own protocol, including Friendica and Hubzilla). diaspora* and Mastodon next to it are both written in Ruby on Rails. Thus, they require more hardware resources per user identity than the three at the bottom while not even nearly offering the latter's features.

Next to them, Pleroma from 2016 is famous for being much more lightweight than Mastodon while still offering more. But it is written in the fairly exotic Elixir language. Also, it can't use MySQL; it is only compatible with more complex PostgreSQL. In the meantime, Misskey, which dates back to 2014, is entirely based on JavaScript: It is written in Microsoft's TypeScript with Vue.js for the frontend. Let's say there's a reason why the former Firefish fork and now Misskey fork Iceshrimp is currently being re-written from scratch in C# as Iceshrimp.NET.

#Fediverse #diaspora* #Mastodon #Ruby on Rails #Pleroma #Elixir #PostgreSQL #Misskey #JavaScript #TypeScript #Vue.js #Friendica #Hubzilla #(streams) #MySQL #PHP #LAMP stack #Meme #FediMeme #Fediverse Meme #Wojak #Wojak comics #Soyjak #Crying Wojak #Moth #Lämp #Moth lamp #EyeContact #CWEyeContact #Profanity #CWProfanity #Swearing #CWSwearing #Swear word #Crying #CWCrying #Tears #Anger #CWAnger #Sensitive #⚠️

Ever wondered why the "Facebook alternative" side of the Fediverse is easy to deploy and so lightweight in spite of its feature wealth?

[spoiler=Caution: Image hidden due to eye contact, crying, anger and Japanese profanity]

Explanation:

This image is a collage based on various memes.

The top row makes use of Wojaks, it basically is a Wojak comic. The two Wojaks on the right are Soyjaks, the third one from the left is essentially the same combination of a Soyjak and a Crying Wojak as seen in the Soyjaks vs Chads format. "Baka", as said by the Soyjak in the top right, is Japanese for "idiot" and hints at Misskey, as well as large parts of its target audience, being Japanese. It has become a meme of its own.

The bottom row re-uses the "Moth Lamp" meme. This time, however, "lämp", intentionally spelled with an umlaut as per the meme, does not mean a light source. Instead, it stands for a so-called "LAMP stack" which is the bare minimum Web server equipment.

• L stands for Linux and refers not to the operating system kernel, but to the whole software platform.
• A stands for the Apache HTTP Server.
• M stands for the MySQL database management system, nowadays usually in the shape of the MySQL fork MariaDB.
• P, in this case, stands for the PHP scripting language used for dynamic websites.

The three Fediverse server applications represented as moths in the bottom row, captioned with "LÄMP", are Friendica, a very powerful Facebook alternative created by Mike Macgirvin in 2010, Hubzilla, a very versatile and extremely powerful "federated content management system" which Mike Macgirvin himself created from 2015 out of his own Friendica fork, and the intentionally nameless application in the streams repository from 2021, itself at the end of a long line of forks by Mike Macgirvin again, starting at Hubzilla. None of the four have any exotic or heavy-weight server software requirements. They need JavaScript for parts of the UI, but otherwise, they can run on a bone-stock Web server, requiring remarkably few CPU and RAM resources.

The four projects in the top row, on the other hand, have more exotic and/or heavy-weight requirements.

The one in the top left is diaspora* from later in 2010 than Friendica, the only one in the image that does not support ActivityPub at all (it is only connected to the few Fediverse projects which support its own protocol, including Friendica and Hubzilla). diaspora* and Mastodon next to it are both written in Ruby on Rails. Thus, they require more hardware resources per user identity than the three at the bottom while not even nearly offering the latter's features.

Next to them, Pleroma from 2016 is famous for being much more lightweight than Mastodon while still offering more. But it is written in the fairly exotic Elixir language. Also, it can't use MySQL; it is only compatible with more complex PostgreSQL. In the meantime, Misskey, which dates back to 2014, is entirely based on JavaScript: It is written in Microsoft's TypeScript with Vue.js for the frontend. Let's say there's a reason why the former Firefish fork and now Misskey fork Iceshrimp is currently being re-written from scratch in C# as Iceshrimp.NET.

#Fediverse #diaspora* #Mastodon #Ruby on Rails #Pleroma #Elixir #PostgreSQL #Misskey #JavaScript #TypeScript #Vue.js #Friendica #Hubzilla #(streams) #MySQL #PHP #LAMP stack #Meme #FediMeme #Fediverse Meme #Wojak #Wojak comics #Soyjak #Crying Wojak #Moth #Lämp #Moth lamp #EyeContact #CWEyeContact #Profanity #CWProfanity #Swearing #CWSwearing #Swear word #Crying #CWCrying #Tears #Anger #CWAnger #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact and food]

Explanation:

The image is based on the "Cats Wanting Fruit Loops" meme template and the "Brother, May I Have Some Oats?" copypasta.

It references Loops, the federated TikTok alternative recently announced by @dansup, also creator of the Instagram alternative Pixelfed and the Android app Fedilab.

#Fediverse #Loops #Meme #FediMeme #Fediverse Meme #Image macro #Copypasta #Cats wanting Fruit Loops #Brother may I have some oats #EyeContact #CWEyeContact #Food #CWFood #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Oh No! Anyway" meme template.

It takes a jab at how vulnerable to spam especially Mastodon is while Hubzilla and (streams) are very resilient against it. Mastodon and other Fediverse projects have suffered from several waves of spam, one of which is on-going, but Hubzilla and (streams) have never been affected. There are various reasons for this.

One reason is the option to be notified if mentioned by a non-connection out of the blue. On Mastodon, this option is on by default, and next to nobody turns it off. On Hubzilla and (streams), this option is off by default, and hardly anyone turns it on.

Another reason is because both Hubzilla and (streams) have very advanced permissions systems with over a dozen parameters. For example, on Mastodon, anyone whom you follow can send you their posts and their boosts, and anyone can reply to your posts and send you DMs. The only countermeasures are muting them, blocking them, blocking their entire instance or having the admins or mods take care of them.

Hubzilla and (streams), in contrast, have vastly more powerful means of self-moderation. They have separate permissions settings for others to send posts, reply to posts and send DMs, amongst other permission settings. These permissions can be generally restricted for the whole Hubzilla or (streams) channel and then granted to certain contacts, keeping non-contacts out. Ignoring and blocking come on top as last resorts.

And this is only what users can do. Admins have some other tricks up their sleeves.

Lastly, it's very unlikely that someone will use Hubzilla or (streams) to send spam and even less likely that a bot will use Hubzilla or (streams) to send spam. You can't just create an account and spam away like on Mastodon. It's more likely for public instances of Hubzilla or (streams) to have registration approval than for Mastodon instances. Also, you have to create a channel to be able to post from it; not your account is your identity with everything in it, but your channel is. This is an extra obstacle. Lastly, while almost the entire rest of the Fediverse defaults to posting in public, both Hubzilla and (streams) default to posting privately to to certain contacts, changing which is anything but straight-forward.

#Fediverse #Mastodon #Hubzilla #(streams) #Spam #Meme #FediMeme #Fediverse Meme #Image macro #Reaction Image #Oh No! Anyway #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Oh No! Anyway" meme template.

It takes a jab at how vulnerable to spam especially Mastodon is while Hubzilla and (streams) are very resilient against it. Mastodon and other Fediverse projects have suffered from several waves of spam, one of which is on-going, but Hubzilla and (streams) have never been affected. There are various reasons for this.

One reason is the option to be notified if mentioned by a non-connection out of the blue. On Mastodon, this option is on by default, and next to nobody turns it off. On Hubzilla and (streams), this option is off by default, and hardly anyone turns it on.

Another reason is because both Hubzilla and (streams) have very advanced permissions systems with over a dozen parameters. For example, on Mastodon, anyone whom you follow can send you their posts and their boosts, and anyone can reply to your posts and send you DMs. The only countermeasures are muting them, blocking them, blocking their entire instance or having the admins or mods take care of them.

Hubzilla and (streams), in contrast, have vastly more powerful means of self-moderation. They have separate permissions settings for others to send posts, reply to posts and send DMs, amongst other permission settings. These permissions can be generally restricted for the whole Hubzilla or (streams) channel and then granted to certain contacts, keeping non-contacts out. Ignoring and blocking come on top as last resorts.

And this is only what users can do. Admins have some other tricks up their sleeves.

Lastly, it's very unlikely that someone will use Hubzilla or (streams) to send spam and even less likely that a bot will use Hubzilla or (streams) to send spam. You can't just create an account and spam away like on Mastodon. It's more likely for public instances of Hubzilla or (streams) to have registration approval than for Mastodon instances. Also, you have to create a channel to be able to post from it; not your account is your identity with everything in it, but your channel is. This is an extra obstacle. Lastly, while almost the entire rest of the Fediverse defaults to posting in public, both Hubzilla and (streams) default to posting privately to to certain contacts, changing which is anything but straight-forward.

#Fediverse #Mastodon #Hubzilla #(streams) #Spam #Meme #FediMeme #Fediverse Meme #Image macro #Reaction Image #Oh No! Anyway #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Oh No! Anyway" meme template.

It takes a jab at how vulnerable to spam especially Mastodon is while Hubzilla and (streams) are very resilient against it. Mastodon and other Fediverse projects have suffered from several waves of spam, one of which is on-going, but Hubzilla and (streams) have never been affected. There are various reasons for this.

One reason is the option to be notified if mentioned by a non-connection out of the blue. On Mastodon, this option is on by default, and next to nobody turns it off. On Hubzilla and (streams), this option is off by default, and hardly anyone turns it on.

Another reason is because both Hubzilla and (streams) have very advanced permissions systems with over a dozen parameters. For example, on Mastodon, anyone whom you follow can send you their posts and their boosts, and anyone can reply to your posts and send you DMs. The only countermeasures are muting them, blocking them, blocking their entire instance or having the admins or mods take care of them.

Hubzilla and (streams), in contrast, have vastly more powerful means of self-moderation. They have separate permissions settings for others to send posts, reply to posts and send DMs, amongst other permission settings. These permissions can be generally restricted for the whole Hubzilla or (streams) channel and then granted to certain contacts, keeping non-contacts out. Ignoring and blocking come on top as last resorts.

And this is only what users can do. Admins have some other tricks up their sleeves.

Lastly, it's very unlikely that someone will use Hubzilla or (streams) to send spam and even less likely that a bot will use Hubzilla or (streams) to send spam. You can't just create an account and spam away like on Mastodon. It's more likely for public instances of Hubzilla or (streams) to have registration approval than for Mastodon instances. Also, you have to create a channel to be able to post from it; not your account is your identity with everything in it, but your channel is. This is an extra obstacle. Lastly, while almost the entire rest of the Fediverse defaults to posting in public, both Hubzilla and (streams) default to posting privately to to certain contacts, changing which is anything but straight-forward.

#Fediverse #Mastodon #Hubzilla #(streams) #Spam #Meme #FediMeme #Fediverse Meme #Image macro #Reaction Image #Oh No! Anyway #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Oh No! Anyway" meme template.

It takes a jab at how vulnerable to spam especially Mastodon is while Hubzilla and (streams) are very resilient against it. Mastodon and other Fediverse projects have suffered from several waves of spam, one of which is on-going, but Hubzilla and (streams) have never been affected. There are various reasons for this.

One reason is the option to be notified if mentioned by a non-connection out of the blue. On Mastodon, this option is on by default, and next to nobody turns it off. On Hubzilla and (streams), this option is off by default, and hardly anyone turns it on.

Another reason is because both Hubzilla and (streams) have very advanced permissions systems with over a dozen parameters. For example, on Mastodon, anyone whom you follow can send you their posts and their boosts, and anyone can reply to your posts and send you DMs. The only countermeasures are muting them, blocking them, blocking their entire instance or having the admins or mods take care of them.

Hubzilla and (streams), in contrast, have vastly more powerful means of self-moderation. They have separate permissions settings for others to send posts, reply to posts and send DMs, amongst other permission settings. These permissions can be generally restricted for the whole Hubzilla or (streams) channel and then granted to certain contacts, keeping non-contacts out. Ignoring and blocking come on top as last resorts.

And this is only what users can do. Admins have some other tricks up their sleeves.

Lastly, it's very unlikely that someone will use Hubzilla or (streams) to send spam and even less likely that a bot will use Hubzilla or (streams) to send spam. You can't just create an account and spam away like on Mastodon. It's more likely for public instances of Hubzilla or (streams) to have registration approval than for Mastodon instances. Also, you have to create a channel to be able to post from it; not your account is your identity with everything in it, but your channel is. This is an extra obstacle. Lastly, while almost the entire rest of the Fediverse defaults to posting in public, both Hubzilla and (streams) default to posting privately to to certain contacts, changing which is anything but straight-forward.

#Fediverse #Mastodon #Hubzilla #(streams) #Spam #Meme #FediMeme #Fediverse Meme #Image macro #Reaction Image #Oh No! Anyway #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Oh No! Anyway" meme template.

It takes a jab at how vulnerable to spam especially Mastodon is while Hubzilla and (streams) are very resilient against it. Mastodon and other Fediverse projects have suffered from several waves of spam, one of which is on-going, but Hubzilla and (streams) have never been affected. There are various reasons for this.

One reason is the option to be notified if mentioned by a non-connection out of the blue. On Mastodon, this option is on by default, and next to nobody turns it off. On Hubzilla and (streams), this option is off by default, and hardly anyone turns it on.

Another reason is because both Hubzilla and (streams) have very advanced permissions systems with over a dozen parameters. For example, on Mastodon, anyone whom you follow can send you their posts and their boosts, and anyone can reply to your posts and send you DMs. The only countermeasures are muting them, blocking them, blocking their entire instance or having the admins or mods take care of them.

Hubzilla and (streams), in contrast, have vastly more powerful means of self-moderation. They have separate permissions settings for others to send posts, reply to posts and send DMs, amongst other permission settings. These permissions can be generally restricted for the whole Hubzilla or (streams) channel and then granted to certain contacts, keeping non-contacts out. Ignoring and blocking come on top as last resorts.

And this is only what users can do. Admins have some other tricks up their sleeves.

Lastly, it's very unlikely that someone will use Hubzilla or (streams) to send spam and even less likely that a bot will use Hubzilla or (streams) to send spam. You can't just create an account and spam away like on Mastodon. It's more likely for public instances of Hubzilla or (streams) to have registration approval than for Mastodon instances. Also, you have to create a channel to be able to post from it; not your account is your identity with everything in it, but your channel is. This is an extra obstacle. Lastly, while almost the entire rest of the Fediverse defaults to posting in public, both Hubzilla and (streams) default to posting privately to to certain contacts, changing which is anything but straight-forward.

#Fediverse #Mastodon #Hubzilla #(streams) #Spam #Meme #FediMeme #Fediverse Meme #Image macro #Reaction Image #Oh No! Anyway #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Pepe Silvia" meme template.

It references the complexity of the history of Fediverse server applications created by @Mike Macgirvin 🖥️ which started in July, 2010 with the release of Mistpark, known today as Friendica. It led through a maze of forks, all created by Mike from his own works, to his most recent project, Forte, from August, 2024. The only other two survivors from this history are Hubzilla from 2015 and the streams repository from 2021. In fact, the streams repository itself adds to the complexity of the history because it is not a project, and the software in it is intentionally without a name and a brand identity.

#Fediverse #Mistpark #Friendika #Friendica #Red #Red Matrix #Hubzilla #Osada #Zap #Mistpark 2020 #Misty #Redmatrix 2020 #Roadhouse #(streams) #Forte #Meme #FediMeme #Fediverse Meme #Image macro #Exploitable #Pepe Silvia #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Pepe Silvia" meme template.

It references the complexity of the history of Fediverse server applications created by @Mike Macgirvin 🖥️ which started in July, 2010 with the release of Mistpark, known today as Friendica. It led through a maze of forks, all created by Mike from his own works, to his most recent project, Forte, from August, 2024. The only other two survivors from this history are Hubzilla from 2015 and the streams repository from 2021. In fact, the streams repository itself adds to the complexity of the history because it is not a project, and the software in it is intentionally without a name and a brand identity.

#Fediverse #Mistpark #Friendika #Friendica #Red #Red Matrix #Hubzilla #Osada #Zap #Mistpark 2020 #Misty #Redmatrix 2020 #Roadhouse #(streams) #Forte #Meme #FediMeme #Fediverse Meme #Image macro #Exploitable #Pepe Silvia #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Pepe Silvia" meme template.

It references the complexity of the history of Fediverse server applications created by @Mike Macgirvin 🖥️ which started in July, 2010 with the release of Mistpark, known today as Friendica. It led through a maze of forks, all created by Mike from his own works, to his most recent project, Forte, from August, 2024. The only other two survivors from this history are Hubzilla from 2015 and the streams repository from 2021. In fact, the streams repository itself adds to the complexity of the history because it is not a project, and the software in it is intentionally without a name and a brand identity.

#Fediverse #Mistpark #Friendika #Friendica #Red #Red Matrix #Hubzilla #Osada #Zap #Mistpark 2020 #Misty #Redmatrix 2020 #Roadhouse #(streams) #Forte #Meme #FediMeme #Fediverse Meme #Image macro #Exploitable #Pepe Silvia #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Pepe Silvia" meme template.

It references the complexity of the history of Fediverse server applications created by @Mike Macgirvin 🖥️ which started in July, 2010 with the release of Mistpark, known today as Friendica. It led through a maze of forks, all created by Mike from his own works, to his most recent project, Forte, from August, 2024. The only other two survivors from this history are Hubzilla from 2015 and the streams repository from 2021. In fact, the streams repository itself adds to the complexity of the history because it is not a project, and the software in it is intentionally without a name and a brand identity.

#Fediverse #Mistpark #Friendika #Friendica #Red #Red Matrix #Hubzilla #Osada #Zap #Mistpark 2020 #Misty #Redmatrix 2020 #Roadhouse #(streams) #Forte #Meme #FediMeme #Fediverse Meme #Image macro #Exploitable #Pepe Silvia #EyeContact #CWEyeContact #Sensitive #⚠️

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

The image is based on the "Pepe Silvia" meme template.

It references the complexity of the history of Fediverse server applications created by @Mike Macgirvin 🖥️ which started in July, 2010 with the release of Mistpark, known today as Friendica. It led through a maze of forks, all created by Mike from his own works, to his most recent project, Forte, from August, 2024. The only other two survivors from this history are Hubzilla from 2015 and the streams repository from 2021. In fact, the streams repository itself adds to the complexity of the history because it is not a project, and the software in it is intentionally without a name and a brand identity.

#Fediverse #Mistpark #Friendika #Friendica #Red #Red Matrix #Hubzilla #Osada #Zap #Mistpark 2020 #Misty #Redmatrix 2020 #Roadhouse #(streams) #Forte #Meme #FediMeme #Fediverse Meme #Image macro #Exploitable #Pepe Silvia #EyeContact #CWEyeContact #Sensitive #⚠️

The Fediverse, late summer of 2024:

The streams repository has no official maintainer, and it doesn't look like it'll have a new one anytime soon.

Firefish had its death announced by its maintainer.

And /kbin was already killed by its maintainer without warning.

[spoiler=Caution: Image hidden due to foul language and potential eye contact]

Explanation:

The image hints at Fediverse server software whose key maintainer has largely or entirely quit. It is not based on a specific template, but it makes use of the meme phrases "That's cute" and "Bitch, please".

(streams)

The top logo is that of the streams repository. It contains an intentionally nameless, brandless, public-domain-licensed Fediverse server application, one of the most advanced Fediverse server applications with the one most advanced set of permission controls. It was created in October, 2021, as a fork of one of three forks of a fork of probably another fork of Hubzilla, the all-purpose Swiss army knife of the Fediverse, which itself is a fork of maybe another fork of Friendica, a decentralised Facebook alternative from as early as 2010. All of this, including the forks in-between, was created by one man, Mike Macgirvin.

On August 31st, Mike announced in a private post only sent to his connections that the streams repository is basically up for grabs because he quit maintaining Fediverse software. Just like with Friendica in 2012 and Hubzilla in 2018, he wanted the community to take over.

But what was easy for Friendica and Hubzilla was expected to be difficult for (streams), as the nameless application is semi-officially called. That's because it only has a few dozen active users, none of which has both the skills and the time to take over as the new main maintainer. It didn't help that Mike dropped it in the middle of the transformation process towards nomadic identity via ActivityPub, in such a buggy state that inviting more people to (streams) is pretty much out of question.

Firefish

The Firefish logo in the middle stands for the official announcement of Firefish's end of life. Naskya, who rather involuntarily ended up the sole new Firefish developer after original forker and maintainer Kainoa had no time for it anymore, declared not having the energy to continue with the project. Firefish's code repository was put into maintenance mode which means that it won't get any new features anymore. At the end of 2024, support will end. And at the end of February, 2025, both the code repository and the official lighthouse instance will be shut down which will practically mark the official end of Firefish.

/kbin

The /kbin logo at the bottom stands for the even earlier death of /kbin. The ambitious Reddit alternative had only had one sole developer from the very beginning. Ernest Wisniewski never had enough time to make /kbin mature because /kbin was rushed by former Redditors at a very early alpha stage. At the same time, he didn't let anyone help him. Apparently, everything eventually became too much for him. Nine months ago already, he quit maintaining /kbin altogether. This summer, he shut down both the official /kbin website and the official lighthouse instance which made up the huge majority of /kbin's size, both with no announcement. There has never been any official statement by Ernest. Some information can be found in this post on Lemmy. What's left are a few third-party /kbin instances whose admins may not even have noticed that /kbin is dead.

#Fediverse #(streams) #/kbin #Firefish #Meme #FediMeme #Fediverse Meme #That's Cute #Bitch Please #Swearing #Eye Contact #Sensitive #⚠️

The Fediverse, late summer of 2024:

The streams repository has no official maintainer, and it doesn't look like it'll have a new one anytime soon.

Firefish had its death announced by its maintainer.

And /kbin was already killed by its maintainer without warning.

[spoiler=Caution: Image hidden due to foul language and potential eye contact]

Explanation:

The image hints at Fediverse server software whose key maintainer has largely or entirely quit. It is not based on a specific template, but it makes use of the meme phrases "That's cute" and "Bitch, please".

(streams)

The top logo is that of the streams repository. It contains an intentionally nameless, brandless, public-domain-licensed Fediverse server application, one of the most advanced Fediverse server applications with the one most advanced set of permission controls. It was created in October, 2021, as a fork of one of three forks of a fork of probably another fork of Hubzilla, the all-purpose Swiss army knife of the Fediverse, which itself is a fork of maybe another fork of Friendica, a decentralised Facebook alternative from as early as 2010. All of this, including the forks in-between, was created by one man, Mike Macgirvin.

On August 31st, Mike announced in a private post only sent to his connections that the streams repository is basically up for grabs because he quit maintaining Fediverse software. Just like with Friendica in 2012 and Hubzilla in 2018, he wanted the community to take over.

But what was easy for Friendica and Hubzilla was expected to be difficult for (streams), as the nameless application is semi-officially called. That's because it only has a few dozen active users, none of which has both the skills and the time to take over as the new main maintainer. It didn't help that Mike dropped it in the middle of the transformation process towards nomadic identity via ActivityPub, in such a buggy state that inviting more people to (streams) is pretty much out of question.

Firefish

The Firefish logo in the middle stands for the official announcement of Firefish's end of life. Naskya, who rather involuntarily ended up the sole new Firefish developer after original forker and maintainer Kainoa had no time for it anymore, declared not having the energy to continue with the project. Firefish's code repository was put into maintenance mode which means that it won't get any new features anymore. At the end of 2024, support will end. And at the end of February, 2025, both the code repository and the official lighthouse instance will be shut down which will practically mark the official end of Firefish.

/kbin

The /kbin logo at the bottom stands for the even earlier death of /kbin. The ambitious Reddit alternative had only had one sole developer from the very beginning. Ernest Wisniewski never had enough time to make /kbin mature because /kbin was rushed by former Redditors at a very early alpha stage. At the same time, he didn't let anyone help him. Apparently, everything eventually became too much for him. Nine months ago already, he quit maintaining /kbin altogether. This summer, he shut down both the official /kbin website and the official lighthouse instance which made up the huge majority of /kbin's size, both with no announcement. There has never been any official statement by Ernest. Some information can be found in this post on Lemmy. What's left are a few third-party /kbin instances whose admins may not even have noticed that /kbin is dead.

#Fediverse #(streams) #/kbin #Firefish #Meme #FediMeme #Fediverse Meme #That's Cute #Bitch Please #Swearing #Eye Contact #Sensitive #⚠️

The Fediverse, late summer of 2024:

The streams repository has no official maintainer, and it doesn't look like it'll have a new one anytime soon.

Firefish had its death announced by its maintainer.

And /kbin was already killed by its maintainer without warning.

[spoiler=Caution: Image hidden due to foul language and potential eye contact]

Explanation:

The image hints at Fediverse server software whose key maintainer has largely or entirely quit. It is not based on a specific template, but it makes use of the meme phrases "That's cute" and "Bitch, please".

(streams)

The top logo is that of the streams repository. It contains an intentionally nameless, brandless, public-domain-licensed Fediverse server application, one of the most advanced Fediverse server applications with the one most advanced set of permission controls. It was created in October, 2021, as a fork of one of three forks of a fork of probably another fork of Hubzilla, the all-purpose Swiss army knife of the Fediverse, which itself is a fork of maybe another fork of Friendica, a decentralised Facebook alternative from as early as 2010. All of this, including the forks in-between, was created by one man, Mike Macgirvin.

On August 31st, Mike announced in a private post only sent to his connections that the streams repository is basically up for grabs because he quit maintaining Fediverse software. Just like with Friendica in 2012 and Hubzilla in 2018, he wanted the community to take over.

But what was easy for Friendica and Hubzilla was expected to be difficult for (streams), as the nameless application is semi-officially called. That's because it only has a few dozen active users, none of which has both the skills and the time to take over as the new main maintainer. It didn't help that Mike dropped it in the middle of the transformation process towards nomadic identity via ActivityPub, in such a buggy state that inviting more people to (streams) is pretty much out of question.

Firefish

The Firefish logo in the middle stands for the official announcement of Firefish's end of life. Naskya, who rather involuntarily ended up the sole new Firefish developer after original forker and maintainer Kainoa had no time for it anymore, declared not having the energy to continue with the project. Firefish's code repository was put into maintenance mode which means that it won't get any new features anymore. At the end of 2024, support will end. And at the end of February, 2025, both the code repository and the official lighthouse instance will be shut down which will practically mark the official end of Firefish.

/kbin

The /kbin logo at the bottom stands for the even earlier death of /kbin. The ambitious Reddit alternative had only had one sole developer from the very beginning. Ernest Wisniewski never had enough time to make /kbin mature because /kbin was rushed by former Redditors at a very early alpha stage. At the same time, he didn't let anyone help him. Apparently, everything eventually became too much for him. Nine months ago already, he quit maintaining /kbin altogether. This summer, he shut down both the official /kbin website and the official lighthouse instance which made up the huge majority of /kbin's size, both with no announcement. There has never been any official statement by Ernest. Some information can be found in this post on Lemmy. What's left are a few third-party /kbin instances whose admins may not even have noticed that /kbin is dead.

#Fediverse #(streams) #/kbin #Firefish #Meme #FediMeme #Fediverse Meme #That's Cute #Bitch Please #Swearing #Eye Contact #Sensitive #⚠️

The Fediverse, late summer of 2024:

The streams repository has no official maintainer, and it doesn't look like it'll have a new one anytime soon.

Firefish had its death announced by its maintainer.

And /kbin was already killed by its maintainer without warning.

[spoiler=Caution: Image hidden due to foul language and potential eye contact]

Explanation:

The image hints at Fediverse server software whose key maintainer has largely or entirely quit. It is not based on a specific template, but it makes use of the meme phrases "That's cute" and "Bitch, please".

(streams)

The top logo is that of the streams repository. It contains an intentionally nameless, brandless, public-domain-licensed Fediverse server application, one of the most advanced Fediverse server applications with the one most advanced set of permission controls. It was created in October, 2021, as a fork of one of three forks of a fork of probably another fork of Hubzilla, the all-purpose Swiss army knife of the Fediverse, which itself is a fork of maybe another fork of Friendica, a decentralised Facebook alternative from as early as 2010. All of this, including the forks in-between, was created by one man, Mike Macgirvin.

On August 31st, Mike announced in a private post only sent to his connections that the streams repository is basically up for grabs because he quit maintaining Fediverse software. Just like with Friendica in 2012 and Hubzilla in 2018, he wanted the community to take over.

But what was easy for Friendica and Hubzilla was expected to be difficult for (streams), as the nameless application is semi-officially called. That's because it only has a few dozen active users, none of which has both the skills and the time to take over as the new main maintainer. It didn't help that Mike dropped it in the middle of the transformation process towards nomadic identity via ActivityPub, in such a buggy state that inviting more people to (streams) is pretty much out of question.

Firefish

The Firefish logo in the middle stands for the official announcement of Firefish's end of life. Naskya, who rather involuntarily ended up the sole new Firefish developer after original forker and maintainer Kainoa had no time for it anymore, declared not having the energy to continue with the project. Firefish's code repository was put into maintenance mode which means that it won't get any new features anymore. At the end of 2024, support will end. And at the end of February, 2025, both the code repository and the official lighthouse instance will be shut down which will practically mark the official end of Firefish.

/kbin

The /kbin logo at the bottom stands for the even earlier death of /kbin. The ambitious Reddit alternative had only had one sole developer from the very beginning. Ernest Wisniewski never had enough time to make /kbin mature because /kbin was rushed by former Redditors at a very early alpha stage. At the same time, he didn't let anyone help him. Apparently, everything eventually became too much for him. Nine months ago already, he quit maintaining /kbin altogether. This summer, he shut down both the official /kbin website and the official lighthouse instance which made up the huge majority of /kbin's size, both with no announcement. There has never been any official statement by Ernest. Some information can be found in this post on Lemmy. What's left are a few third-party /kbin instances whose admins may not even have noticed that /kbin is dead.

#Fediverse #(streams) #/kbin #Firefish #Meme #FediMeme #Fediverse Meme #That's Cute #Bitch Please #Swearing #Eye Contact #Sensitive #⚠️

The Fediverse, late summer of 2024:

The streams repository has no official maintainer, and it doesn't look like it'll have a new one anytime soon.

Firefish had its death announced by its maintainer.

And /kbin was already killed by its maintainer without warning.

[spoiler=Caution: Image hidden due to foul language and potential eye contact]

Explanation:

The image hints at Fediverse server software whose key maintainer has largely or entirely quit. It is not based on a specific template, but it makes use of the meme phrases "That's cute" and "Bitch, please".

(streams)

The top logo is that of the streams repository. It contains an intentionally nameless, brandless, public-domain-licensed Fediverse server application, one of the most advanced Fediverse server applications with the one most advanced set of permission controls. It was created in October, 2021, as a fork of one of three forks of a fork of probably another fork of Hubzilla, the all-purpose Swiss army knife of the Fediverse, which itself is a fork of maybe another fork of Friendica, a decentralised Facebook alternative from as early as 2010. All of this, including the forks in-between, was created by one man, Mike Macgirvin.

On August 31st, Mike announced in a private post only sent to his connections that the streams repository is basically up for grabs because he quit maintaining Fediverse software. Just like with Friendica in 2012 and Hubzilla in 2018, he wanted the community to take over.

But what was easy for Friendica and Hubzilla was expected to be difficult for (streams), as the nameless application is semi-officially called. That's because it only has a few dozen active users, none of which has both the skills and the time to take over as the new main maintainer. It didn't help that Mike dropped it in the middle of the transformation process towards nomadic identity via ActivityPub, in such a buggy state that inviting more people to (streams) is pretty much out of question.

Firefish

The Firefish logo in the middle stands for the official announcement of Firefish's end of life. Naskya, who rather involuntarily ended up the sole new Firefish developer after original forker and maintainer Kainoa had no time for it anymore, declared not having the energy to continue with the project. Firefish's code repository was put into maintenance mode which means that it won't get any new features anymore. At the end of 2024, support will end. And at the end of February, 2025, both the code repository and the official lighthouse instance will be shut down which will practically mark the official end of Firefish.

/kbin

The /kbin logo at the bottom stands for the even earlier death of /kbin. The ambitious Reddit alternative had only had one sole developer from the very beginning. Ernest Wisniewski never had enough time to make /kbin mature because /kbin was rushed by former Redditors at a very early alpha stage. At the same time, he didn't let anyone help him. Apparently, everything eventually became too much for him. Nine months ago already, he quit maintaining /kbin altogether. This summer, he shut down both the official /kbin website and the official lighthouse instance which made up the huge majority of /kbin's size, both with no announcement. There has never been any official statement by Ernest. Some information can be found in this post on Lemmy. What's left are a few third-party /kbin instances whose admins may not even have noticed that /kbin is dead.

#Fediverse #(streams) #/kbin #Firefish #Meme #FediMeme #Fediverse Meme #That's Cute #Bitch Please #Swearing #Eye Contact #Sensitive #⚠️

I guess we've all reacted this way at least once already.

[spoiler=Caution: Image hidden due to eye contact]

Explanation:

This is a universal reaction image macro from whenever Mastodon acts in a way that displeases the developers or users of non-Mastodon Fediverse projects, sometimes even Mastodon's own users. Whenever Mastodon's self-imposed limitations stand in the way of something, whenever Mastodon's refusal to comply with established standards and preference for non-standard solutions leads to incompatibility et cetera, this image macro can be used to blame it all on Mastodon's creator, Eugen Rochko, also known as Gargron.

It is based on the "Dinkleberg" meme template. An explanation can be found on KnowYourMeme.

#Mastodon #Meme #FediMeme #Fediverse Meme #Reaction Image #Dinkleberg #Sensitive #⚠️