Was soll daraus werden? Tonnenweise Accounts verlinken noch dort hin. Wenn die Domain einfach ausgegeben wird, schnappt sich ein #Domain-Hai diese garantiert weg und geht dann zu irgent welchem Domain-Parker wie #sedo hin und macht damit dick fett Kohle. Das sollten wir nicht wollen!

Und außerdem, was passiert mit den Bots, wie z.B. @bestofpispers ?

For those with a slow Internet connection, it can be a pain to download #fgdata for #FlightGear through GIT as GIT does not support resume and the connection may get lost and then they have to download the whole pack all over again.

For this, I have donated my #bittorrent tracker to the community, alongside other "small" stuff like #Haiku (BeOS) and others. You can find the tracker at ...
There you find the main bundle fgdata_new.bundle and currently 2 update files. You can now download them with bittorrent. Then you have to clone from them as usual:

$ git clone fgdata_new.bundle fgdata
$ cd fgdata
$ git remote add update1 ../fgdata_new-update-001.bundle
$ git remote add update2 ../fgdata_new-update-002.bundle
$ git fetch --all
$ git merge update1/master
$ git merge update2/master

$ git remote rm update1
$ git remote rm update1
$ git remote set-url origin https://git.code.sf.net/p/flightgear/fgdata
$ git fetch
$ git merge origin/master

Hi @Friendica Developers I'm getting this error on my instance (this):

PHP Notice:  Use of undefined constant REGISTER_CLOSED - assumed 'REGISTER_CLOSED' in /var/www/../.htconfig.php on line 38
PHP Stack trace:
PHP   1. {main}() /var/www/../bin/daemon.php:0
PHP   2. include() /var/www/../bin/daemon.php:41

I get this every time I start or stop the daemon (as you can see in backtrace).

Gettings these warnings a lot:

Warning: mysqli::close(): Couldn't fetch mysqli in /var/www/../htdocs/include/dba.php on line 100

Call Stack:
 0.0005 346776 1. {main}() /var/www/../htdocs/include/cron_sync.php:0
 0.0149 486640 2. run_pulling_job() /var/www/../htdocs/include/cron_sync.php:93
 0.0899 567136 3. pull_worker() /var/www/../htdocs/include/sync.php:406
 0.0927 578144 4. dba->__destruct() /var/www/../htdocs/include/sync.php:350
 0.0927 578144 5. mysqli->close() /var/www/../htdocs/include/dba.php:100

Anyone knows what is wrong? And I had to fix .htaccess file for Apache 2.4 (Require all denied is the correct one).

Finally I found some time to continue developing (at least a bit) on my upcoming FLOSS Java projects (do I have to add the class path exception here?) with entities (JPA), Enterprise Java Beans and JSF applications.

And I listen to #Psy-Trance .

I have to commit a lot as I have not done that for several months. Now I review my changes and found here and there some bad things, like having "complex" methods in entity classes (you should better write an utility class for these methods and declare them static).

Really a lot stuff to do here. I have many small projects as suggested by my trainer. Have small reusable "components" and not one big "core" that all have to include.

I'm currently developing (free time project) a Java Server Faces application which uses the #JPA (very common to do so) over EJBs (Enterprise Java Beans). When I turned on logging of SQL queries, I thought I didn't see it right. For each entity ("row" in database table) a distinct query has been issued. Means, when I have 1,000 rows, the same amount of queries are being issued.

This can become a nightmare when "only" 100 users are on the server. Does someone know how to reconfigure the JPA (I use #Payara ) to issue only one SQL query per table?

Surely I have used JPQL (Java Persistence Query Language) and no WHERE was used there. So normally the whole table should be fetched. But this is not the case for linked tables (e.g. with @OneToOne) where each such referenced entity is being fetched distinctly.

So is there a way to prevent this from happening? RAM is not a issue here. 16 GB are installed and data will not grow so much.

Ich wurde hier #aufarbeit angesprochen, ob ich [bold]hier[/bold] auf #Facebook unterwegs sei ... Ja, ist verwechselbar, wenn man sehr ungenau hinsieht. Vielleicht hat er sich an dem Favicon festgeklammert?

Naja, nicht als Kritik oder FB-Bashing verstehen, was damit auch nicht beabsichtigt ist, ich weis sehr wohl, dass Friendica != Facebook ist, da es eine freie Alternative ist.

Ich finde es halt etwas bedenklich. Ich musste nachkorrigieren und sagen, dass es nicht FB, sondern Friendica ist. Mal schauen, vielleicht wechsel ich das Theme? Sieht es wirklich so verwandt mit FB aus? Finde nicht, hier ist vieles weiss und grau, bei FB weiss und blau.

I currently have a glass stuck in a porcelain. I have already setup cold water in top glass and hot (boiling, I'm careful) around lower but still they remain stuck. Plus I added salt in upper (cold) glass. I got this (last) idea from a #youtube video with ID #HOglOnne3As which seems quite straight-forward but still no success here.

Any ideas? I cannot currently upload images, size limit of 780k exceeded but I set $a->config['system']['maximagesize'] = 2*1024*1024; which should be enough, right?

Strange #bug in #Friendica ... So you have to live with a link to my #nextcloud instance: cloud.mxchange.org/s/rnFtrpbQq…

I have managed to bring back my #searx instance at
back working again. I had updated my Apache installation to 2.4 and forgot to change the settings to Require all granted.

Feel free to use it (on your own risk, careful: adult content is possible to find).

@Friendica Support I had always a working XMPP instance on my friendica instance. Now it doesn't connect. I have enabled debug log in .htaconfig file but nothing is written there.

With pstree I can only see beam.smp with 18 beam.smp threads but no ejabberd_auth.php sub process which did happen before. strace tells me that it tries to read from 0 (stdin) so it seems to wait for input. Access rights and correct user/group are set (0700, ejabberd.ejabberd according to documentation). Yet still it isn't starting.

Any ideas what might cause this?