We've been calling it the "berserker.town fork of Glitchsoc" or just "berserker.town", but this project isn't meant to be specific to berserker.town. You're supposed to be able to deploy it elsewhere. It needs a nice and snappy name. And it shouldn't be a bad name like GNU Smelly Warthog.
We've been calling it the "berserker.town fork of Glitchsoc" or just "berserker.town", but this project isn't meant to be specific to berserker.town. You're supposed to be able to deploy it elsewhere. It needs a nice and snappy name. And it shouldn't be a bad name like GNU Smelly Warthog.
glitch-soc is fine imo.
It's hard enough to find any glitch-soc instances and a little modification is sort of expected. As long as the changes are transparent again, I see no problems...
glitch-soc is fine imo.
It's hard enough to find any glitch-soc instances and a little modification is sort of expected. As long as the changes are transparent again, I see no problems...
Other instances will likely want to rename again anyway. But if we're playing the naming game just for fun,
"Berserker Glitch Soc" would be an obvious choice. It sounds like putting the glitchiness and therefore the freedom to the max. I like that...
Other instances will likely want to rename again anyway. But if we're playing the naming game just for fun,
"Berserker Glitch Soc" would be an obvious choice. It sounds like putting the glitchiness and therefore the freedom to the max. I like that...
@akko More specifically: This is not the Git repository for the local deployment that's running on berserker.town. The main branch here will not give you a Tavern for example. That's a site-specific modification. I noticed that you made an issue ticket about the Tavern, but it's just called the local timeline in this repository. The modifications that are for berserker.town specifically are on a branch named "local".
@akko More specifically: This is not the Git repository for the local deployment that's running on berserker.town. The main branch here will not give you a Tavern for example. That's a site-specific modification. I noticed that you made an issue ticket about the Tavern, but it's just called the local timeline in this repository. The modifications that are for berserker.town specifically are on a branch named "local".
@akko The project is associated with berserker.town but is intended for use elsewhere also. It merges in changes from Glitchsoc much like Glitchsoc merges changes in from Mastodon.
@akko The project is associated with berserker.town but is intended for use elsewhere also. It merges in changes from Glitchsoc much like Glitchsoc merges changes in from Mastodon.
First thought: trying to retain the association to Mastodon which was part of the extinct Amrican megafauna, so maybe something like Glyptodon (giant armadillo) or Smilodon (cool name and it's a cat!).
Second thought: bs.town runs on a derivate of glitch-soc being a derivate of Mastodon, just like the most popular Linux distro Mint being a derivate of a derivate, so name it a herb like parsley, chives or basil.
It's so difficult.
First thought: trying to retain the association to Mastodon which was part of the extinct Amrican megafauna, so maybe something like Glyptodon (giant armadillo) or Smilodon (cool name and it's a cat!).
Second thought: bs.town runs on a derivate of glitch-soc being a derivate of Mastodon, just like the most popular Linux distro Mint being a derivate of a derivate, so name it a herb like parsley, chives or basil.
We've been calling it the "berserker.town fork of Glitchsoc" or just "berserker.town", but this project isn't meant to be specific to berserker.town. You're supposed to be able to deploy it elsewhere. It needs a nice and snappy name. And it shouldn't be a bad name like GNU Smelly Warthog.
glitch-soc is fine imo.
It's hard enough to find any glitch-soc instances and a little modification is sort of expected. As long as the changes are transparent again, I see no problems...
Other instances will likely want to rename again anyway. But if we're playing the naming game just for fun,
"Berserker Glitch Soc" would be an obvious choice. It sounds like putting the glitchiness and therefore the freedom to the max. I like that...
@akko That's missing the point.
@akko More specifically: This is not the Git repository for the local deployment that's running on berserker.town. The main branch here will not give you a Tavern for example. That's a site-specific modification. I noticed that you made an issue ticket about the Tavern, but it's just called the local timeline in this repository. The modifications that are for berserker.town specifically are on a branch named "local".
@akko The project is associated with berserker.town but is intended for use elsewhere also. It merges in changes from Glitchsoc much like Glitchsoc merges changes in from Mastodon.
It's so difficult.
First thought: trying to retain the association to Mastodon which was part of the extinct Amrican megafauna, so maybe something like Glyptodon (giant armadillo) or Smilodon (cool name and it's a cat!).
Second thought: bs.town runs on a derivate of glitch-soc being a derivate of Mastodon, just like the most popular Linux distro Mint being a derivate of a derivate, so name it a herb like parsley, chives or basil.