A privacy-aware, distributed, open source social network.
AGPL-3.0 License
Bot releases are hidden (Show)
Published by jhass over 9 years ago
This release includes a major upgrade of the background processing system Sidekiq. To upgrade cleanly:
RAILS_ENV=production bundle exec sidekiq
and wait 5-10 minutes, then stop it again (hit CTRL+C
)Please edit config/initializers/secret_token.rb
, replacing secret_token
with
secret_key_base
.
# Old
Rails.application.config.secret_token = '***********...'
# New
Diaspora::Application.config.secret_key_base = '*************...'
You also need to take care to set RAILS_ENV
and to clear the cache while precompiling assets: RAILS_ENV=production bundle exec rake tmp:cache:clear assets:precompile
This release drops official support for the Ruby 1.9 series. This means we will no longer test against this Ruby version or take care to choose libraries
that work with it. However that doesn't mean we won't accept patches that improve running diaspora* on it.
At the same time we adopt support for the Ruby 2.1 series and recommend running on the latest Ruby version of that branch. We continue to support the Ruby 2.0
series and run our comprehensive test suite against it.
The default for including jQuery from a CDN has changed. If you want to continue to include it from a CDN, please explicitly set the jquery_cdn
setting to true
in diaspora.yml.
For MySQL databases, replace charset: utf8
with encoding: utf8mb4
and change collation
from utf8_bin
to utf8mb4_bin
in the file config/database.yml
.
This is enables full UTF8 support (4bytes characters), including standard emoji characters.
See database.yml.example
for reference.
Please make sure to stop Diaspora prior running this migration!
This release adds experimental integration with XMPP for real-time chat. Please see our wiki for further informations.
The way services are shown in the statistics.json
route is changing. The keys relating to showing whether services are enabled or not are moving to their own container as "services": {....}
, instead of having them all in the root level of the JSON.
The keys will still be available in the root level within the 0.5 release. The old keys will be removed in the 0.6 release.
Removing of old inactive users can now be done automatically by background processing. The amount of inactivity is set by after_days
. A warning email will be sent to the user and after an additional warn_days
, the account will be automatically closed.
This maintenance is not enabled by default. Podmins can enable it by for example copying over the new settings under settings.maintenance
to their diaspora.yml
file and setting it enabled. The default setting is to expire accounts that have been inactive for 2 years (no login).
It is now possible to enable an automatic proxying of external assets, for example images embedded via Markdown or OpenGraph thumbnails loaded from insecure third party servers through a Camo proxy.
This is disabled by default since it requires the installation of additional packages and might cause some traffic. Check the wiki page for more information and detailed installation instructions.
Podmins can now set the currency for donations, and use an unhosted button if they can't use
a hosted one. Note: you need to copy the new settings from diaspora.yml.example to your
diaspora.yml file. The existing settings from 0.4.x and before will not work any more.
diaspora* no longer adds a div.container
to wrap custom splash pages. This adds the ability for podmins to write home pages using Bootstrap's fluid design. Podmins who added a custom splash page in app/views/home/_show.{html,mobile}.haml
need to wrap the contents into a div.container
to keep the old design. You will find updated examples in our wiki.
opengraph_parser
with open_graph_reader
#5462
more
link on mobile stream pages #5400
Published by denschub over 9 years ago
Update Redcarped, fixes OSVDB-120415.
Published by jhass almost 10 years ago
Update Rails, fixes CVE-2014-7818.
Published by jhass about 10 years ago
Published by jaywink about 10 years ago
This release brings a new ToS feature that allows pods to easily display to users the terms of service they are operating on. This feature is not enabled by default. If you want to enable it, please add under settings
in config/diaspora.yml
the following and restart diaspora. If in doubt see config/diaspora.yml.example
:
terms:
enable: true
When enabled, the footer and sidebar will have a link to terms page, and signup will have a disclaimer indicating that creating an account means the user accepts the terms of use.
While the project itself doesn't restrict what kind of terms pods run on, we realize not all podmins want to spend time writing them from scratch. Thus there is a basic ToS template included that will be used unless a custom one available.
To modify (or completely rewrite) the terms template, create a file called app/views/terms/terms.haml
or app/views/terms/terms.erb
and it will automatically replace the default template, which you can find at app/views/terms/default.haml
.
There are also two configuration settings to customize the terms (when using the default template). These are optional.
settings.terms.jurisdiction
- indicate here in which country or state any legal disputes are handled.settings.terms.minimum_age
- indicate here if you want to show a minimum required age for creating an account.There is a new Rake task podmin:admin_mail
available to allow podmins to easily send news and notices to users. The rake task triggers emails via the normal diaspora mailer mechanism (so they are embedded in the standard template) and takes the following parameters:
all
- all users in the database (except deleted)active_yearly
- users logged in within the last yearactive_monthly
- users logged in within the last monthactive_halfyear
- users logged in within the last 6 monthsExample shell command (depending on your environment);
RAILS_ENV=production bundle exec rake podmin:admin_mail['active_monthly','./message.html','Important message from pod']
Read more about specifying arguments to Rake tasks.
Published by jaywink over 10 years ago
Published by jaywink over 10 years ago
A regression caused accounts deletions to not properly perform in some cases, see #4792.
To ensure these are reexecuted properly, please run RAILS_ENV=production bundle exec rake accounts:run_deletions
after you've upgraded.
This version will break federation to pods running on versions prior 0.1.1.0.
Published by jhass over 10 years ago
Published by jaywink over 10 years ago
Published by jaywink over 10 years ago
Published by jaywink over 10 years ago
A new feature has been added to allow pods to report extra statistics. Automatically after this code change, the route /statistics.json contains some basic data that was also available before via page headers (pod name, version, status of signups). But also, optionally podmins can enable user and post counts in the diaspora.yml configuration file. The counts are by default switched off, so if you want to report the total user, active user and local post counts, please edit your diaspora.yml configuration with the example values in diaspora.yml.example and uncomment the required lines as indicated.
We now recommend using Ruby 2.0 with Diaspora. If you're using RVM make sure to run:
rvm get stable
rvm install 2.0.0
cd ~/diaspora
git pull
cd - && cd ..
For more details see https://wiki.diasporafoundation.org/Updating
Added:
Removed:
Updated:
Published by fabianrbz almost 11 years ago
Published by jhass about 11 years ago
Start versioning diaspora*
Published by jhass about 11 years ago
Copy over config/diaspora.yml.example to config/diaspora.yml and migrate your settings! An updated Heroku guide including basic hints on howto migrate is here.
The new configuration system allows all possible settings to be overriden by environment variables. This makes it possible to deploy heroku without checking any credentials into git. Read the top of config/diaspora.yml.example
for an explanation on how to convert the setting names to environment variables.
The following gems and their related files were removed as they aren't widely enough used to justify maintenance for them by the core developers. If you use them please maintain them in your fork.
The following gems were removed because their are neither used in daily development or are just CLI tools that aren't required to be loaded from the code:
Refactoring of the JavaScript code; it is now completely rewritten to make use of Backbone.js.
This paves the way for future improvements such as post preview or edit toolbar/help.
The feature-flag on users and all the code in connection with experimental UX changes got removed/reverted. Those are the parts that became Makr.io.
The single-post view will also be revamped/reverted, but that didn't make it into this release.
Published by jhass about 11 years ago
Published by jhass about 11 years ago
Fix exception when the root of a reshare of a reshare got deleted #3546
Published by jhass about 11 years ago
script/get_config.rb
config/script_server.yml
is removed and replaced by the server
section in config/diaspora.yml
RAILS_ENV
and DB
are now prefered over those set in config/diaspora.yml
ENVIRONMENT_UNICORN_EMBED_RESQUE_WORKER
got renamed to SERVER_EMBED_RESQUE_WORKER
follow_diasporahq
has now to be set to true
to enable following the DiasporaHQ account. Was false
And their dependencies.
Published by jhass about 11 years ago
Published by jhass about 11 years ago
Published by jhass about 11 years ago