Skip to main content

Testing #friendica mastodon API from toot cli. Friendica seems to be quite compatible with quite many mastodon clients already. Still continuing the testing
This entry was edited (3 months ago)

Markku Raitisoja reshared this.

Our Email Self-Defense guide, which teaches you how to encrypt your email with GnuPG, is back and better than ever! Check out the updated version, get your GnuPG set up, and share with absolutely everyone you know with #UserFreedom:

Very nice!
Uff. Having a guide is better than nor having one... but the length of this guide really demonstrates how arcane #email #encryption still is. It requires a lengthy setup that includes using the terminal and even when used correctly, there are still many gotchas (don't use that subject line).

It's no wonder people prefer to use software such as the vendor-locked #signal instead. Signal gets the UX right so no guide is necessary.

#pgp #gpg #openpgp

How would they surveillance encrypted chats?
by requiring backdoors. Companies with "true" encryption could be deemed as operating illegally once the second law is approved.
lol like that will stop anyone, still gonna use matrix
what a shame and disappointed, who of those parliamentary know what does IP address do :oh_no_blob:

Markku Raitisoja reshared this.

Friendica 2021.07 released

We are very happy to announce the availability of the new stable release of Friendica “Siberian Iris” 2021.07. This release contains 219 pull requests from ten contributors and the work of the translation teams. While fixing some problems identified, we have added some nice features
  • support for right-to-left languages was added,
  • the API was expanded to have Mastodon compatible endpoints and
  • an addon was added to support SAML services like keycloak for login.

For a detailed overview of the changes, please have a look at the CHANGELOG.

How to Update

Updating from old Friendica versions

If you are updating from an older version than the 2020.03 release, please first update your Friendica instance to that version.

In that version we introduced views to the database and some node admins reported that they had to adjust their MariaDB configuration (table_definition_cache). Also setting pdo_emulate_prepares to true in the Friendica configuration might be nessessary.

Pre-Update Procedures

Ensure that the last backup of your Friendica installation was done recently. We had no problems reported during the upgrade process from 2021.04 to the 2021.06 release candidate, so hopefully you will have a smooth transition.

Please make sure to use Barracuda as MySQL DB file format for your Friendica database. Change your database settings before you proceed with the Friendica update. This change will take some time depending on the size of your database.

Using Git

Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository, regardless of the branch (stable or develop) you are using. Remember to update the dependencies with composer as well.
cd friendica
git fetch
git checkout BRANCH
bin/composer.phar install --no-dev
cd addon
git fetch
git checkout BRANCH
Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.

Using the Archive Files

If you had downloaded the source files in an archive file (tar.gz) please download the current version of the archive (friendica-full-2021.07.tar.gz and friendica-addons 2021.07.tar.gz) and unpack it on your local computer.

As many files got deleted or moved around, please upload the unpacked files to a new directory on your server (say friendica_new) and copy over your existing configuration (config/local.config.php and config/addon.config.php) and .htaccess files. Afterwards rename your current Friendica directory (e.g. friendica) to friendica_old and friendica_new to friendica.

The files of the dependencies are included in the archive (make sure you are using the friendica-full-2021.07 archive), so you don’t have to worry about them.

Post Update Tasks

The database update should be applied automatically, but sometimes it gets stuck. If you encounter this, please initiate the DB update manually from the command line by running the script
bin/console dbstructure update
from the base of your Friendica installation. If the output contains any error message, please let us know using the channels mentioned below.

Please note, that some of the changes to the database structure will take some time to be applied, depending on the size of your Friendica database.

Known Issues

Please note, that one of the dependencies of Friendica is currently incompatible with PHP 7.0. If you are still running that version of PHP, please have a look at this forum thread for a workaround.

How to Contribute

If you want to contribute to the project, you don’t need to have coding experience. There are a number of tasks listed in the issue tracker with the label “Junior Jobs” we think are good for new contributors. But you are by no means limited to these – if you find a solution to a problem (even a new one) please make a pull request at github or let us know in the development forum.

Contribution to Friendica is also not limited to coding. Any contribution to the documentation, the translation or advertisement materials is welcome or reporting a problem. You don’t need to deal with Git(Hub) or Transifex if you don’t like to. Just get in touch with us and we will get the materials to the appropriate places.

Thanks everyone who helped making this release possible and have fun!
Umm, are you sure you know git? 😀 (I DO NOT!)
You say I shall do
git fetch
git checkout stable

But then git says
Your branch is behind 'origin/stable' by 819 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)

But you have not told me to pull. Is it fine not to pull? 😉
You should do git pull so that your stable branch becomes up to date with the upstream stable branch.
@grin @Friendica News thanks! the pull got lost at some point during the editing of the release notes. I've updated them.
The `man` say "pull" equals to "git fetch && git merge", so I guess it shall be "got merge" (but it's no accident that I dislike git due to its obscure command structure and even more obscure documentation).
I guess, based on that, both pull and merge would be fine. It is also possible that in some cases checkout is enough? I can't tell.
There is an important distinction between your local repository that you cloned and the remote repository you cloned from. Each branch you check out from the remote repository is duplicated on your local repository. On checkout the local branch is set on the same commit as the remote one but from then on, it will be completely independent. If you currently are on somebranch, git pull actually is equivalent to git fetch remote && git merge remote/somebranch somebranch. You are merging the remote branch into your local branch. If you didn't commit any work on your local branch, it can simply be reset to the current remote branch commit, this is the meaning of "fast-forwarded".
@Tobias would be good to include the git pull, right? Also can we replace "BRANCH" with "stable" for the future? I mean this is a update notification, anyone wanting to do the update should checkout stable, nothing else, at least for this notification, right?
Thank you all for the demonstration of why I dislike git. 😁
I give you one week to figure out the exact half dozen commands and parameters which does not mess up everything. :-]

(As a sidenote, I rm -rf-ed it because it started acting really weird, like complaining half of the files being local updates which were not, and cloned a fresh one and it was upgraded just fine. And sent mental greetings to git authors.)

Apple has OTP client built-in with new beta versions of the password program.
You can find it in iOS, ipadOS and MacOS beta settings.

Also screenshotting the password entry on iOS nicely hides password and OTP code automatically.

#ios15 #macOS12Monterey #iPadOS15