- 3 servidors necessiten 192+173+117 = 482 megues de RAM
- 1 servidor 322+300+290+290 = 1.202 megues de RAM
- 1 servidor (veure imatge) 491 megues de RAM
- 1 servidor (veure imatge) 395,3 de RAM

Tots els servidors tenen un sol usuari actiu.
és la millor opció, clarament ( ) 😀

També tinc dades de
- 1 sol servidor Misskey necessita 945,6 megues de RAM, el segon pitjor en consum de RAM després de Mastodon.
Igual que els anteriors servidors, aquest de Misskey només té un usuari actiu.

guanya a tots en consum de RAM.

Question for #FediAdmin , especially the ones managing a single-user instance (or just with very few users):

How much RAM is currently using your fedi software, whether it is #Mastodon#Akkoma#GoToSocial or one of the fifty shades of #Misskey (and by RAM I'm meaning "in total", not just the software's main process, also the database and additionnai stuff)

It's really out of curiosity. For instance, soc(dot)breadcat(dot)run currently uses approx 4,5Gb (4Gb for Akkoma's main processes and ~500Mb for the DB, on Docker)

Repost appreciated nice-three-hearts

Question for #FediAdmin , especially the ones managing a single-user instance (or just with very few users):

How much RAM is currently using your fedi software, whether it is #Mastodon#Akkoma#GoToSocial or one of the fifty shades of #Misskey (and by RAM I'm meaning "in total", not just the software's main process, also the database and additionnai stuff)

It's really out of curiosity. For instance, soc(dot)breadcat(dot)run currently uses approx 4,5Gb (4Gb for Akkoma's main processes and ~500Mb for the DB, on Docker)

Repost appreciated nice-three-hearts

⚠️ Mastodon and Misskey will never ask you to verify your ID.

This is a scam attempting to collect personal information and, in some cases, hijack accounts by tricking you into clicking malicious links.

⚠️ However, Mastodon and Misskey do offer an option in your account settings to enable two-step verification for logins.

For your own security and to help prevent brute-force attacks, it’s strongly recommended that you enable this feature on your account.

#Fediverse#ActivityPub#Mastodon#Misskey

⚠️ Mastodon and Misskey will never ask you to verify your ID.

This is a scam attempting to collect personal information and, in some cases, hijack accounts by tricking you into clicking malicious links.

⚠️ However, Mastodon and Misskey do offer an option in your account settings to enable two-step verification for logins.

For your own security and to help prevent brute-force attacks, it’s strongly recommended that you enable this feature on your account.

#Fediverse#ActivityPub#Mastodon#Misskey

Fragmentation on the Fediverse is a real problem.

Hypothetically, let’s say I’m an admin. I don’t like "John Doe" (just a random example). Instead of simply blocking John Doe myself, I demand that "Billy Bob" — the admin of his instance — remove him entirely.

Billy Bob refuses, because John Doe hasn’t broken any rules. So, being an egotistical maniac, I blacklist Billy Bob’s entire instance — 5,000+ innocent users who had nothing to do with anything.

I also have 5,000+ users on my instance. Now you’ve got over 10,000 people who can’t communicate, all because of a personal disagreement.

This kind of thing happens far too often on the Fediverse. If you create more than one account (on different instances), you’ll likely discover people you didn’t even know existed — people you’d want to follow but previously couldn’t, due to the growing fragmentation across the network.

The scale of the problem becomes even more obvious when you move to a different instance. You’ll likely find that not everyone you currently follow can be followed from the new site.

The solution?

Right now, it means having more than one account just to keep in touch with everyone you want to follow.

How crazy is that?

#Fediverse#ActivityPub#Mastodon#Misskey

Fragmentation on the Fediverse is a real problem.

Hypothetically, let’s say I’m an admin. I don’t like "John Doe" (just a random example). Instead of simply blocking John Doe myself, I demand that "Billy Bob" — the admin of his instance — remove him entirely.

Billy Bob refuses, because John Doe hasn’t broken any rules. So, being an egotistical maniac, I blacklist Billy Bob’s entire instance — 5,000+ innocent users who had nothing to do with anything.

I also have 5,000+ users on my instance. Now you’ve got over 10,000 people who can’t communicate, all because of a personal disagreement.

This kind of thing happens far too often on the Fediverse. If you create more than one account (on different instances), you’ll likely discover people you didn’t even know existed — people you’d want to follow but previously couldn’t, due to the growing fragmentation across the network.

The scale of the problem becomes even more obvious when you move to a different instance. You’ll likely find that not everyone you currently follow can be followed from the new site.

The solution?

Right now, it means having more than one account just to keep in touch with everyone you want to follow.

How crazy is that?

#Fediverse#ActivityPub#Mastodon#Misskey

I have now found 1070 verified accounts from media organizations in the #Fediverse, but only on #Mastodon, #Flipboard, #Threads, #Bluesky, #Ghost and #Peertube.

Just one is on #Sharkey (👋🏻 @heiseBotti) and none on #Pixelfed, #Lemmy, #Piefed, #Misskey & Co. Are there really none there, or did I miss some?

Source:
https://fingolas.eu/fediverse/overview.html

@fediverse

Curious. Why did someone think it necessary to do sharkey and iceshrimp. What is wrong with Misskey?

I'm curious about people's thoughts around Misskey and its forked projects.

  1. Why is Misskey so popular in Asia, but not used much in the west? Why do you think the preferences are so different between the regions?
  2. What is wrong with Misskey that some people are willing to invest their time and money on separate forks (IceShrimp, Sharkey). What's the difference between the forks and the originals?
  3. Does anyone have experience running any of these? Do they have any downsides like, for example, a database that grows unreasonably fast or that requires too many resources?