#singleuser — Public Fediverse posts

Struggling a bit with the whole hashtag review section in admin/moderation. Surely, as a single-user instance, this is about content that I am/am not interested in? So if I say 'Not Trendable', or 'Not Used' (eg.) then that's okay? If this is how it works why do some tags come back asking for a review? To change my mind? Surely having a single-user instance is all about personalisation, or, am I missing something here?

#fediverse #mastodon #admin #owner #singleuser #personalisation #moderation

Struggling a bit with the whole hashtag review section in admin/moderation. Surely, as a single-user instance, this is about content that I am/am not interested in? So if I say 'Not Trendable', or 'Not Used' (eg.) then that's okay? If this is how it works why do some tags come back asking for a review? To change my mind? Surely having a single-user instance is all about personalisation, or, am I missing something here?

#fediverse #mastodon #admin #owner #singleuser #personalisation #moderation

Struggling a bit with the whole hashtag review section in admin/moderation. Surely, as a single-user instance, this is about content that I am/am not interested in? So if I say 'Not Trendable', or 'Not Used' (eg.) then that's okay? If this is how it works why do some tags come back asking for a review? To change my mind? Surely having a single-user instance is all about personalisation, or, am I missing something here?

#fediverse #mastodon #admin #owner #singleuser #personalisation #moderation

Struggling a bit with the whole hashtag review section in admin/moderation. Surely, as a single-user instance, this is about content that I am/am not interested in? So if I say 'Not Trendable', or 'Not Used' (eg.) then that's okay? If this is how it works why do some tags come back asking for a review? To change my mind? Surely having a single-user instance is all about personalisation, or, am I missing something here?

#fediverse #mastodon #admin #owner #singleuser #personalisation #moderation

Struggling a bit with the whole hashtag review section in admin/moderation. Surely, as a single-user instance, this is about content that I am/am not interested in? So if I say 'Not Trendable', or 'Not Used' (eg.) then that's okay? If this is how it works why do some tags come back asking for a review? To change my mind? Surely having a single-user instance is all about personalisation, or, am I missing something here?

#fediverse #mastodon #admin #owner #singleuser #personalisation #moderation

Thinking about setting up a #gotosocial instance as a possible alternative to my current Mastodon instance. Seems quite straight forward to run as a self-contained single (podman) container, which is an approach I have come to like more and more. I already run my own #Forgejo instance that way. When I have time to spare, I will give it a try :)

#SelfHost #ActivityPub #SingleUser

Thinking about setting up a #gotosocial instance as a possible alternative to my current Mastodon instance. Seems quite straight forward to run as a self-contained single (podman) container, which is an approach I have come to like more and more. I already run my own #Forgejo instance that way. When I have time to spare, I will give it a try :)

#SelfHost #ActivityPub #SingleUser

Thinking about setting up a #gotosocial instance as a possible alternative to my current Mastodon instance. Seems quite straight forward to run as a self-contained single (podman) container, which is an approach I have come to like more and more. I already run my own #Forgejo instance that way. When I have time to spare, I will give it a try :)

#SelfHost #ActivityPub #SingleUser

Thinking about setting up a #gotosocial instance as a possible alternative to my current Mastodon instance. Seems quite straight forward to run as a self-contained single (podman) container, which is an approach I have come to like more and more. I already run my own #Forgejo instance that way. When I have time to spare, I will give it a try :)

#SelfHost #ActivityPub #SingleUser

Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

Check out the #alttext or my #profile info for information on how to connect.

#bbs
#rc2014bbs
#rcbox

Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

Check out the #alttext or my #profile info for information on how to connect.

#bbs
#rc2014bbs
#rcbox

Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

Check out the #alttext or my #profile info for information on how to connect.

#bbs
#rc2014bbs
#rcbox

Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

Check out the #alttext or my #profile info for information on how to connect.

#bbs
#rc2014bbs
#rcbox

Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

Check out the #alttext or my #profile info for information on how to connect.

#bbs
#rc2014bbs
#rcbox

Since setting my single-user instance up in 2018, I forgot to set up media cleanup. Before I do that, some stats for my 6yo instance:

$ for flag in "" --remove-headers --prune-profiles; do tootctl media remove $flag --dry_run; done
Removed 421484 media attachments (approx. 357 GB) (DRY RUN)
Visited 169679 accounts and removed profile media totaling 27.7 GB (DRY RUN)
Visited 169680 accounts and removed profile media totaling 39.8 GB (DRY RUN)

And media/month graph...

#SingleUser #MastoAdmin

Since setting my single-user instance up in 2018, I forgot to set up media cleanup. Before I do that, some stats for my 6yo instance:

$ for flag in "" --remove-headers --prune-profiles; do tootctl media remove $flag --dry_run; done
Removed 421484 media attachments (approx. 357 GB) (DRY RUN)
Visited 169679 accounts and removed profile media totaling 27.7 GB (DRY RUN)
Visited 169680 accounts and removed profile media totaling 39.8 GB (DRY RUN)

And media/month graph...

#SingleUser #MastoAdmin

Since setting my single-user instance up in 2018, I forgot to set up media cleanup. Before I do that, some stats for my 6yo instance:

$ for flag in "" --remove-headers --prune-profiles; do tootctl media remove $flag --dry_run; done
Removed 421484 media attachments (approx. 357 GB) (DRY RUN)
Visited 169679 accounts and removed profile media totaling 27.7 GB (DRY RUN)
Visited 169680 accounts and removed profile media totaling 39.8 GB (DRY RUN)

And media/month graph...

#SingleUser #MastoAdmin

Since setting my single-user instance up in 2018, I forgot to set up media cleanup. Before I do that, some stats for my 6yo instance:

$ for flag in "" --remove-headers --prune-profiles; do tootctl media remove $flag --dry_run; done
Removed 421484 media attachments (approx. 357 GB) (DRY RUN)
Visited 169679 accounts and removed profile media totaling 27.7 GB (DRY RUN)
Visited 169680 accounts and removed profile media totaling 39.8 GB (DRY RUN)

And media/month graph...

#SingleUser #MastoAdmin

Since setting my single-user instance up in 2018, I forgot to set up media cleanup. Before I do that, some stats for my 6yo instance:

$ for flag in "" --remove-headers --prune-profiles; do tootctl media remove $flag --dry_run; done
Removed 421484 media attachments (approx. 357 GB) (DRY RUN)
Visited 169679 accounts and removed profile media totaling 27.7 GB (DRY RUN)
Visited 169680 accounts and removed profile media totaling 39.8 GB (DRY RUN)

And media/month graph...

#SingleUser #MastoAdmin

When I poked around with Postmarks (a federated bookmarking service) last year, I briefly mentioned another federated server, Shuttlecraft… but I never followed up on that.

Shuttlecraft is a single-user ActivityPub-compatible application that can run on a platform like Glitch – in fact, it’s more-or-less a single-click deployment to fork and install on Glitch.

I’ve written about being all-in on the Fediverse and I generally try a lot of different things out. I created a Shuttlecraft instance for myself around the same time I set up Postmarks last year – both run on Glitch, both are somewhat experimental / in-progress and unfinished. The fact is that I use my Postmarks instance all the time for logging links of interest, but Shuttlecraft has really just been sitting there without very much interaction. That’s mostly deliberate, it’s a playground more than anything else, and it can be handy for playing with interactions with other ActivityPub servers.

However – yesterday I thought I’d take a quick look at it, only to discover that my Glitch app was down.

After doing some digging in the console and logs, I found that Node was complaining about being unable to load a module. That was surprising to me, as I hadn’t changed anything there for a long while. It turned out that what was actually happening was that the container’s disk allocation had run out, and the log message itself was spurious.

To be fair, the Shuttlecraft README is very clear that a) it’s an unsupported side-project from the author Ben Brown, and b) …

all data is written as PLAIN TEXT FILES to the disk.

Right now, the app builds an IN-MEMORY INDEX of EVERY SINGLE POST. This will work for several thousand posts, but … maybe not for 10,000s of posts. I’m not sure how far it will go. I have ideas about being able to shard the index into multiple files and page through it, etc. But.

It took a bit of very messy and imperfect cleanup inside hidden directories in the Glitch container, but for now, I have my small instance back up again. Realistically, it is probably not worth following / I don’t look at it much / it will fall over again, before much longer – but it’s also a fun thing to tinker with, and the code is quick to tweak in the Glitch editor.

In the past few months, quite a few things have changed in the ecosystem – for example, I’m now on Threads, and my account is federated out from there. Shuttlecraft is missing something in its ability to play nicely with that, which is a bit sad… maybe I’ll have to have a look into it at some stage.

I’ll have to look at some more Fediverse-compatible apps soon, hopefully more resilient ones! 🙂 Fediforum is coming up next month, and that’s usually a great place to learn about what developers are working on across the ActivityPub ecosystem.

https://andypiper.co.uk/2024/08/07/recovering-my-shuttlecraft/

#Blaugust2024 #100DaysToOffload #activitypub #Coding #fediverse #glitch #postmarks #selfHosting #singleUser

When I poked around with Postmarks (a federated bookmarking service) last year, I briefly mentioned another federated server, Shuttlecraft… but I never followed up on that.

Shuttlecraft is a single-user ActivityPub-compatible application that can run on a platform like Glitch – in fact, it’s more-or-less a single-click deployment to fork and install on Glitch.

I’ve written about being all-in on the Fediverse and I generally try a lot of different things out. I created a Shuttlecraft instance for myself around the same time I set up Postmarks last year – both run on Glitch, both are somewhat experimental / in-progress and unfinished. The fact is that I use my Postmarks instance all the time for logging links of interest, but Shuttlecraft has really just been sitting there without very much interaction. That’s mostly deliberate, it’s a playground more than anything else, and it can be handy for playing with interactions with other ActivityPub servers.

However – yesterday I thought I’d take a quick look at it, only to discover that my Glitch app was down.

After doing some digging in the console and logs, I found that Node was complaining about being unable to load a module. That was surprising to me, as I hadn’t changed anything there for a long while. It turned out that what was actually happening was that the container’s disk allocation had run out, and the log message itself was spurious.

To be fair, the Shuttlecraft README is very clear that a) it’s an unsupported side-project from the author Ben Brown, and b) …

all data is written as PLAIN TEXT FILES to the disk.

Right now, the app builds an IN-MEMORY INDEX of EVERY SINGLE POST. This will work for several thousand posts, but … maybe not for 10,000s of posts. I’m not sure how far it will go. I have ideas about being able to shard the index into multiple files and page through it, etc. But.

It took a bit of very messy and imperfect cleanup inside hidden directories in the Glitch container, but for now, I have my small instance back up again. Realistically, it is probably not worth following / I don’t look at it much / it will fall over again, before much longer – but it’s also a fun thing to tinker with, and the code is quick to tweak in the Glitch editor.

In the past few months, quite a few things have changed in the ecosystem – for example, I’m now on Threads, and my account is federated out from there. Shuttlecraft is missing something in its ability to play nicely with that, which is a bit sad… maybe I’ll have to have a look into it at some stage.

I’ll have to look at some more Fediverse-compatible apps soon, hopefully more resilient ones! 🙂 Fediforum is coming up next month, and that’s usually a great place to learn about what developers are working on across the ActivityPub ecosystem.

Like it? Share it -

• Click to share on Mastodon (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)

https://andypiper.co.uk/2024/08/07/recovering-my-shuttlecraft/

#Blaugust2024 #100DaysToOffload #activitypub #Coding #fediverse #glitch #postmarks #selfHosting #singleUser

When I poked around with Postmarks (a federated bookmarking service) last year, I briefly mentioned another federated server, Shuttlecraft… but I never followed up on that.

Shuttlecraft is a single-user ActivityPub-compatible application that can run on a platform like Glitch – in fact, it’s more-or-less a single-click deployment to fork and install on Glitch.

I’ve written about being all-in on the Fediverse and I generally try a lot of different things out. I created a Shuttlecraft instance for myself around the same time I set up Postmarks last year – both run on Glitch, both are somewhat experimental / in-progress and unfinished. The fact is that I use my Postmarks instance all the time for logging links of interest, but Shuttlecraft has really just been sitting there without very much interaction. That’s mostly deliberate, it’s a playground more than anything else, and it can be handy for playing with interactions with other ActivityPub servers.

However – yesterday I thought I’d take a quick look at it, only to discover that my Glitch app was down.

After doing some digging in the console and logs, I found that Node was complaining about being unable to load a module. That was surprising to me, as I hadn’t changed anything there for a long while. It turned out that what was actually happening was that the container’s disk allocation had run out, and the log message itself was spurious.

To be fair, the Shuttlecraft README is very clear that a) it’s an unsupported side-project from the author Ben Brown, and b) …

all data is written as PLAIN TEXT FILES to the disk.

Right now, the app builds an IN-MEMORY INDEX of EVERY SINGLE POST. This will work for several thousand posts, but … maybe not for 10,000s of posts. I’m not sure how far it will go. I have ideas about being able to shard the index into multiple files and page through it, etc. But.

It took a bit of very messy and imperfect cleanup inside hidden directories in the Glitch container, but for now, I have my small instance back up again. Realistically, it is probably not worth following / I don’t look at it much / it will fall over again, before much longer – but it’s also a fun thing to tinker with, and the code is quick to tweak in the Glitch editor.

In the past few months, quite a few things have changed in the ecosystem – for example, I’m now on Threads, and my account is federated out from there. Shuttlecraft is missing something in its ability to play nicely with that, which is a bit sad… maybe I’ll have to have a look into it at some stage.

I’ll have to look at some more Fediverse-compatible apps soon, hopefully more resilient ones! 🙂 Fediforum is coming up next month, and that’s usually a great place to learn about what developers are working on across the ActivityPub ecosystem.

https://andypiper.co.uk/2024/08/07/recovering-my-shuttlecraft/

#activitypub #Coding #fediverse #glitch #postmarks #selfHosting #singleUser

When I poked around with Postmarks (a federated bookmarking service) last year, I briefly mentioned another federated server, Shuttlecraft… but I never followed up on that.

Shuttlecraft is a single-user ActivityPub-compatible application that can run on a platform like Glitch – in fact, it’s more-or-less a single-click deployment to fork and install on Glitch.

I’ve written about being all-in on the Fediverse and I generally try a lot of different things out. I created a Shuttlecraft instance for myself around the same time I set up Postmarks last year – both run on Glitch, both are somewhat experimental / in-progress and unfinished. The fact is that I use my Postmarks instance all the time for logging links of interest, but Shuttlecraft has really just been sitting there without very much interaction. That’s mostly deliberate, it’s a playground more than anything else, and it can be handy for playing with interactions with other ActivityPub servers.

However – yesterday I thought I’d take a quick look at it, only to discover that my Glitch app was down.

After doing some digging in the console and logs, I found that Node was complaining about being unable to load a module. That was surprising to me, as I hadn’t changed anything there for a long while. It turned out that what was actually happening was that the container’s disk allocation had run out, and the log message itself was spurious.

To be fair, the Shuttlecraft README is very clear that a) it’s an unsupported side-project from the author Ben Brown, and b) …

all data is written as PLAIN TEXT FILES to the disk.

Right now, the app builds an IN-MEMORY INDEX of EVERY SINGLE POST. This will work for several thousand posts, but … maybe not for 10,000s of posts. I’m not sure how far it will go. I have ideas about being able to shard the index into multiple files and page through it, etc. But.

It took a bit of very messy and imperfect cleanup inside hidden directories in the Glitch container, but for now, I have my small instance back up again. Realistically, it is probably not worth following / I don’t look at it much / it will fall over again, before much longer – but it’s also a fun thing to tinker with, and the code is quick to tweak in the Glitch editor.

In the past few months, quite a few things have changed in the ecosystem – for example, I’m now on Threads, and my account is federated out from there. Shuttlecraft is missing something in its ability to play nicely with that, which is a bit sad… maybe I’ll have to have a look into it at some stage.

I’ll have to look at some more Fediverse-compatible apps soon, hopefully more resilient ones! 🙂 Fediforum is coming up next month, and that’s usually a great place to learn about what developers are working on across the ActivityPub ecosystem.

https://andypiper.co.uk/2024/08/07/recovering-my-shuttlecraft/

#activitypub #Coding #fediverse #glitch #postmarks #selfHosting #singleUser

When I poked around with Postmarks (a federated bookmarking service) last year, I briefly mentioned another federated server, Shuttlecraft… but I never followed up on that.

Shuttlecraft is a single-user ActivityPub-compatible application that can run on a platform like Glitch – in fact, it’s more-or-less a single-click deployment to fork and install on Glitch.

I’ve written about being all-in on the Fediverse and I generally try a lot of different things out. I created a Shuttlecraft instance for myself around the same time I set up Postmarks last year – both run on Glitch, both are somewhat experimental / in-progress and unfinished. The fact is that I use my Postmarks instance all the time for logging links of interest, but Shuttlecraft has really just been sitting there without very much interaction. That’s mostly deliberate, it’s a playground more than anything else, and it can be handy for playing with interactions with other ActivityPub servers.

However – yesterday I thought I’d take a quick look at it, only to discover that my Glitch app was down.

After doing some digging in the console and logs, I found that Node was complaining about being unable to load a module. That was surprising to me, as I hadn’t changed anything there for a long while. It turned out that what was actually happening was that the container’s disk allocation had run out, and the log message itself was spurious.

To be fair, the Shuttlecraft README is very clear that a) it’s an unsupported side-project from the author Ben Brown, and b) …

all data is written as PLAIN TEXT FILES to the disk.

Right now, the app builds an IN-MEMORY INDEX of EVERY SINGLE POST. This will work for several thousand posts, but … maybe not for 10,000s of posts. I’m not sure how far it will go. I have ideas about being able to shard the index into multiple files and page through it, etc. But.

It took a bit of very messy and imperfect cleanup inside hidden directories in the Glitch container, but for now, I have my small instance back up again. Realistically, it is probably not worth following / I don’t look at it much / it will fall over again, before much longer – but it’s also a fun thing to tinker with, and the code is quick to tweak in the Glitch editor.

In the past few months, quite a few things have changed in the ecosystem – for example, I’m now on Threads, and my account is federated out from there. Shuttlecraft is missing something in its ability to play nicely with that, which is a bit sad… maybe I’ll have to have a look into it at some stage.

I’ll have to look at some more Fediverse-compatible apps soon, hopefully more resilient ones! 🙂 Fediforum is coming up next month, and that’s usually a great place to learn about what developers are working on across the ActivityPub ecosystem.

Like it? Share it -

• Click to share on Mastodon (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)

https://andypiper.co.uk/2024/08/07/recovering-my-shuttlecraft/

#Blaugust2024 #100DaysToOffload #activitypub #Coding #fediverse #glitch #postmarks #selfHosting #singleUser

Tip for #singleuser or small instance users:
The biggest disadvantage of small instances is the dead federated timeline. Instance admins can subscribe to the classic #relays, but this comes at a high price such as high resource usage and too much noise, depending on the relay. It's either all or nothing.

Instead you can populate your federated timeline by following the #FediBuzz relays. They can be followed as normal users and boost posts based on the hashtag, instance or even language.
Here are a few examples:
@tag-fediverse (boosts the #fediverse hashtag from all instances)
@instance-jasdemi.com (boosts everything from my instance, jasdemi.com)
@language-it (boosts only posts in Italian language from all instances)

Now before you follow any relays, I suggest creating an alt account as this will make you home timeline very noisy. With your main account you can now check out the federated timeline or follow hashtags.
More info here: https://relay.fedi.buzz/

#fediadmin #gotosocial #sharkey #mastodon #feditip #selfhosted

Tip for #singleuser or small instance users:
The biggest disadvantage of small instances is the dead federated timeline. Instance admins can subscribe to the classic #relays, but this comes at a high price such as high resource usage and too much noise, depending on the relay. It's either all or nothing.

Instead you can populate your federated timeline by following the #FediBuzz relays. They can be followed as normal users and boost posts based on the hashtag, instance or even language.
Here are a few examples:
@tag-fediverse (boosts the #fediverse hashtag from all instances)
@instance-jasdemi.com (boosts everything from my instance, jasdemi.com)
@language-it (boosts only posts in Italian language from all instances)

Now before you follow any relays, I suggest creating an alt account as this will make you home timeline very noisy. With your main account you can now check out the federated timeline or follow hashtags.
More info here: https://relay.fedi.buzz/

#fediadmin #gotosocial #sharkey #mastodon #feditip #selfhosted

Tip for #singleuser or small instance users:
The biggest disadvantage of small instances is the dead federated timeline. Instance admins can subscribe to the classic #relays, but this comes at a high price such as high resource usage and too much noise, depending on the relay. It's either all or nothing.

Instead you can populate your federated timeline by following the #FediBuzz relays. They can be followed as normal users and boost posts based on the hashtag, instance or even language.
Here are a few examples:
@tag-fediverse (boosts the #fediverse hashtag from all instances)
@instance-jasdemi.com (boosts everything from my instance, jasdemi.com)
@language-it (boosts only posts in Italian language from all instances)

Now before you follow any relays, I suggest creating an alt account as this will make you home timeline very noisy. With your main account you can now check out the federated timeline or follow hashtags.
More info here: https://relay.fedi.buzz/

#fediadmin #gotosocial #sharkey #mastodon #feditip #selfhosted

Tip for #singleuser or small instance users:
The biggest disadvantage of small instances is the dead federated timeline. Instance admins can subscribe to the classic #relays, but this comes at a high price such as high resource usage and too much noise, depending on the relay. It's either all or nothing.

Instead you can populate your federated timeline by following the #FediBuzz relays. They can be followed as normal users and boost posts based on the hashtag, instance or even language.
Here are a few examples:
@tag-fediverse (boosts the #fediverse hashtag from all instances)
@instance-jasdemi.com (boosts everything from my instance, jasdemi.com)
@language-it (boosts only posts in Italian language from all instances)

Now before you follow any relays, I suggest creating an alt account as this will make you home timeline very noisy. With your main account you can now check out the federated timeline or follow hashtags.
More info here: https://relay.fedi.buzz/

#fediadmin #gotosocial #sharkey #mastodon #feditip #selfhosted

Tip for #singleuser or small instance users:
The biggest disadvantage of small instances is the dead federated timeline. Instance admins can subscribe to the classic #relays, but this comes at a high price such as high resource usage and too much noise, depending on the relay. It's either all or nothing.

Instead you can populate your federated timeline by following the #FediBuzz relays. They can be followed as normal users and boost posts based on the hashtag, instance or even language.
Here are a few examples:
@tag-fediverse (boosts the #fediverse hashtag from all instances)
@instance-jasdemi.com (boosts everything from my instance, jasdemi.com)
@language-it (boosts only posts in Italian language from all instances)

Now before you follow any relays, I suggest creating an alt account as this will make you home timeline very noisy. With your main account you can now check out the federated timeline or follow hashtags.
More info here: https://relay.fedi.buzz/

#fediadmin #gotosocial #sharkey #mastodon #feditip #selfhosted

For #selfhosted #singleuser #mastodonadmin folks:

If you were to start over again fresh in 2025, what would be your preferred #Fediverse alternative stack or project instead of #Mastodon?

Asking for a friend. ( #itme )

For #selfhosted #singleuser #mastodonadmin folks:

If you were to start over again fresh in 2025, what would be your preferred #Fediverse alternative stack or project instead of #Mastodon?

Asking for a friend. ( #itme )

For #selfhosted #singleuser #mastodonadmin folks:

If you were to start over again fresh in 2025, what would be your preferred #Fediverse alternative stack or project instead of #Mastodon?

Asking for a friend. ( #itme )

For #selfhosted #singleuser #mastodonadmin folks:

If you were to start over again fresh in 2025, what would be your preferred #Fediverse alternative stack or project instead of #Mastodon?

Asking for a friend. ( #itme )

For #selfhosted #singleuser #mastodonadmin folks:

If you were to start over again fresh in 2025, what would be your preferred #Fediverse alternative stack or project instead of #Mastodon?

Asking for a friend. ( #itme )

5 months into self-hosting my single-user instance, and I have zero complaints. The cost comes up to $6usd/mo. (~$8 cad, atm), and there’s headroom to spare. I’m running Akkoma on Fedora (which I thought was 38 but is actually 37 so I guess I should probably update it).

This is on a Vultr “Cloud Compute” server, with the “AMD High Performance” option (EPYC CPU + NVMe storage) on the lowest tier: 1 vCPU, 1GB memory, and 25GB storage. As an irritable person who hates waiting for things to load, it’s performed beautifully.

I can’t comment on Mastodon. While I’m told it’s a bit of a resource hog, especially as it scales, it might be perfectly fine for a single user instance, although when I was first considering self-hosting, I was advised that I’d be better off spending $15 or $20 minimum on a more capable server for Mastodon. I can’t refute or confirm that statement, so use your own judgement, but I don’t really like the way the Mastodon project is run, and I like being able to use Markdown, even if barely anybody will see it.

#selfhost #selfhosting #singleuser #singleuserinstance #akkoma #fediverse #hashtag #octothorpe

5 months into self-hosting my single-user instance, and I have zero complaints. The cost comes up to $6usd/mo. (~$8 cad, atm), and there’s headroom to spare. I’m running Akkoma on Fedora (which I thought was 38 but is actually 37 so I guess I should probably update it).

This is on a Vultr “Cloud Compute” server, with the “AMD High Performance” option (EPYC CPU + NVMe storage) on the lowest tier: 1 vCPU, 1GB memory, and 25GB storage. As an irritable person who hates waiting for things to load, it’s performed beautifully.

I can’t comment on Mastodon. While I’m told it’s a bit of a resource hog, especially as it scales, it might be perfectly fine for a single user instance, although when I was first considering self-hosting, I was advised that I’d be better off spending $15 or $20 minimum on a more capable server for Mastodon. I can’t refute or confirm that statement, so use your own judgement, but I don’t really like the way the Mastodon project is run, and I like being able to use Markdown, even if barely anybody will see it.

#selfhost #selfhosting #singleuser #singleuserinstance #akkoma #fediverse #hashtag #octothorpe

5 months into self-hosting my single-user instance, and I have zero complaints. The cost comes up to $6usd/mo. (~$8 cad, atm), and there’s headroom to spare. I’m running Akkoma on Fedora (which I thought was 38 but is actually 37 so I guess I should probably update it).

This is on a Vultr “Cloud Compute” server, with the “AMD High Performance” option (EPYC CPU + NVMe storage) on the lowest tier: 1 vCPU, 1GB memory, and 25GB storage. As an irritable person who hates waiting for things to load, it’s performed beautifully.

I can’t comment on Mastodon. While I’m told it’s a bit of a resource hog, especially as it scales, it might be perfectly fine for a single user instance, although when I was first considering self-hosting, I was advised that I’d be better off spending $15 or $20 minimum on a more capable server for Mastodon. I can’t refute or confirm that statement, so use your own judgement, but I don’t really like the way the Mastodon project is run, and I like being able to use Markdown, even if barely anybody will see it.

#selfhost #selfhosting #singleuser #singleuserinstance #akkoma #fediverse #hashtag #octothorpe

5 months into self-hosting my single-user instance, and I have zero complaints. The cost comes up to $6usd/mo. (~$8 cad, atm), and there’s headroom to spare. I’m running Akkoma on Fedora (which I thought was 38 but is actually 37 so I guess I should probably update it).

This is on a Vultr “Cloud Compute” server, with the “AMD High Performance” option (EPYC CPU + NVMe storage) on the lowest tier: 1 vCPU, 1GB memory, and 25GB storage. As an irritable person who hates waiting for things to load, it’s performed beautifully.

I can’t comment on Mastodon. While I’m told it’s a bit of a resource hog, especially as it scales, it might be perfectly fine for a single user instance, although when I was first considering self-hosting, I was advised that I’d be better off spending $15 or $20 minimum on a more capable server for Mastodon. I can’t refute or confirm that statement, so use your own judgement, but I don’t really like the way the Mastodon project is run, and I like being able to use Markdown, even if barely anybody will see it.

#selfhost #selfhosting #singleuser #singleuserinstance #akkoma #fediverse #hashtag #octothorpe

5 months into self-hosting my single-user instance, and I have zero complaints. The cost comes up to $6usd/mo. (~$8 cad, atm), and there’s headroom to spare. I’m running Akkoma on Fedora (which I thought was 38 but is actually 37 so I guess I should probably update it).

This is on a Vultr “Cloud Compute” server, with the “AMD High Performance” option (EPYC CPU + NVMe storage) on the lowest tier: 1 vCPU, 1GB memory, and 25GB storage. As an irritable person who hates waiting for things to load, it’s performed beautifully.

I can’t comment on Mastodon. While I’m told it’s a bit of a resource hog, especially as it scales, it might be perfectly fine for a single user instance, although when I was first considering self-hosting, I was advised that I’d be better off spending $15 or $20 minimum on a more capable server for Mastodon. I can’t refute or confirm that statement, so use your own judgement, but I don’t really like the way the Mastodon project is run, and I like being able to use Markdown, even if barely anybody will see it.

#selfhost #selfhosting #singleuser #singleuserinstance #akkoma #fediverse #hashtag #octothorpe

In comparison to #mastodon, running a #selfhosted #singleuser instance on #peertube and #pixelfed is a bit more wild west in terms of finding stuff. Peertube feels like public-access programming, but I'm certain there's something interesting out there. On PixelFed I'm struggling to find content I can connect with versus just looking at mastodon.art. All three are great ways to store my own personal content, so I'm still #happy with them. I just need to spend more time on them. I'm having #fun

In comparison to #mastodon, running a #selfhosted #singleuser instance on #peertube and #pixelfed is a bit more wild west in terms of finding stuff. Peertube feels like public-access programming, but I'm certain there's something interesting out there. On PixelFed I'm struggling to find content I can connect with versus just looking at mastodon.art. All three are great ways to store my own personal content, so I'm still #happy with them. I just need to spend more time on them. I'm having #fun

@adlerweb ich halte das für naiv (anders als Blockaden von :activitypub: - Instanzen, denn #Threads wird wie ein dauerhafter #DDoS-Angriff alles (außer vielleicht wenige #SingleUser-Instanzen) lahmlegen.

Das ist genauso wie #eMail - Server aufsetzen und keinerlei #Blocklist alla #Spamhaus nutzen...

@adlerweb ich halte das für naiv (anders als Blockaden von :activitypub: - Instanzen, denn #Threads wird wie ein dauerhafter #DDoS-Angriff alles (außer vielleicht wenige #SingleUser-Instanzen) lahmlegen.

Das ist genauso wie #eMail - Server aufsetzen und keinerlei #Blocklist alla #Spamhaus nutzen...

@adlerweb ich halte das für naiv (anders als Blockaden von :activitypub: - Instanzen, denn #Threads wird wie ein dauerhafter #DDoS-Angriff alles (außer vielleicht wenige #SingleUser-Instanzen) lahmlegen.

Das ist genauso wie #eMail - Server aufsetzen und keinerlei #Blocklist alla #Spamhaus nutzen...

any other single-user instances who’ve enabled authorized fetch having any visible problems with interacting on the fedi? I have not noticed any but I fear I might not be able to tell.

#authorizedFetch #singleUser

any other single-user instances who’ve enabled authorized fetch having any visible problems with interacting on the fedi? I have not noticed any but I fear I might not be able to tell.

#authorizedFetch #singleUser

any other single-user instances who’ve enabled authorized fetch having any visible problems with interacting on the fedi? I have not noticed any but I fear I might not be able to tell.

#authorizedFetch #singleUser

any other single-user instances who’ve enabled authorized fetch having any visible problems with interacting on the fedi? I have not noticed any but I fear I might not be able to tell.

#authorizedFetch #singleUser

any other single-user instances who’ve enabled authorized fetch having any visible problems with interacting on the fedi? I have not noticed any but I fear I might not be able to tell.

#authorizedFetch #singleUser