This update fixes a critical bug preventing normal profile/server probe that made displayed profile number plummet since version 2.3.0.

#Friendica #Development

I just pushed version 2.3.0 of #Friendica Directory.

This release notably adds back support for the zrl query parameter that allows a directory user coming from a Friendica node to be automatically authenticated with remote nodes to make remote follow seamless.

This was a legacy directory feature that had been missing from the new directory ever since it's been initially released.

As usual, please report bugs and feature requests at https://github.com/friendica/friendica-directory/issues where I'll safely ignore them for several months before suddenly take care of one of them during an all-nighter coding frenzy!

#development

I need one of the git masters here.

git pull
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.

How can I solve this? I do not need to keep any local changes, except for config files and .htaccess or so.
The message showed up after I did checkout "develop".

#Friendica !Friendica Support

I had a problem with #Friendica, compared to Faceshit. I constantly read posts by only the most frequently posting accounts. And others were just lost on the timeline.

So I made a little script. Idea is to group contacts by posting frequency into couple of groups created just for this purpose, like "rare", "very rare" and "frequent". I run this script from time to time to automatically move contacts between these groups.

https://github.com/loziniak/red-scripts/blob/master/friendica-regroup.red

Script is written in Red, you can check the language out here: http://www.red-lang.org/

@Friendica Support #fediverse #facebook

Thanks to @hypolite I'm having a little play with #Friendica over at @uxintro

It's an account that will self destruct in a week. Feel free to interact with it but don't be surprised if I disappear 😆

Hello !Friendica Support
any cool idea what to do with the domain mistpark.com? 😀

For the historical background of the name...

"Friendica (formerly Friendika, originally Mistpark) is an open, free, distributed social network."

https://en.wikipedia.org/wiki/Friendica

Steffen K9 🐰

2020-05-23 11:56:58

Ha! Hahahahaha! Okay. So, what now?

#mistpark #friendica

mistpark.com

Sometime when I post a reply (did some tests) on my other #friendica server I only get an empty page only stating "success" as shown below.

What is wrong in this case?

Looks like this:

!Friendica Support

How can I see the jpm again? Does it require a certain log level? Had a tail -F running for a few minutes but didn't spot anything like it.

I got it activated in the config:
'worker_jpm' => 'true'

!Friendica Support #friendica

Sind bei anderen Nutzern von #Friendica die Benachrichtigungen (trotz der Spracheinstellungen auf Deutsch) in Englisch?
Fiel mir bis jetzt nicht auf, aber nehme an da ist nen Fehler im letzten Release, kann das sein?

!Friendica Support

@Friendica Support My #friendica instance is running for about 1 year now and the database has grown to 9.9GB. I found out about the remote items today and set the threshold to 20 days. After running the worker some 100 MB where gone from the database, but after running OPTIMIZE TABLE it is back on 9.9GB.

My instance has only one user. What can be the reason for such a lot of used space?

Since we now have contact filters, here's a breakdown of my contacts from #Friendica by protocol (Followers/Follows/Mutuals):

• DFRN: 147/105/90
• Diaspora: 174/103/96
• OStatus: 171/16/8
• ActivityPub: 139/89/39
• Twitter: 200/154/(69 or 141?)

Unexpectedly my #Friendica Server went into maintenance mode this night (I guess). I think it got stuck in the maintenance mode.

On the page I see:

#0 [internal function]: Friendica\Module\Maintenance::content(Array)
#1 /srv/http/src/App/Page.php(332): call_user_func(Array, Array)
#2 /srv/http/src/App/Page.php(388): Friendica\App\Page->initContent(Object(Friendica\App\Module), Object(Friendica\App\Mode))
#3 /srv/http/src/App.php(576): Friendica\App\Page->run(Object(Friendica\App), Object(Friendica\App\BaseURL), Object(Friendica\App\Mode), Object(Friendica\App\Module), Object(Friendica\Core\L10n), Object(Friendica\Core\Config\JitConfig), Object(Friendica\Core\PConfig\JitPConfig))
#4 /srv/http/index.php(42): Friendica\App->runFrontend(Object(Friendica\App\Module), Object(Friendica\App\Router), Object(Friendica\Core\PConfig\JitPConfig), Object(Friendica\App\Authentication), Object(Friendica\App\Page))
#5 {main}

I tried to run "bin/console dbstructure update", but in mysql there is no processes.

Should I try to finish maintenance mode manually?

!Friendica Support