20
How to convince my uni / dept. to switch to Mastodon? (lemmy.world)
submitted 1 week ago* (last edited 1 week ago) by Maroon@lemmy.world to c/selfhosted@lemmy.world
21 comments fedilink hide all child comments

I want to capitalise on the current "X-odus" momentum, and convince my university (or at least my department, which is quite big) to have its own Mastodon server.

My rationale is that if I can convince my uni/dept that they will have better reach, control and experience with Mastodon, it will help populate the Fediverse and bring more academics on this platform to disseminate their research.

The reason I am asking the self-hosting community for help is because I know nothing about hosting my own Mastodon server, but should I manage to have a talk with my IT head or the dept head and convince them to come to the Fediverse, I might need to spin up a server for them.

  1. How easy is it to get Mastodon up and going?
  2. How costly a hardware do I need to ask for?
  3. How expensive is it to run the server annually?
  4. Any other points or aspects I need to keep in mind?
you are viewing a single comment's thread
view the rest of the comments
[-] Mora@pawb.social 3 points 1 week ago

use the fediverse through threads or bluesky

Bluesky is not part of the fediverse and threads is mostly technically capable to be part of it - it is however blocked from the most other instances.

[-] 01189998819991197253@infosec.pub 1 points 1 week ago

Bluesky is supposed to decentralized, though it doesn't seem to be. Threads being blocked doesn't change the fact that it is technically part of the verse, although a red herring. Maybe both poor examples, but they're alternatives to the verse, which was my point. Maybe adding a public mastodon instance as an alternative would have been a better example, but the main point stands: a uni isn't likely going to host their own instance, due to the inherent risk associated with it.

this post was submitted on 17 Nov 2024
20 points (85.7% liked)

Selfhosted

40359 readers
370 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz