home.social

#glitchsoc — Public Fediverse posts

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

  1. @_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.

  2. @_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.

  3. @_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.

  4. @_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.

  5. @_elena Hello fellow #YunoHost person. Yes I love yunohost and serve #glitchsoc here as well as some other apps.

  6. :boost_ok: We'd like to move to fosstodon.org (or any other #FLOSS-centric Instance; preferably with #GlitchSoc support for #MarkDown)…

    - Anyone willing to do a recommendation / offer an invite?

    #OS1337 #Fediverse #Migration #PleaseBoost

  7. :boost_ok: We'd like to move to fosstodon.org (or any other #FLOSS-centric Instance; preferably with #GlitchSoc support for #MarkDown)…

    - Anyone willing to do a recommendation / offer an invite?

    #OS1337 #Fediverse #Migration #PleaseBoost

  8. :boost_ok: We'd like to move to fosstodon.org (or any other #FLOSS-centric Instance; preferably with #GlitchSoc support for #MarkDown)…

    - Anyone willing to do a recommendation / offer an invite?

    #OS1337 #Fediverse #Migration #PleaseBoost

  9. :boost_ok: We'd like to move to fosstodon.org (or any other #FLOSS-centric Instance; preferably with #GlitchSoc support for #MarkDown)…

    - Anyone willing to do a recommendation / offer an invite?

    #OS1337 #Fediverse #Migration #PleaseBoost

  10. I think I'm going to play with followed hash tags on glitchsoc as I've never really given the mastodon / glitchsoc sites a chance until now. It will be a fun adventure I looking forward to. Let's go!

    #mastodon #glitchsoc #fediverse

  11. I think I'm going to play with followed hash tags on glitchsoc as I've never really given the mastodon / glitchsoc sites a chance until now. It will be a fun adventure I looking forward to. Let's go!

    #mastodon #glitchsoc #fediverse

  12. I think I'm going to play with followed hash tags on glitchsoc as I've never really given the mastodon / glitchsoc sites a chance until now. It will be a fun adventure I looking forward to. Let's go!

    #mastodon #glitchsoc #fediverse

  13. I think I'm going to play with followed hash tags on glitchsoc as I've never really given the mastodon / glitchsoc sites a chance until now. It will be a fun adventure I looking forward to. Let's go!

    #mastodon #glitchsoc #fediverse

  14. I think I'm going to play with followed hash tags on glitchsoc as I've never really given the mastodon / glitchsoc sites a chance until now. It will be a fun adventure I looking forward to. Let's go!

    #mastodon #glitchsoc #fediverse

  15. I switched my instance to glitch-soc.

    It now supports:

    • Markdown formatting
    • Longer posts (5000 chars)

    Docs: glitch-soc.github.io/docs

    #GlitchSoc #Mastodon #Fediverse

  16. I switched my instance to glitch-soc.

    It now supports:

    • Markdown formatting
    • Longer posts (5000 chars)

    Docs: glitch-soc.github.io/docs

    #GlitchSoc #Mastodon #Fediverse

  17. I switched my instance to glitch-soc.

    It now supports:

    • Markdown formatting
    • Longer posts (5000 chars)

    Docs: glitch-soc.github.io/docs

    #GlitchSoc #Mastodon #Fediverse

  18. I switched my instance to glitch-soc.

    It now supports:

    • Markdown formatting
    • Longer posts (5000 chars)

    Docs: glitch-soc.github.io/docs

    #GlitchSoc #Mastodon #Fediverse

  19. so, #Glitchsoc has something mastodon does not, in the main glitch website you get, you have a thread mode. I'm still learning how to use it. I will be researching how this works. This is a new fresh reinstall from when ever I got this one up and running, I think 2 weeks ago.

  20. so, #Glitchsoc has something mastodon does not, in the main glitch website you get, you have a thread mode. I'm still learning how to use it. I will be researching how this works. This is a new fresh reinstall from when ever I got this one up and running, I think 2 weeks ago.

  21. so, #Glitchsoc has something mastodon does not, in the main glitch website you get, you have a thread mode. I'm still learning how to use it. I will be researching how this works. This is a new fresh reinstall from when ever I got this one up and running, I think 2 weeks ago.

  22. so, #Glitchsoc has something mastodon does not, in the main glitch website you get, you have a thread mode. I'm still learning how to use it. I will be researching how this works. This is a new fresh reinstall from when ever I got this one up and running, I think 2 weeks ago.

  23. so, #Glitchsoc has something mastodon does not, in the main glitch website you get, you have a thread mode. I'm still learning how to use it. I will be researching how this works. This is a new fresh reinstall from when ever I got this one up and running, I think 2 weeks ago.

  24. so, for those who want to know what happened and why I was offline for about 2 months here's the shortened version.
    On April 13, I attempted to upgrade my #GlitchSoc instance. The upgrade itself appeared to complete, but restoring from the backup did not work. After that, the application was no longer functional even though the system itself was still mostly running.
    Initial troubleshooting focused on configuration and basic recovery steps, however the issue turned out to be related to the runtime environment. The required Ruby setup was not in a working state, and some of the background services refused to start, preventing the application from starting correctly.
    Over time, Multiple attempts were made to recover the instance, however the issue was not resolved. After a period of no progress, the focus shifted to stabilizing the system. System packages were updated, repository issues were corrected, and the server was brought back to a clean and consistent state.
    Once the system was stable, GlitchSoc was reinstalled from scratch instead of attempting another restore. The reinstall completed successfully. This included rebuilding the required runtime environment via yunohost’s configuration when the app was chosen. The application is now running normally.
    The previous backup was not restored due to compatibility concerns and the risk of reintroducing the same issue. Instead, The instance is being rebuilt gradually.
    #Fediverse #Mastodon #SelfHosting

  25. so, for those who want to know what happened and why I was offline for about 2 months here's the shortened version.
    On April 13, I attempted to upgrade my #GlitchSoc instance. The upgrade itself appeared to complete, but restoring from the backup did not work. After that, the application was no longer functional even though the system itself was still mostly running.
    Initial troubleshooting focused on configuration and basic recovery steps, however the issue turned out to be related to the runtime environment. The required Ruby setup was not in a working state, and some of the background services refused to start, preventing the application from starting correctly.
    Over time, Multiple attempts were made to recover the instance, however the issue was not resolved. After a period of no progress, the focus shifted to stabilizing the system. System packages were updated, repository issues were corrected, and the server was brought back to a clean and consistent state.
    Once the system was stable, GlitchSoc was reinstalled from scratch instead of attempting another restore. The reinstall completed successfully. This included rebuilding the required runtime environment via yunohost’s configuration when the app was chosen. The application is now running normally.
    The previous backup was not restored due to compatibility concerns and the risk of reintroducing the same issue. Instead, The instance is being rebuilt gradually.
    #Fediverse #Mastodon #SelfHosting

  26. so, for those who want to know what happened and why I was offline for about 2 months here's the shortened version.
    On April 13, I attempted to upgrade my #GlitchSoc instance. The upgrade itself appeared to complete, but restoring from the backup did not work. After that, the application was no longer functional even though the system itself was still mostly running.
    Initial troubleshooting focused on configuration and basic recovery steps, however the issue turned out to be related to the runtime environment. The required Ruby setup was not in a working state, and some of the background services refused to start, preventing the application from starting correctly.
    Over time, Multiple attempts were made to recover the instance, however the issue was not resolved. After a period of no progress, the focus shifted to stabilizing the system. System packages were updated, repository issues were corrected, and the server was brought back to a clean and consistent state.
    Once the system was stable, GlitchSoc was reinstalled from scratch instead of attempting another restore. The reinstall completed successfully. This included rebuilding the required runtime environment via yunohost’s configuration when the app was chosen. The application is now running normally.
    The previous backup was not restored due to compatibility concerns and the risk of reintroducing the same issue. Instead, The instance is being rebuilt gradually.
    #Fediverse #Mastodon #SelfHosting

  27. so, for those who want to know what happened and why I was offline for about 2 months here's the shortened version.
    On April 13, I attempted to upgrade my #GlitchSoc instance. The upgrade itself appeared to complete, but restoring from the backup did not work. After that, the application was no longer functional even though the system itself was still mostly running.
    Initial troubleshooting focused on configuration and basic recovery steps, however the issue turned out to be related to the runtime environment. The required Ruby setup was not in a working state, and some of the background services refused to start, preventing the application from starting correctly.
    Over time, Multiple attempts were made to recover the instance, however the issue was not resolved. After a period of no progress, the focus shifted to stabilizing the system. System packages were updated, repository issues were corrected, and the server was brought back to a clean and consistent state.
    Once the system was stable, GlitchSoc was reinstalled from scratch instead of attempting another restore. The reinstall completed successfully. This included rebuilding the required runtime environment via yunohost’s configuration when the app was chosen. The application is now running normally.
    The previous backup was not restored due to compatibility concerns and the risk of reintroducing the same issue. Instead, The instance is being rebuilt gradually.
    #Fediverse #Mastodon #SelfHosting

  28. so, for those who want to know what happened and why I was offline for about 2 months here's the shortened version.
    On April 13, I attempted to upgrade my #GlitchSoc instance. The upgrade itself appeared to complete, but restoring from the backup did not work. After that, the application was no longer functional even though the system itself was still mostly running.
    Initial troubleshooting focused on configuration and basic recovery steps, however the issue turned out to be related to the runtime environment. The required Ruby setup was not in a working state, and some of the background services refused to start, preventing the application from starting correctly.
    Over time, Multiple attempts were made to recover the instance, however the issue was not resolved. After a period of no progress, the focus shifted to stabilizing the system. System packages were updated, repository issues were corrected, and the server was brought back to a clean and consistent state.
    Once the system was stable, GlitchSoc was reinstalled from scratch instead of attempting another restore. The reinstall completed successfully. This included rebuilding the required runtime environment via yunohost’s configuration when the app was chosen. The application is now running normally.
    The previous backup was not restored due to compatibility concerns and the risk of reintroducing the same issue. Instead, The instance is being rebuilt gradually.
    #Fediverse #Mastodon #SelfHosting

  29. so, I can't read the quote of my own post. I mean I can read my quote, however I cannot read the post being quoted. This by using the mastodon keys on the main mastodon / glitch site and hearing my statement then the status message that the post contains a quote. All that to say, maybe I'm missing something or misunderstanding how that is supposed to work.
    #mastodon #Glitchsoc #Accessibility

  30. so, I can't read the quote of my own post. I mean I can read my quote, however I cannot read the post being quoted. This by using the mastodon keys on the main mastodon / glitch site and hearing my statement then the status message that the post contains a quote. All that to say, maybe I'm missing something or misunderstanding how that is supposed to work.
    #mastodon #Glitchsoc #Accessibility

  31. so, I can't read the quote of my own post. I mean I can read my quote, however I cannot read the post being quoted. This by using the mastodon keys on the main mastodon / glitch site and hearing my statement then the status message that the post contains a quote. All that to say, maybe I'm missing something or misunderstanding how that is supposed to work.
    #mastodon #Glitchsoc #Accessibility

  32. so, I can't read the quote of my own post. I mean I can read my quote, however I cannot read the post being quoted. This by using the mastodon keys on the main mastodon / glitch site and hearing my statement then the status message that the post contains a quote. All that to say, maybe I'm missing something or misunderstanding how that is supposed to work.
    #mastodon #Glitchsoc #Accessibility

  33. so, I can't read the quote of my own post. I mean I can read my quote, however I cannot read the post being quoted. This by using the mastodon keys on the main mastodon / glitch site and hearing my statement then the status message that the post contains a quote. All that to say, maybe I'm missing something or misunderstanding how that is supposed to work.
    #mastodon #Glitchsoc #Accessibility

  34. @fraser #glitchsoc lets you do that with a simple env var, also did that for this reason

  35. @fraser #glitchsoc lets you do that with a simple env var, also did that for this reason

  36. @fraser #glitchsoc lets you do that with a simple env var, also did that for this reason

  37. @fraser #glitchsoc lets you do that with a simple env var, also did that for this reason

  38. @fraser #glitchsoc lets you do that with a simple env var, also did that for this reason

  39. Well cool! import of my second batch failed. I'm looking into siddkick. I've seen this before
    #Mastodon #Glitchsoc

  40. Well cool! import of my second batch failed. I'm looking into siddkick. I've seen this before
    #Mastodon #Glitchsoc

  41. Well cool! import of my second batch failed. I'm looking into siddkick. I've seen this before
    #Mastodon #Glitchsoc

  42. Well cool! import of my second batch failed. I'm looking into siddkick. I've seen this before
    #Mastodon #Glitchsoc

  43. Well cool! import of my second batch failed. I'm looking into siddkick. I've seen this before
    #Mastodon #Glitchsoc

  44. @ivory any chance you have support for the #glitchsoc local-only post change planned?

    The 👁️ was depreciated and no longer works.

  45. @ivory any chance you have support for the #glitchsoc local-only post change planned?

    The 👁️ was depreciated and no longer works.

  46. @ivory any chance you have support for the #glitchsoc local-only post change planned?

    The 👁️ was depreciated and no longer works.

  47. @ivory any chance you have support for the #glitchsoc local-only post change planned?

    The 👁️ was depreciated and no longer works.

  48. @ivory any chance you have support for the #glitchsoc local-only post change planned?

    The 👁️ was depreciated and no longer works.

  49. v4.6.3

    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 section. Changelog Security Update...

    github.com/glitch-soc/mastodon

    #glitchsoc #glitch #mastodon #mastoadmin

  50. v4.6.3

    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 section. Changelog Security Update...

    github.com/glitch-soc/mastodon

    #glitchsoc #glitch #mastodon #mastoadmin