Do you mind when I disable the Twitter plugin? Do other people use it here?
I mean: you are using Friendica or the Fediverse in whole by purpose, because you decided to not use Twitter. I don't think that anyone is using Friendica as a Twitter client.
So, are we ok with disabling the Twitter plugin on Nerdica?
I don't know why, but the webserver seems to be under attack the last days. At least there was way too much load on the webserver caused by connections in "sending" state:
Total accesses: 1080 - Total Traffic: 11.5 MB - Total Duration: 222445988 CPU Usage: u6.3 s.84 cu8.99 cs1.45 - 3.12% CPU load 1.92 requests/sec - 20.9 kB/second - 10.9 kB/request - 205969 ms/request 195 requests currently being processed, 5 idle workers WRCWWWWWCRCCWWRRWRWRCWCRWWWWWWWWWRCRWWRRWWWWWWWCWWWWWWWWWRCWRCWR RWRWCCWWWCWWWWWWWWWRWWRWWWWCWWWWWWWWWWWWWCRRWWWWWCWWWCRWWRWWWWWW WWWWCWRCWWWCWWWWWWWWCWWWWWRWWWWWWWRWWRCRCWWWWWCW.WWCWWWWWRWWRWW. WRWRWWRWR_WWWRWWWW_RWWWWW__RRRW_W.........................WCWCWW WRWWWCRWWWWRWWWRWWW.......W.WWCWWWWWWWWWWWWC..WW........W..G.W.. ........WW..W.CC.WWWWWWWWWWWWWWWWWWWWWWWWCWWRWWRRWCWRRWWWWWWWWWC WWWCWRRWRWWWRRWR Scoreboard Key: "_" Waiting for Connection, "S" Starting up, "R" Reading Request, "W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup, "C" Closing connection, "L" Logging, "G" Gracefully finishing, "I" Idle cleanup of worker, "." Open slot with no current process
The effect was that the webserver and thereof Friendica on Nerdica.net was quite unresponsive, as you can imagine from this screenshot:
I've now activated mod_evasive in Apache configuration and the result is after some minutes already visible:
K__KKW__KK__K__W_R__R____....................................... .W.............................................................. ................................................................ ................................................................ ................................................................ ................................................................ ................ Scoreboard Key: "_" Waiting for Connection, "S" Starting up, "R" Reading Request, "W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup, "C" Closing connection, "L" Logging, "G" Gracefully finishing, "I" Idle cleanup of worker, "." Open slot with no current process 2019 Aug 31 11:13:02 vserv1 Blacklisting address 2001:b011:700e:102f:c55f:352b:4274:a089: possible DoS attack. 2019 Aug 31 11:14:29 vserv1 Blacklisting address 126.96.36.199: possible DoS attack. 2019 Aug 31 11:15:05 vserv1 Blacklisting address 188.8.131.52: possible DoS attack. 2019 Aug 31 11:15:07 vserv1 Blacklisting address 184.108.40.206: possible DoS attack. 2019 Aug 31 11:15:55 vserv1 Blacklisting address 220.127.116.11: possible DoS attack.
So, hopefully the issue is now resolved. But if you experience issues because of mod_evasive, then please send me a mail to the same address as my Nerdica address... (or via XMPP).
Bond In Guy reshared this.
As already proposed some weeks ago, I've now implemented a method to shutdown the open registration when there are 1200 users on Nerdica. Currently we are at 1194 users.
Registration will automatically re-open when the number of users drops again under 1100 users.
Already registered users can invite family and friends to Nerdica.Net regardless of public registration status being open or closed. Just invite them by mail.
But public registration will now be automatically closed and re-opened as described.
There was another short outage for maintenance to mitigate some CPU bugs:
SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:OK CVE-2018-3639:OK CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:OK CVE-2018-12130:OK CVE-2018-12127:OK CVE-2019-11091:OK
Services should be back to normal now.
cc @nerdicasupport @fedilab
Right now this #Friendica node has 1098 registered users and like 200 monthly active users.
I'm thinking about switching the registration mode from open registration to closed registration. With closed registration it should be still possible to invite friends over here and get new users, but it won't be possible to still register without an invitation.
The idea of limiting the number of users on this node are:
* this is a private server with limited resources. So having thousands or tenthousands of users is unlikey to run will on the current hardware. It's not like the current hardware is facing its limits, but I want to avoid facing these limits for the sake of smooth operation for the current users
* the basic idea of the federation is that everyone can run an own node instead of having large, centralized nodes. Currently we have 3 or 4 large nodes running Friendica and limiting the number of users would strengthen the federated nature of Friendica by encouraging new users to register on smaller nodes.
So, how do you think about this? My basic idea is to have a user count between 1000 and 1200 users. When I come close to 1200 registered users, I will close down registration and when users got deleted and the number comes down to 1000 users again, I will open registration again. As already said: as a registered user you should be able to invite other people regardless of the registration being open or closed.
Just some minutes ago I upgraded Nerdica to current release candidate version 2019.06-rc:
Friendica 'Dalmatian Bellflower' 2019.06-rc - 1313
Prior upgrade tries were failing, but this time everything went well.
If you experience any issues please report them to
!email@example.com- that way the issues can be worked on directly by the developers.
as you certainly have experienced on Friday, Nerdica.Net was unavailable for a longer time.
Well, I tried to upgrade the underlying Debian Linux installtion from stretch to buster. Although I did that before on other virtual servers, there was a new problem on this server: the Apache webserver didn't want to start.
Unfortunately, as a bonus challenge, I needed to go away from my desk and was only able to work on the issue via my iPhone SE and an SSL client. This lead to longer time to fix this issue than it would have been when I was still on my laptop.
In the end everything should work again. If you experience some problems, please drop me a note. Thanks!
you may have experienced some outage this evening. Reason was that I tried to upgrade to the release candidate of Friendica 2019.06-rc today. This failed and I needed to restore the code from backup.
Apparently it is now running again on latest stable release.
Sorry for the inconvenience...
When I go to settings, select "Password change", fill in my new password and confirmation, fill in the current password (the one I got via email), then click "Save Settings" I get 4 warnings, one of which displays "Password unchanged".
And indeed when trying to log off/in my new password doesn't work and the old one still does.
Is this an issue with Friendica, should I be submitting it on Github?
c0dr LnX likes this.
this evening I switched Nerdica to the current release candidate 2019.03-rc of Friendica.
The migration took a little longer as the database upgrade failed again and again with a strange error. It took a while until I figured out was the problem was and fixing it.
Sorry for the unexpected long downtime, but now it should be running just fine again. If you experience any issues, please report here or in the Friendica Support Forum, where the developers are also reading...
I found the Social Networks page, and the Wordpress Export section. But I can't find any documentation anywhere that explains what's being looked for in the key "WordPress API URL" field. Anyone have an answer, or know where I can dig up more information on this?
"All (friendly) creatures welcome! Free registration. Server located in Germany. As a registered user on Nerdica.Net you are also able to use XMPP (Jabber) under the same address and with your password. Get the best of free and open networks at Nerdica.Net! "
I received a mail from Google about the closing down of #Google+ :
Hello Google+ Developer,
The email below contains your most recent usage of Google+ APIs. Note: It includes Google+ OAuth scope requests, which are also affected by the Google+ shutdown. A prior email sent to active API callers did not include information about OAuth requests. One final reminder email will be sent in February to users who still have active API or OAuth request activity.
What do I need to know?
On March 7, 2019, all Google+ APIs and Google+ Sign-in will be shut down completely. This will be a progressive shutdown, with API calls starting to intermittently fail as early as January 28, 2019, and OAuth requests for Google+ scopes starting to intermittently fail as early as February 15, 2019.
What do I need to do?
Please update your projects listed below by March 7, 2019 and ensure they are no longer using Google+ APIs, or requesting Google+ OAuth scopes. The data below shows which Google+ API methods your projects have recently called, as well as Google+ OAuth scopes it has requested.
Note: If you see calls to people.get, these can be the result of using the Google+ Sign-In feature in your application, which is now fully deprecated and is being shut down. Developers should migrate from the Google+ Sign-In feature to the more comprehensive Google Sign-in authentication system.
Project Google+ API Name Version Method or OAuth Scope
Friendica (friendica-19xxxx) plus v1 plus.activities.list
So, everyone on Nerdica.Net using the Google+ addon: please prepare now that this addon will not work anymore. As advised by Google the shutdown has already started on January 28th.
I'm not sure if Nerdica.Net is already affected or not. I do see some errors like this in the logfile:
2019-02-01T20:21:17Z@40ns7opdru3pcmj7849e2e0lt5 [Info]:CurlResult.php:143:checkSuccess error: https://plus.google.com/.well-known/host-meta: 404 - 2019-02-01T20:21:17Z@40ns7opdru3pcmj7849e2e0lt5 [Info]:CurlResult.php:143:checkSuccess error: http://plus.google.com/.well-known/host-meta: 0 - Recv failure: Connection reset by peer
When I have proof that the G+ addon is not working anymore, I'll deactivate it without any further notice.
There is a small nasty bug in newest Friendica release 2019.01:
When enabling "use browser location" the modal for writing the post doesn't appear
So, when you're using browser location you might not be able to post anything on Nerdica.Net. As a workaround I've followed the tip to disable this function on SQL level:
MariaDB [friendica]> UPDATE user SET `allow_location` = 0 WHERE `allow_location` = 1; Query OK, 10 rows affected (0.01 sec) Rows matched: 10 Changed: 10 Warnings: 0
As you can see there were 10 users affected. In the development branch this bug has already been fixed, but I still await a fixed release version. As soon as this fix is available you should be able to enable "use browser location" again.
As yesterday already pointed out, I worked on enabling XMPP for all Friendica.Net users. A short test showed that this was successful, at least as far as I could test it.
So, what's this XMPP stuff is all about?
What is XMPP?
XMPP, or formerly known as Jabber, is a protocol for instant messaging. You can read the XMPP article in Wikipedia if your interested in details.
XMPP is similar to Friendica in that it is a federated protocol as well as email is. So, there is no central server infrastructure like for Facebook, but basically everyone can run his/her own server, if wanted. But you don't need to! There are hundreds of free XMPP servers out there where you can register an account. As an user of Nerdica.Net you already have an XMPP account with the same address as your Friendica account: <username>@nerdica.net.
How can I use XMPP?
There are multiple options.
1) Within your profile settings you can find XMPP addon in Friendica. Just activate it and enter your login/password again. You'll need to enter the BOSH URL as follows:
2) You can also visit this site which is my main XMPP server on the same server, but a different virtual machine. There you can also enter your Nerdica.Net account in the format of <username>@nerdica.net and your password to login to use an XMPP client in your browser window.
3) On your PC or laptop you can install a XMPP or multiprotocol client like Pidgin, Gajim, Jitsi or whichever client you like. Again, just enter your <username>@nerdica.net and password and have fun!
4) For your mobile usage you can install ChatSecure from Apples AppStore on iOS devices or Conversations from Googles PlayStore. Both a state-of-the-art clients for mobile.
Why should I use XMPP?
You are already using a free, open and federated network when
you use Friendica on this node. You are doing this because you enjoy the benefits of it. Not being dependent from a big company that just want to sell your personal data is a good thing in itself. Google, Facebook and others have also used XMPP for their instant messengers in the past, but decided at some point to close it down and make proprietary messengers out of this to lock you in their own infrastructure. From then on you needed a Google Talk account if you wanted to chat with your friends at Google, or a Facebook account when your friends used Facebooks messenger.
With a free, open and standardized protocol like XMPP you are no longer locked in by a company. Instead you have the freedom to choose the best solution for your secure communication with your friends! Help to keep the Internet free and open by using federated, open and standardized protocols and software!
Ok, but what's the downside of this?
Honestly, I can't imagine of any downside. Maybe the only one is that there is no central directory of contacts and you cannot easily find your friends by looking up their names or phone numbers in an addressbook. But from the privacy aspect viewed even this is more a positive thing.
So, feel free to test it out! You can even have a group chat, a so called multi-user conference (MUC). I've setup on for you at firstname.lastname@example.org - feel free to join!
Mikael Odhage likes this.