jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Site description
These are the voyag... uh, things I post about.
Admin email
jrollans@gmail.com
Admin account
@jrollans@jrollans.com

Search results for tag #mastoadmin

[?]Larvitz :fedora: :redhat: » 🌐
@Larvitz@burningboard.net

Did quite some maintenance on burningboard.net Mastodon instance today ..

Updated servers and jails to FreeBSD 15.0-RELEASE-p5 :freebsd:

1.
proxy_cache_path (S3 media cache) was already on a ZFS dataset with autosnapshot disabled .. But proxy_temp_path and client_body_temp_path (both nginx temp folders) weren't. Leading to extremely bloated daily ZFS snapshots for the Nginx jail. Changed those and cleaned old snapshots -> 31GB reclaimed space

2.
Cleaned up Database Snapshots and did a pg_repack on prod to reclaim deleted database pages -> 3GB reclaimed space

3.
Fixed issue with backend path over gif tunnel to Elasticsearch (6in6). Turned out to be a MSS issue (clamp-mss to 1140 on the tunnel iface solved it!)

4.
Fixed IPv6 routing issue for Prometheus Monitoring after reboot (rc.d static_routes != ipv6_static_routes)

All in all, our instance is in very good shape again :-)

@tux

    [?]Larvitz :fedora: :redhat: » 🌐
    @Larvitz@burningboard.net

    @tux Running a pretty reasonable stack now ...

    FreeBSD 15.0-RELEASE-p5
    Mastodon 4.5.8
    PostgreSQL 18.3
    Valkey 9.0.1
    Opensearch (fork of Elastic) 3.2.0

    28,4 GB PostgreSQL Database size
    162 GB Media Files
    4,88 GB Search Index size

      AodeRelay boosted

      [?]💜💙💚💛🧡❤️ vanta rainbow black ❤️🧡💛💚💙💜 » 🌐
      @vantablack@cyberpunk.lol

      LMAO some AI company sent us a takedown request but that's not how trademarks work lmao??? you can't just send those out willy nilly because somebody said something you don't like

      here's the email and attachments they sent xD

      if this happens to any other fedi admins, just in case it wasn't clear, this can be safely ignored

      it was from doppel.com

      Takedown Request - hxxp[://]cyberpunk[.]lol/[at]dirtwizard666/116405761408095582

Name: Doppel SOC Team
Infringing Site: cyberpunk.lol/@dirtwizard666/116405761408095582
 Domain IP Address: 91.132.147.113
Other related infringing sites: cyberpunk.lol/@dirtwizard666/116405761408095582

The infringing site is using trademark A16Z without authorization. This unauthorized use of their trademark may cause customer confusion / harm.

We kindly request the immediate removal of the infringing site and ensure the user refrains from infringing the mark in the future.

Thank you for your assistance in advance.


Kind Regards,

Doppel Security Operations Center

E: takedowns@doppel.com | W: doppel.com


If we have contacted you incorrectly, please respond back to this email.


If you would like us to report to a different address, please reach out to us at provider-relations@doppel.com.


Authority to Act: We, Doppel, confirm that the information in this notice is accurate and assert, under penalty of perjury, that we are authorized to act on behalf of AH Capital Management, L.L.C. as their authorized agent.
--
*The content of this email is confidential and intended for the recipient
specified in the message only. It is strictly forbidden to share any part
of this message with any third party, without consent of the sender. If you
received this message by mistake, please reply to this message and follow
with its deletion, so that we can ensure such a mistake does not occur in
the future.

      Alt...Takedown Request - hxxp[://]cyberpunk[.]lol/[at]dirtwizard666/116405761408095582 Name: Doppel SOC Team Infringing Site: cyberpunk.lol/@dirtwizard666/116405761408095582 Domain IP Address: 91.132.147.113 Other related infringing sites: cyberpunk.lol/@dirtwizard666/116405761408095582 The infringing site is using trademark A16Z without authorization. This unauthorized use of their trademark may cause customer confusion / harm. We kindly request the immediate removal of the infringing site and ensure the user refrains from infringing the mark in the future. Thank you for your assistance in advance. Kind Regards, Doppel Security Operations Center E: takedowns@doppel.com | W: doppel.com If we have contacted you incorrectly, please respond back to this email. If you would like us to report to a different address, please reach out to us at provider-relations@doppel.com. Authority to Act: We, Doppel, confirm that the information in this notice is accurate and assert, under penalty of perjury, that we are authorized to act on behalf of AH Capital Management, L.L.C. as their authorized agent. -- *The content of this email is confidential and intended for the recipient specified in the message only. It is strictly forbidden to share any part of this message with any third party, without consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

      screnshot of an average dirtwizard post

      Alt...screnshot of an average dirtwizard post

      patent pdf thingy

      Alt...patent pdf thingy

      https://www.doppel.com/ homepage

      Alt...https://www.doppel.com/ homepage

        [?]Michael » 🌐
        @michael@mstdn.thms.uk

        @mastodonlgbt@mastodon.lgbt @alxhu Just so you know: When they released the trademark policy they made statements saying that they would permit instances that use the mastodon name in good faith and predated the policy.

        I'm not aware of a change of that position since.

        My own instance use mstdn in the url (IIRC also covered by the trademark) and based on this statement I am keeping my instance up.

        May @andypiper can advise?

          fedicat boosted

          [?]Jeff » 🌐
          @box464@mastodon.social

          Updated my test mastodon instance to 4.5.9, no issues (so far).

          github.com/mastodon/mastodon/r

            [?]Ian Littman » 🌐
            @ian@phpc.social

            phpc.social is now running on Mastodon 4.5.9, released ~5.5 hours ago.

              [?]Exquisite.social » 🌐
              @exquisite@exquisite.social

              Maintenance :flan_hacker:

              Upgrading to Mastodon v4.5.9 - might have an intermittent reboot shortly. Sorry about the inconvenience and thank you for bearing with us as always.

                [?]Exquisite.social » 🌐
                @exquisite@exquisite.social

                ## Maintenance :flan_hacker:

                Upgrading to Mastodon `v4.5.9` - might have an intermittent reboot shortly. Sorry about the inconvenience and thank you for bearing with us as always.

                  [?]Watzmann » 🌐
                  @watzmann@watzmann.social

                  [?]Larvitz :fedora: :redhat: » 🌐
                  @Larvitz@burningboard.net

                  RE: mastodon.social/@MastodonEngin

                  Burningboard.net was successfully updated to Mastodon v4.5.9 🙂 No issues.

                  fedicat boosted

                  [?]Mastodon Engineering » 🌐
                  @MastodonEngineering@mastodon.social

                  We just released Mastodon 4.5.9, 4.4.16, and 4.3.22.

                  These versions contain various bug fixes, including important security fixes.

                  Full release notes and update instructions are available on the GitHub releases page.

                  github.com/mastodon/mastodon/r

                      fedicat boosted

                      [?]Mastodon Engineering » 🌐
                      @MastodonEngineering@mastodon.social

                      We just released Mastodon 4.5.9, 4.4.16, and 4.3.22.

                      These versions contain various bug fixes, including important security fixes.

                      Full release notes and update instructions are available on the GitHub releases page.

                      github.com/mastodon/mastodon/r

                        [?]Adhidarma Hadiwinoto :verify: » 🌐
                        @adhisimon@mastodon.kodesumber.com

                        Mastodon has release new patches for 4.5, 4.4, and 4.3:

                        - 4.5.9
                        - 4.4.16
                        - 4.3.22

                        You can follow my bot @mstdn_release_watcher to get information when mastodon has release a new version.

                          [?]Mastodon Release Watcher » 🤖 🌐
                          @mstdn_release_watcher@mastodon.kodesumber.com

                          "There is a new release of mastodon. Happy updating your instance."

                          v4.5.9

                          Upgrade overview This release contains upgrade notes that deviate from the norm: ℹ️ Requires assets recompilation For more information, view the complete release notes and scroll down to the upgrade instructions...

                          github.com/mastodon/mastodon/r

                            [?]Cadu :hiddenDisability: [o/ele/-e] » 🌐
                            @cadusilva@bolha.one

                            RE: bolha.one/@cadusilva/116409509

                            The fediverse is hosted in Germany and it shows. At least from our perspective, being a server phisically located in Brazil with a lusophone audience.

                            But most of the requests are from german (anonymized) IPs, because most of the federation is hosted there. The statistics are from Bunny CDN.

                            São Paulo comes in second because it's closer to our users or the peering/routing is better. I live closer to Fortaleza, but I end up being routed to São Paulo anyway.

                            It's nice that the fediverse isn't US-based for a change, but concetrating in a single european country is not so good either.

                              [?]*|FNAME|*:canada: [they/them/their] » 🌐
                              @crispius@mstdn.fname.ca

                              So I have a weird problem with my Masotdon/Glitchsoc instance: when I log in from my PC I get the ‘Something went wrong on our end’ pachyderm smashing on keyboard error. I’ve tried a clean install (of the client system), Firefox, Edge, Chrome. Client access through Ivory is unaffected as is accessing it with Safari on my iPad. I’ve tried regenerating my secrets keys. Re-running the database migration. No joy. It’s a single-user instance running with .

                                fedicat boosted

                                [?]Ryan Wild » 🌐
                                @wild1145@mastodonapp.uk

                                We're adding mastodon.cloud to our list due to the instance seemingly being abandoned with open signups and zero moderation. The burden of us suspending accounts locally is not practical when the instance is out of date and not being maintained.

                                It's been flagged since August last year - social.growyourown.services/@F so I don't see it likely that anything is suddenly going to change.

                                  [?]Ashwin Dixit » 🌐
                                  @purrperl@noc.social

                                  Dear @admin ( noc.social ),

                                  Here we are again. I am sensing something non-kosher.

                                  It has been weeks, that I have been trying to reach you and have not heard back.

                                  Please send me a password reset email, as I have forgotten my password.

                                  Please respond, and have a nice day!

                                  Thanks,




                                    [?]Leafy, Kylie, Skye 🏳️‍🌈🏳️‍⚧️ » 🌐
                                    @alxhu@greifswald.lgbt

                                    fedicat boosted

                                    [?]Mastodon Engineering » 🌐
                                    @MastodonEngineering@mastodon.social

                                    Trunk & Tidbits for March is out - our monthly engineering news, featuring current releases, the profiles redesign, Collections, additional FEPs implemented - lots of work in motion.

                                    blog.joinmastodon.org/2026/04/

                                      fedicat boosted

                                      [?]Roni Rolle Laukkarinen » 🌐
                                      @rolle@mementomori.social

                                      Support for the new profile design is almost ready for Mastodon Bird UI v4.0.0-alpha.6 (for Mastodon nightly 4.6.0-alpha.6).

                                      Original core Mastodon on the left.
                                      With Mastodon Bird UI on the right.

                                      Mastodon default profile for v4.6.0, screenshot

                                      Alt...Mastodon default profile for v4.6.0, screenshot

                                      Mastodon Bird UI profile for v4.6.0, screenshot

                                      Alt...Mastodon Bird UI profile for v4.6.0, screenshot

                                        fedicat boosted

                                        [?]Ryan Wild » 🌐
                                        @wild1145@mastodonapp.uk

                                        The Universeodon relay is now back up and running and migrated to our new environment.

                                        I'll keep an eye for a little longer just to make sure everything continues to work as expected but it should be fine as far as I can see.

                                          AodeRelay boosted

                                          [?]Ryan Wild » 🌐
                                          @wild1145@mastodonapp.uk

                                          Just as a quick note for the community - The Universeodon relay is about to be migrated to new infrastructure.

                                          I'm expecting there to be a short blip where the relay will be down while I move the config and DB from the relay to the new server and switch our load balancer to use the new server.

                                          This will then be the final item on our legacy server cluster that needs migrating (Which is frankly long overdue!)