home.social

#single-user — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #single-user, aggregated by home.social.

fetched live
  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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 -

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

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

  10. 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 -

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

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

  11. 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

  12. 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

  13. 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 )

  14. 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 )

  15. 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

  16. @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...

  17. 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

  18. @[email protected] @fedidevs @fedidevs

    What underlying infra are you looking at building this upon - #Gofed, #Streams, #Bovine?

    Perhaps a small, uber portable #POSIX compliant ANSI C single-user system built on top something like #Snacs2?

    And what are your possible solutions of mind for those who already self-host their own #Fediverse accounts? Should they have to rent another #VPS or create yet another hostname for additional servers, A RRs, and AAAA RRs, at their homes for each #bot?

    I'm not seeing the utility here. Maybe explaining it a bit differently so the net #simplification of doing it that way is clear?

    I dunno, it just seems kind of a lot of redundancy in creating all those #storage, #CPU, and #RAM stacks.

    All the wonderful #single user Fediverse platforms currently in popular use notwithstanding, it might be more economically viable and #greener to just take a family of five and their three bots and just put them all on the single instance of whatever Fediverse platform on their own Raspberry Pi... maybe?

    Interesting idea Gabe, but I'm having trouble seeing how this is simpler or better than the current methods of just self-hosted forks of #Pleroma, #Misskey, and other lightweight platforms that would seem to make it so much easier already 🙂

    #tallship #FOSS #ActivityPub #Fediverse #SocialHub SocialHub.ActivityPub.Rocks



    .♲ social.gabekangas.com/objects/…
  19. I'm announcing a new Verified policy on my platform.

    I'm offering members to get a big triple-double blue icon to symbolize their importance.

    They'll have to pay me for this.

    Payment will be required in ice-cream. One small tub per month.

    #singleuser #selfhost #Selfhosting

  20. I'm announcing a new Verified policy on my platform.

    I'm offering members to get a big triple-double blue icon to symbolize their importance.

    They'll have to pay me for this.

    Payment will be required in ice-cream. One small tub per month.

    #singleuser #selfhost #Selfhosting

  21. Happy 1 month anniversary to my single user instance! Since I connected to a couple of #relays and worked out the kinks with #sidekiq, it's been humming along.

    The handy part of it being a physical box in my living room is that I hear the fan going off whenever something is chugging. 😉

    #mastoadmin #singleuser

  22. It became extremely apparent that 1GB of RAM wasn’t cutting it for even a #SingleUserInstance. Slow response times and time-outs on gathering replies, etc. So upped my server to 2GB and so far it’s a lot zippier.

    #mastoAdmin #mastodonAdmin #mastodon #singleUser

  23. It became extremely apparent that 1GB of RAM wasn’t cutting it for even a #SingleUserInstance. Slow response times and time-outs on gathering replies, etc. So upped my server to 2GB and so far it’s a lot zippier.

    #mastoAdmin #mastodonAdmin #mastodon #singleUser

  24. @troyhunt @haveibeenpwned

    This is a siutation where domain-related #singleuser instances make sense.

    The verification process is much more straightforward if you set up something like

    [email protected]

    with the verification link back to the site

    That way, we'd have a quick look at the profile, see the link back to the site and go, oh, ok, its' good.

    I think we will get there with a lot of brands/initiatives/software/platforms

  25. Really enjoying being on my own instance. It cuts the noise A LOT. #Mastodon #SingleUser

  26. Really enjoying being on my own instance. It cuts the noise A LOT. #Mastodon #SingleUser

  27. CW: Let's try to kick around the concept of "sample size".
    The ubiquity of posts characterizing Mastodon vs #Pleroma almost totally abitrarily is making me nuts. It's like people are going around one floor of a college dorm, seeing who's using Windows vs Mac, and determing that the rich kids are "artsy" and own Macs ergo mostly artists use Mac.

    Just one major variable to consider is how many #singleUser Pleroma instances are there vs Mastodon? They're almost certainly #selfHosting, they made their platform choice based on which makes the most sense to maintain technically as well as financially.

    So now we're talking about many individuals vs even more communities, any generalization is going to be absurdly inaccurate.
  28. Okay, #Calckey is fucking awesome, so this is the last server I'll set up for a #fediverse #SingleUser instance. I'll be messing with a #Matrix server next. But I promise this is my last #fediverse account!

  29. Here’s another case of why I’m building Tusk (as I’ve come to call it):

    From @simon :
    “My least favourite sharp edge of Mastodon is the fact that when you view someone else's post you only see replies to it that are known to your server - so there's actually a good chance there will be replies that are completely invisible to you, especially if you run your own instance”

    #MastAdmin #SingleUser #discoverability

    fedi.simonwillison.net/@simon/

  30. @EndlessMason I 100% agree. I love seeing #singleuser instances, and particularly the hard work from #relay owners who are supporting them.

  31. @EndlessMason I 100% agree. I love seeing #singleuser instances, and particularly the hard work from #relay owners who are supporting them.

  32. Can't sleep, so I'm working on setting up a #SingleUser #Akkoma instance. Having a couple of cheap domain names is handy.

  33. Update on my #Mastodon #Discoverability project for #SingleUser instances:

    It has a name: Tusk (because it sits in front of a mastodon).

    I can search for users, hashtags, and statuses across all known mastodon 4.0.x instances.

    It does not yet allow interaction with remote statuses or users.

    It still needs installation instructions so people who are not me can figure out how to install it.

  34. Starting a couple of experiments with my #selfhosted #singleuser #mastodon instance...

    Firstly @TrendingBot aggregates trending links across known peer instances and posts new trending links... a new #trending link is "a top ten link that hasn't been seen before"... It runs hourly

    Secondly, I'm looking for the top 10 most popular #hashtags across known instances and streaming these into the #federated timeline

  35. #introduction
    Hello! I've been around on #Mastodon for a bit, but wanted to mess with a #SingleUser #instance, so here it is! I'm normally at alt.mstdon.com/@skroobler, which is a great instance run by @marie

  36. I'm trying out the Mastodon.py API library to process data from #mastodon servers using #python

    It seems quite easy with that to access info from your own account (needs authentication) and public info from other servers (no authentication needed)

    Maybe I will try to make a script to bring more posts with interesting #hashtags from other servers to my #SingleUser server's federated feed

    Link: github.com/halcy/Mastodon.py

  37. CW: Searching for self-hosted ActivityPub single-user blog software
    Anybody have first-hand accounts of self-hosted #activitypub single-user #blog software? I'm quickly running out of options that aren't just write my own...

    Aiming for a git-backed markdown-based static site generator with AP support.

    Tried #writefreely and was mostly impressed but annoyed by the subscription-only additions (comments, media/images, etc.)

    Tried #plume and was disappointed it was not suited for single-user and also put off by how premature it was.

    Do not want to touch #wordpress with the AP plugin

    WAT DO?!

    #fediverse #interoperability #blogging #recommendation #selfhosted #singleuser #opensource
  38. I just updated my #SingleUser instance to 4.0.2. Things seem to be working... I think I'm getting the hang of this!

    #MastoAdmin