bd3867b32e
When running `bundle exec rails assets:precompile` inside docker build, with `site_title` it requires a DB connection, where as `Setting.default_settings['site_title']` doesn't. Running a docker build without this commit, the following error is reported: ``` ... [build-hometown:5785] ** Execute assets:generate_static_pages [build-hometown:5786] rails aborted! [build-hometown:5787] ActionView::Template::Error: could not connect to server: Connection refused [build-hometown:5788] Is the server running on host "localhost" (127.0.0.1) and accepting [build-hometown:5789] TCP/IP connections on port 5432? [build-hometown:5790] could not connect to server: Cannot assign requested address [build-hometown:5791] Is the server running on host "localhost" (::1) and accepting [build-hometown:5792] TCP/IP connections on port 5432? [build-hometown:5793] /opt/mastodon/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `initialize' [build-hometown:5794] /opt/mastodon/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `new' [build-hometown:5795] /opt/mastodon/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `connect' ... ``` I can provide the full trace logs if needed. |
||
|---|---|---|
| .circleci | ||
| .dependabot | ||
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| dist | ||
| lib | ||
| log | ||
| nanobox | ||
| public | ||
| spec | ||
| streaming | ||
| vendor | ||
| .buildpacks | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.nanobox | ||
| .env.production.sample | ||
| .env.test | ||
| .env.vagrant | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .foreman | ||
| .gitattributes | ||
| .gitignore | ||
| .haml-lint.yml | ||
| .nanoignore | ||
| .nvmrc | ||
| .profile | ||
| .rspec | ||
| .rubocop.yml | ||
| .ruby-version | ||
| .sass-lint.yml | ||
| .slugignore | ||
| .yarnclean | ||
| app.json | ||
| Aptfile | ||
| AUTHORS.md | ||
| babel.config.js | ||
| boxfile.yml | ||
| Capfile | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| crowdin.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| package.json | ||
| postcss.config.js | ||
| priv-config | ||
| Procfile | ||
| Procfile.dev | ||
| Rakefile | ||
| README.md | ||
| scalingo.json | ||
| Vagrantfile | ||
| yarn.lock | ||
Hometown: a Mastodon fork
Photo by Joana Mujollari, CC0 / Public Domain.
Mastodon is a free, open-source social network server based on ActivityPub. This is not the official version of Mastodon; this is a separate version (i.e. a fork) maintained by Darius Kazemi. For more information on Mastodon, you can see the official website and the upstream repo.
Hometown is a light weight fork of Mastodon. This fork is based on the principle of: minimum code change for maximum user experience change.
Please check out our wiki for a list of Hometown-exclusive features. Some but not all of these are covered in this document.
Support this project
Please consider supporting Hometown by pledging to my Patreon, which supports all my open source projects including this one!
Of course this project couldn't exist without Mastodon so maybe support the Mastodon project Patreon too.
Migrating from Mastodon to Hometown
Please see this article in the wiki for directions on migration from Mastodon to Hometown.
Local only posting
Mastodon right now is designed to get your messages out to the entire fediverse. This is great, but there is a huge need for more private communities. And in a federated network I think it makes the most sense for your home server to be that community (hence "Hometown").
In the context of Hometown, local only posting is a per-post security option that lets you set whether that post can federate out to other servers or not.
I've been running Friend Camp, a Mastodon fork with local only posting, for about a year. Being able to have conversations with people on your server that don't federate is a hugely liberating thing. It allows inside jokes to develop. It allows people the freedom to complain about things that they wouldn't necessarily feel comfortable leaving a trusted server (cops, employers, etc). It also lets us do things like have a server-wide movie night where we flood the local timeline with posts about the movie, and it doesn't pollute the rest of the Fediverse.
This feature is based on the work of Renato Lond, which is itself based on a feature in the Mastodon Glitch Edition fork.
Reading more content types
Mastodon is microblogging software, meant for Twitter-style shortform posting.
Hometown is microblogging for writing, but its goal is to accept many content types for reading. So while I don't plan to let Hometown users publish massive blog posts, I would like your Hometown instance to be your one-stop shop for viewing all sorts of things on the Fediverse.
For Hometown this means if you subscribe to a service that sends out Article objects over ActivityPub (such as a blog on Write As), then those full articles render in your home timeline, behind a cut for length. Also, Hometown will render a variety of rich text like italic and bold.
Click on this GIF for a brief video demo:
This is based on rich text work by Thibaut Girka, and my own work on Article support.
It's more than just reading more stuff
Reading more content types also helps make the fediverse better. ActivityPub supports all kinds of content, but most ActivityPub servers shoehorn all their content into Note because that's the type that Mastodon treats as first-class. This has important implications for the fediverse and also on your day to do user experience.
Take the "quote tweet" debate for example.
Twitter has a feature called "quote tweeting" that lets you embed what someone else tweets, with your own comment right next to it. It's really useful for provide commentary in context, like this, where I point people to a sale and they can read both my comment on the sale and the original tweet about the sale in one post:
But it's also open to abuse with people quote-tweeting things they disagree with to encourage a pile-on from their followers. There's been a lot of debate among Mastodon users as to whether the good of this feature outweighs the bad. So far, Mastodon has avoided implementing quoting.
What does this have to do with content types? Well, if we support an Article content type and a Note content type, we can support quoting for an Article but not for a Note. In practice this means that you can quote blog posts and news articles, but you can't quote a quick personal microblog note.
Hometown doesn't support quoting articles yet... but it will.
Better list management
If Hometown is going to be a universal reader, you're going to need better control over organizing your feeds than mainline Mastodon provides.
Exclusive lists
My first plan is to introduce a new kind of exclusive list. Right now if you add an account to your "friends I like" list in Mastodon, posts from people on that list appear on that list. But they also appear on your home timeline, and maybe you don't want that! You'd rather treat your "friends I like" list as your "real" home timeline, and then check your home timeline when you're bored.
Or another case: I might have all the blogs I read in one list, but I only check it on Saturdays when I have time to read things. In that case I don't want updates from those blogs clogging up my home timeline.
This is not yet implemented but will be available in the first release.
Better accessibility defaults
Look, right now this pretty much just means that we underline hyperlinks by default. I'm of course open to implementing other obviously beneficial accessibilty defaults that Mastodon itself doesn't implement.
Hometown is still 99.999% Mastodon
I don't intend to stray very far from mainline Mastodon with this fork. If you want something that provides a ton of new features and widgets and stuff, the Mastodon Glitch Edition fork is a wondrous kitchen sink of major and minor tweaks.
Part of why I don't want to stray far from mainline Mastodon is that this project is going to be just me for the foreseeable future, and I'd like to keep it up to date with new Mastodon versions as easily as possible. The less code I change from Mastodon, the easier that is. Hence the principle of "minimum code change for maximum user experience change."
Versioning
Hometown uses semantic versioning and follows a versioning convention like v1.0.0+2.9.3. The 1.0.0 part is the actual Hometown version number, and then the 2.9.3 after the + sign is what's known in semantic versioning as "build metadata". It just means that a particular release is synchronized with Mastodon version 2.9.3, so for example an upgrade from v1.0.0+2.9.2 to v1.0.0+2.9.3 would upgrade Mastodon but not provide any new Hometown features or fixes.
Contributing to Hometown
Setting up your Hometown development environment is exactly like setting up your Mastodon development environment. Pull requests should be made to the hometown-dev branch, which is our default branch in Github.
License
Copyright (C) 2016-2019 Eugen Rochko and other Mastodon contributors; see AUTHORS.md.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see https://www.gnu.org/licenses/.