Friendica Developers reshared this.
CI currenrly not usable
Hi, I recently tried to increase the woodpecker / ci performance. Unfortunately it dropped the repositories after migrating from sqlite to MySQL as backend. @Tobias re-added it again (thanks 
) but now some settings are still missing.
So currently, the CI isn't working 
I'll be back home at Sunday evening, but I think I will fix it not before Monday/Tuesday..
So if you need to merge new PRs, keep in mind that the files under files.friendi.ca aren't updating ...
Sorry and I'll give an update when it's working again..
like this
utzer [Friendica], Torsten Torsten and Hypolite Petovan like this.
Opensocial.at reshared this.
Geplante Downtime / Server Migration
!Opensocial.at
-- English below
Liebe opensocial.at BenutzerInnen,
Ich starte nun eine Migration von opensocial.at auf eine stรคrkere server-hardware. Dadurch entstehen temporรคre Downtimes in den kommenden Stunden.
Ich mรถchte mich fรผr die Unannehmlichkeiten entschuldigen, aber ich denke, dass dadurch die gesamte Performance von opensocial.at wieder besser werden sollte :).
Lg,
Philipp
----
Dear opensocial.at user,
I'm planning to migrate my server infrastructure onto a more powerful environment.
The goal is to increase the performance, as, I think, you all currently experience a downgrading performance.
I hope it will help :)
It will take some hours, where opensocial.at will be temporary unavailable from time to time.
Regards,
Philipp
friendica.me reshared this.
Planned Downtime / Migration
Dear friendica.me user,
I'm planning to migrate my server infrastructure onto a more powerful environment.
The goal is to increase the performance, as, I think, you all currently experience a downgrading performance.
I hope it will help :)
It will take some hours, where friendica.me will be temporary unavailable from time to time.
Regards,
Philipp
friendica.me reshared this.
--> I will retry again in august
- ich habe deinen Account bei opensocial.at abgelehnt, weil er am selben Server lรคuft wie Friendica.me , mit dem du bereits schon nicht glรผcklich wurdest.. probier libranet.deDer Motzmichel :mastodon: likes this.
#FediBlock*.mastotroll.netz.orgโฒ Admin (of friendica.utzer.de) - 2023-05-03 18:16:56 GMT
New troll domain with many subsomains. This is a strongly recommended block for all #Fediverse services for *.mastotroll.netz.org.Please share this post!
Torsten Torsten likes this.
Friendica Admins reshared this.
Slow photo requests / inbox requests
Hi !Friendica Admins ,
I'm currently tracing down performance issues, I' currently suffering from on my nodes opensocial.at and friendica.me .
It seems like the main performance problems are
- delivering photos
- [code]/inbox/code] requests
You can see some peeks and some long runners here:
The long runners (10sec) are the /inbox requests, the peaks are delivering photos after opening conversations, network pane, ...
Do you have any hints how I could improve these two types of requests?
The database is currently using ~50GB RAM, I set them as high as possible.
Friendica Admins reshared this.
@Hypolite Petovan @Philipp Holzer it's a XFS filesystem on a LVM
Hardware:
- SATA as main storage
- 2x NMVe RAID1 as read/write cache (https://manpages.ubuntu.com/manpages/impish/man7/lvmcache.7.html)
Roland Häder likes this.
Friendica Admins reshared this.
Friendica Admins reshared this.
xdebug and set mode=trace. Then use e.g. kcachegrind to analyze it, e.g. which method takes the most time. That might be a start! Yes, you normally want to have xdebug disabled on live (no development) servers. But this is an exception as high load cannot be simulated properly to find the bottleneck.Philipp Holzer likes this.
Friendica Admins reshared this.
'decoupled_receiver' => true, in your config. Then the inbox requests would be much faster. Then the processing is done via worker processes.like this
Roland Häder and Philipp Holzer like this.
Friendica Admins reshared this.
'avatar_cache' => true,
'avatar_cache_path' => '/path/to/a/folder',But that one is tricky to set up. Best is to store the photos in a folder outside the web folder and then you can define a rule in your webserver that will redirect requests to the avatar folder to that folder.
Roland Häder likes this.
Friendica Admins reshared this.
Friendica Admins reshared this.
Roland Häder likes this.
Friendica Admins reshared this.
Philipp Holzer likes this.
Friendica Admins reshared this.
Friendica Admins reshared this.
/photo/contact route for the avatar cache, don't I?Friendica Admins reshared this.
No, the setup process is completely different. You have to have a path (somewhere) that is both readable and writable by the frontend and backend process
This path needs to be reachable when you call https://your.server.tld/avatar (you have to redirect /avatar) or you have to define avatar_cache_url.
You you setup the file path from above in avatar_cache_path and set avatar_cache to true. After you deactivate the caching of the avatars in the admin frontend, it should work.
The URL path is stored in the contact table fields. So once you defined that URL, you mustn't change it again, since all old requests would fail. This mechanism is powerful, but currently too easy to misconfigure, that's why it is only accessible via the config file.
Friendica Admins reshared this.
Friendica Admins reshared this.
like this
Philipp Holzer and Roland Häder like this.
Friendica Admins reshared this.
https://? That's never a good idea.Friendica Admins reshared this.
seems to work : https://friendica.philipp.info/avatar/4c/a1/d7c/53/8b/f08b/cd3c2904ac0bfd56-300.png?ts=1682970014
This image is now served by a completely different nginx than the frontend nginx . Because it's stateless, I'm now able to start more nginx for "just" serving stateless static content!
Brilliant!
Friendica Admins reshared this.
Philipp Holzer likes this.
Friendica Admins reshared this.
17000 from 59000 finished ;)Michael Vogel likes this.
Friendica Admins reshared this.
avatar/, there are still a lot of long running requests, see the image above. Do you have any idea? The overall CPU/RAM is on a normal state.
Philipp Holzer reshared this.
Friendica 2023.04 released
Content warning: We are very happy to announce the availability of the new stable release of Friendica โGiant Rhubarbโ 2023.04. The highlights of this release are For details, please the CHANGELOG file in the repository. What is Friendica Friendica is a decentralized comm
We are very happy to announce the availability of the new stable release of Friendica โGiant Rhubarbโ 2023.04. The highlights of this release are
- The Mastodon compatible API of Friendica was improved,
- Drag and Drop functionality was added to the Frio theme for image attachments, and
- Christian Pรถschl from usd AG reported a XSS fulnurability in a javascript dependency in the gallery of the Frio theme that was fixed.
For details, please the CHANGELOG file in the repository.
What is Friendica
Friendica is a decentralized communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Tumblr.
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2022.12 release, please first update your Friendica instance to that version as it contained some breaking changes.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently.
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. So, assuming that you are on the stable branch, the commands to update your installation to the 2023.04 release would be
cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull
If you want to use a different branch than the stable one, you need to fetch and checkout the branch before your perform the git pull.
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 from friendica-full-2023.04.tar.gz (sha256) and friendica-addons 2023.04.tar.gz (sha256)) 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-2023.04 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
During the release candidate phase of this release, we had reports that changes to the Tumblr addon combined with PHP version 7.4 might lead a WSoD situation on some pages and connection problems with Tumblr (see 12979 and 13021). These problems could be solved for this release. The Tumblr addon will receive an overhaul in the upcoming release where these issues will be addressed as well.
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!
like this
OldKid, Hypolite Petovan, testing, Steffen K9 ๐ฐ, :jan::abreath:๐ฌ:dandelion:, rewarp, Schmaker, โกThierry Talbert๐ง, Philipp Holzer, Andreas vom Zwenkauer See, rwa, Ercanbrack, Lapo Luchini, error, Wilhelm, Matthias โ, Debbie Goldsmith ๐ณ๏ธโง๏ธ๐ณ๏ธ๐, Paula Gentle on Friendica, Raroun, Joe Slam, Víลฅa Vydra ๐ฉ๐๐ณ๐ดโ ๏ธ, Marc, Damian Wajer, Roland Häder, anubis2814, S_FangX and clacke: looking for something ๐ธ๐ช๐ญ๐ฐ๐๐ like this.
reshared this
Poliverso - notizie dal fediverso, Daniel Siepmann, OldKid, Hypolite Petovan, Fynh, AndiS ๐๐ท๐ช๐บ, MiKlo:~/citizen4.eu$๐๐, Philipp Holzer, Pen² L, error, Wilhelm, Víลฅa Vydra ๐ฉ๐๐ณ๐ดโ ๏ธ, Marc and clacke: looking for something ๐ธ๐ช๐ญ๐ฐ๐๐ reshared this.
I don't really think I'm the first one using that release. ๐คฃ
โฆ
2023.01 (113)
2023.03-dev (14)
2023.03-rc (33)
2023.04 (1)
(it makes sense)
Joe Slam likes this.
rel="me" attribute and points to your user profile on Friendica. Then add a link to your homepage in your profile. https://wiki.friendi.ca/docs/verify_homepage
Friendica Developers reshared this.
Update JSON LD
@Hypolite Petovan already fixed a current JSON-LD issue with https://git.friendi.ca/friendica/php-json-ld/pulls/1
Do we need a 1.1.2 release to upgrade it in the Friendica composer.lock file as well?
The logs of my instances are flooded with this error, that's why I'm asking *g*
Add support for local files for unsecured document loading
- $http_response_header isn't set in the local file read case Address https://github.com/friendica/friendica/issues/12728#issuecomment-1407623586Friendica
like this
Roland Häder and Torsten Torsten like this.
Friendica Developers reshared this.
Philipp Holzer likes this.
Friendica Developers reshared this.
like this
Hypolite Petovan and Roland Häder like this.
Friendica Developers reshared this.
BaseURL components (hostname, SSL policy, urlpath)
I'm currently reducing the whole
BaseUrl.php code massively.Do we really need the ssl_policy, urlpath and hostname separate from the
system.url? I will use for the
BaseUrl.php, based on the system.url a "real" UriInterface as $this->url, so we don't need saving the scheme, urlpath and hostname separately anymore. They are just useful for the install process but must not be changed afterwards.The only thing, which I'm unsure is the
ssl_policy, because if someone changes it afterwards in the admin site, all URL in all contacts and photos will get updated. But the question is => is this even allowed? I think this could brick the access over federation because the base-url of each entry isn't right anymore. And it isn't supported when the policy is changed by console.So I would drop it as well and merge all config entries into the
system.url.Additionally, I will replace the Exception with a "CRITICAL" log entry to avoid a WSOD.
Friendica Developers reshared this.
nurl) so it wouldn't have an impact on Friendica federation.Roland Häder likes this.
Friendica Developers reshared this.
Roland Häder likes this.
Friendica Developers reshared this.
Friendica Developers reshared this.
https://friendica.local you definitely need to ignore SSL/certificate errors because they are mostly only self-signed.Friendica Developers reshared this.
https and there is no check at all in the code that would fail here. It works fine Roland Häder likes this.
Opensocial.at reshared this.
Friendica.me | Opensocial.at Short Downtime because of DB adjustements
I do have to restart the Database instances because they are too resource hungry.
There's a short downtime possible.
friendica.me reshared this.
friendica.me reshared this.
Philipp Holzer reshared this.
Friendica 2023.01 released
Content warning: Christian Pรถschl from usd AG has found another XSS vulnerability in Friendica which is close with this hotfix release of Friendica. In addition some other bugfixes for the distribution of forum postings and improvements to the update process of node infor
Christian Pรถschl from usd AG has found another XSS vulnerability in Friendica which is close with this hotfix release of Friendica.
In addition some other bugfixes for the distribution of forum postings and improvements to the update process of node information are included in this release.
For details, please the CHANGELOG file in the repository.
What is Friendica
Friendica is a decentralized communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Twitter.
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2022.06 release, please first update your Friendica instance to that version as it contained some breaking changes.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently.
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. So, assuming that you are on the stable branch, the commands to update your installation to the 2022.12 release would be
cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull
If you want to use a different branch than the stable one, you need to fetch and checkout the branch before your perform the git pull.
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 from friendica-full-2023.01.tar.gz (sha256) and friendica-addons 2023.01.tar.gz (sha256)) 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-2023.01 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
Regarding the update process none as of writing.
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!
like this
Montag, Philipp Holzer, Cord, Rebeka Catalina, and2099, Gidi Kroon, Hypolite Petovan, superdaigo, don Elías (como los buses) ๐ฅจ, Hans-Peter Gauster, Andreas Kuckartz, Debbie Goldsmith ๐ณ๏ธโง๏ธ๐ณ๏ธ๐, ginAd and Roland Häder like this.
reshared this
Poliverso - notizie dal fediverso, Aboumael โ ๐ป, Alessandro, oigreslima, Philipp Holzer, and2099, Gidi Kroon, Hypolite Petovan, superdaigo and Debbie Goldsmith ๐ณ๏ธโง๏ธ๐ณ๏ธ๐ reshared this.
Philipp Holzer reshared this.
Friendica 2022.12 released
Content warning: We are very happy to announce the avail-ability of the new stable version of Friendica. Wrapping up the sprint from the 2022.10 release of Friendica we closed 73 filed issues and had almost 300 pull requests by 19 contributors. A special thanks goes out t
We are very happy to announce the avail-ability of the new stable version of Friendica. Wrapping up the sprint from the 2022.10 release of Friendica we closed 73 filed issues and had almost 300 pull requests by 19 contributors.
A special thanks goes out to Christian Pรถschl from usd AG and Matthias Moritz who have found a CSRF- and XSS-attack, that is fixed with this release.
In addition to fixing this bug, the highlights of the changes since the 2022.10 release are
- The default theme of Friendica (frio) got many improvements and some old themes got deprecated.
- The calendar saw some improvements and can now be made visible to anonymous visitors.
- The homepage mentioned on the user profile is now automatically verified via the rel-me backlink.
- Images attached to a posting are now shown in a grid at the bottom of the posting.
- A moderation corner was established from the admin panel where a future release will add more moderation tool and bundle them with the current once.
For details, please the CHANGELOG file in the repository.
Since version 2022.06 the lowest required PHP version Friendica needed on the server was raised to PHP 7.3 and PHP 8.0 is supported.
What is Friendica
Friendica is a decentralized communications platform, you can use to host your own social media server that integrates with independent social networking platforms (like the Fediverse or Diaspora*) but also some commercial ones like Twitter.
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2022.06 release, please first update your Friendica instance to that version as it contained some breaking changes.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently.
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. So, assuming that you are on the stable branch, the commands to update your installation to the 2022.12 release would be
cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull
If you want to use a different branch than the stable one, you need to fetch and checkout the branch before your perform the git pull.
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 from friendica-full-2022.12.tar.gz (sha256) and friendica-addons 2022.12.tar.gz (sha256)) 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-2022.12 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
Regarding the update process none as of writing.
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!
like this
ginAd, ะะปะตะบัะฐะฝะดั, and2099, Falgn0n The Wizard, Hans-Peter Gauster, Kristian, elrido, Marc, Iron Bug, Roland Häder, Lex Publica, Andreas vom Zwenkauer See, Raroun, Tio, mrostu, Michael, Marek Bachmann, ts, Hypolite Petovan, Alexander Barton, Paula Gentle on Friendica, Aaron, Wandering Thinker, Philipp Holzer, Philipp Holzer, Steffen K9 ๐ฐ, Joe Slam, Xiku Francesc, Weltraumeindringling, Andy H3, Carmela, John Samuel, Jonathan Blackshire, Salva Pl and usd AG like this.
reshared this
Poliverso - notizie dal fediverso, ricardo :mastodon:, butterflyofZbeul Wéon โ, Wayne Mackintosh ๐ณ๐ฟ๐ง, ะะปะตะบัะฐะฝะดั, Ritinha, wakest, Rag. Gustavino Bevilacqua, Todd FOSS alt :popos:, and2099, Falgn0n The Wizard, Debbie Goldsmith ๐ณ๏ธโง๏ธ๐ณ๏ธ๐, Pen² L, Aaron Winston Smith, ๆฐไธญๅฝๅๅฏ็๐จ๐ณ๐ :emacs: :verified:, HerrThees, Daniel Siepmann, AndiS ๐๐ท๐ช๐บ, halfey โ ๐ฎ๐จ๐ฌ๐ญ๐๐ฒ๐พ๐บ๐ฆ๐น๐ผ, Robin Hüskes, Marek Bachmann, Wandering Thinker, Hypolite Petovan, Wouter, Philipp Holzer, Philipp Holzer, Steffen K9 ๐ฐ, Michael, J. Alfred Prufrock, Hiro :vivaldi_red:, Jonathan Blackshire, Ramon van Belzen and tunda reshared this.
using WP + elementor for my personal home page.
Added rel=me to a link in the page pointing at my #Friendica profile per the elementor instructions.
Not working?
Most likely I am doing it wrong.
Or else - where do I send my $8 to get my blue check!?
rel=โmeโ presence is checked once on profile form submission, and then once a day. Please resubmit the profile edit form first.Thanks.
Didn't seem to do anything.
Don't worry about it, not all that important, just thought I'd try out "the cool new feature"
Falgn0n The Wizard likes this.
But thx - #Friendica is still the best fedi server and updates are a breeze
@Friendica News
like this
Roland Häder and ะะปะตะบัะฐะฝะดั like this.
Roland Häder likes this.
I think your speed experience of old was more based around that specific instance and its configuration (and it is no longer running). My Friendica installation is as quick and responsive as my Akkoma instance.
On the topic of Friendica I was also somewhat surprised to notice the new (beta) app Mammoth is showing my Friendica instance quite well. Surprised especially since Mammoth does not show my Akkoma (i.e. Pleroma) instance (which the app MetaText does though).
@news
However obviously it depends on the instance and how loaded it is.
Also certain operations in Friendica are slower by design compared to some other platforms. E.g. when you post a comment it isn't fired to other servers almost immediately like in Mastodon but is sent on next worker run which typically is every several minutes. In that regard Friendica feels less like chat and more like email :)
Danke Leute !
With a table of pics at the end of the post it'll would look like fucking FB. :(
NOTE: The Apache2 rewrite rule in the .htaccess-dist has been changed.
The change has to be applied manually to the existing .htaccess.
Unfortunately I cannot find any hint about the change? Is this true or has this hint been carried over from the previous update where such changes were described in detail?
@Friendica News
B flag to the RewriteRule.Roland Häder likes this.
First I already have done this. I can even remembver doing it, but not when. This must have been during the previous update. It is only in .htaccess-dist and not .htaccess - right?
And second, where can I find how to do it? Again as stated above, I already did this but can no longer find the howto ... must be me getting older
@Hypolite Petovan
.htaccess-dist must be applied manually by node admins to their respective .htaccess file because we don't have access to them from the official Friendica repository.If you paste the contents of your
.htaccess file, I'll be able to give you the updated version.Roland Häder likes this.
like this
Hypolite Petovan and Roland Häder like this.
like this
Hypolite Petovan and Shallow Water like this.
was raised to PHP 7.3 and PHP 8.0 is supported.
I'd say 8.1 is supported, not sure why you kept 8.0.
@Friendica News
Cฤtฤ likes this.
It's been more than one day already and it's still not showing up the checkmark on my profile here. I wasn't sure if I mistook something or if Gravatar is simply not the right tool for this.
It would show the error in the Friendica log, though, you can grep for "CheckRelMeProfileLink" for more information.
like this
ะะปะตะบัะฐะฝะดั and Cฤtฤ like this.
link HTML tag instead of a and the other has several values in rel attribute - maybe this is what breaks the check?https://github.com/friendica/friendica/issues/12507
Hypolite Petovan likes this.
develop branch with a few modifications. You can see the little check next to my homepage URL.@Hypolite Petovan, It's not my server, I don't know how to access these logs. Is there an option in the settings or anything?
Cฤtฤ likes this.
Thanks for using my profile as a guinea pig, hope this will help others tho.
Hypolite Petovan likes this.
.htaccess file needed to be updated on Apache. If I'm upgrading from 2022.10, do I need to do this still?@Hypolite Petovan
.htaccess file, yes.Jonathan Lamothe likes this.
Friendica Support reshared this.
opensocial.at database data seems corrupt
It seems like I do have a problem with my opensocial.at database
.The database ran full about a year ago (what a shame, I know :( ...) and I had to recover some of the data (otherwise I had to import a backup about ~12hours ago, I tried to avoid to loose posts for this period of time for my users ...). So I stopped it, started it with
innodb_force_recovery=3, repaired it and checked it with mysqlcheck.Two days ago, I updated the mariadb from 1.10.3 to 1.10.10 and now the problems occur again.
I stopped the MariaDB 1.10.3 container, updated it to 1.10.10 and started it again .. And MariaDB started a "crash recovery". I really don't know why... The crash recovery wasn't successfully (I tried it ~4 times), so I had to add
innodb_force_recovery=3 again.Now the database went up, but everytime I stopped it and started it again, the crash recovery appears again.
So after the instance was up and running, I dumped the whole database with
mysqldump into one single *.sql , started a brand new MariaDB 1.10.10 and imported the dump again.So far so good ..
But... unfortunately, after a restart, the crash recovery appears again. So I'm totally lost, what's now happening..
I noticed during the import that one batch of rows took about 2 hours to complete with the result query affected 0 rows.
here's my
customized.cnf, which I'm using (it's a Hetzner root server with 64 GB RAM and 12 CPUs):[mysqld]
query_cache_size = 0
query_cache_type = 0
performance_schema = ON
join_buffer_size = 140M
innodb_buffer_pool_size = 12G
innodb_log_buffer_size = 31M
innodb_log_file_size = 3G
table_open_cache = 1000
max_connections = 400
wait_timeout = 200
interactive_timeout = 4000
log-bin = mysqld-bin
transaction-isolation = READ-COMMITTED
binlog-format = ROW
skip-innodb-read-only-compressed = ON
innodb_read_only_compressed = OFF
innodb_use_native_aio = OFF
innodb_fast_shutdown=0
innodb_max_dirty_pages_pct=0
innodb_buffer_pool_dump_at_shutdown=1
innodb_buffer_pool_load_at_startup=1For the new MariaDB instance, I didn't add any customization to avoid any wrong options.
currently, it makes a recovery again:
db_1 | 2022-12-16 10:41:00 0 [Note] InnoDB: Rolled back recovered transaction 371172
db_1 | 2022-12-16 10:41:11 0 [Note] InnoDB: To roll back: 1 transactions, 7611737 rows
db_1 | 2022-12-16 10:41:26 0 [Note] InnoDB: To roll back: 1 transactions, 7608132 rows
db_1 | 2022-12-16 10:41:41 0 [Note] InnoDB: To roll back: 1 transactions, 7603940 rows
db_1 | 2022-12-16 10:41:46 0 [Note] DDL_LOG: Crash recovery executed 1 entries
db_1 | 2022-12-16 10:41:46 0 [Note] Server socket created on IP: '0.0.0.0'.
db_1 | 2022-12-16 10:41:46 0 [Note] Server socket created on IP: '::'.
db_1 | 2022-12-16 10:41:47 0 [Note] mariadbd: ready for connections.
db_1 | Version: '10.10.2-MariaDB-1:10.10.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
db_1 | 2022-12-16 10:41:56 0 [Note] InnoDB: To roll back: 1 transactions, 7601453 rows
db_1 | 2022-12-16 10:42:11 0 [Note] InnoDB: To roll back: 1 transactions, 7600146 rows
db_1 | 2022-12-16 10:42:26 0 [Note] InnoDB: To roll back: 1 transactions, 7598395 rows
db_1 | 2022-12-16 10:42:41 0 [Note] InnoDB: To roll back: 1 transactions, 7595967 rows
db_1 | 2022-12-16 10:42:56 0 [Note] InnoDB: To roll back: 1 transactions, 7594000 rows
db_1 | 2022-12-16 10:43:11 0 [Note] InnoDB: To roll back: 1 transactions, 7590646 rows
db_1 | 2022-12-16 10:43:26 0 [Note] InnoDB: To roll back: 1 transactions, 7585618 rows
db_1 | 2022-12-16 10:43:41 0 [Note] InnoDB: To roll back: 1 transactions, 7579929 rows
db_1 | 2022-12-16 10:43:56 0 [Note] InnoDB: To roll back: 1 transactions, 7574058 rows
db_1 | 2022-12-16 10:44:11 0 [Note] InnoDB: To roll back: 1 transactions, 7568214 rowslike this
Roland Häder and Torsten Torsten like this.
Friendica Support reshared this.
But not THAT good..
@Michael Vogel do you have any suggestions for me?
Since months, the database time for the
Network page is unusual high as well:Datenbank: 8.827/0, Netzwerk: 0, Darstellung: 0.07, Sitzung: 0, I/O: 0, Sonstiges: 0.32, Gesamt: 9.22
Class-Init: 0.012, Boot: 0.005, Init: 0, Inhalt: 9.205, Sonstiges: 0.002, Gesamt: 9.224At first, I thought it's because of some missing optimizations. But I'm now sure that there's something wrong in the database ...
Torsten Torsten likes this.
Friendica Support reshared this.
Friendica Support reshared this.
[mysqld]
performance_schema = ON
join_buffer_size = 140M
innodb_buffer_pool_size = 46G
innodb_log_buffer_size = 31M
innodb_log_file_size = 3G
table_open_cache = 3000
max_connections = 400
wait_timeout = 200
interactive_timeout = 4000As said, I do have 64 GB RAM, so I chose high values to optimize it as best as possible
Friendica Support reshared this.
Hi Philipp,
im not familiar with the Container Versions of MariaDB, because that version numbers donยดt fit the official "self installed" ones.
Mariadb >10.4 has some weird changes in indexing, which makes the database insanely slow.
You could try to include this into your mariadb.conf:
optimizer_use_condition_selectivity = 1
optimizer_switch='rowid_filter=off'
With this set, the behaviour of Maridb is like the versions before 10.4.
like this
Philipp Holzer and Steffen K9 ๐ฐ like this.
Friendica Support reshared this.
And now it's incredible fast again
Datenbank: 0.137/0, Netzwerk: 0, Darstellung: 0.07, Sitzung: 0, I/O: 0, Sonstiges: 0.07, Gesamt: 0.29
Class-Init: 0.011, Boot: 0.005, Init: 0, Inhalt: 0.268, Sonstiges: 0.002, Gesamt: 0.286Thanks for your help
Friendica Support reshared this.
My guess regarding the permament crash recovery:
When sending the database a shutdown, it flushes erverythin in memory in its files.
Depending on your hardware and database size, this could take a while - iยดve seen databases that took up to 10 minutes to do that.
If your container or OS is shutting down before the process ends, youll get a crash recovery on the next startup.
check if the maridb process is terminated before the container or OS is shut down.
If the databse is correctly shut down and the crash recovery starts again on the next database startup, you could try to remove the MariaDB Log files. The transactions are stored in that files.
You should back them up before removing them, just in case you need a rollback.
i donยดt know your mariadb install locations, but thats what i would do:
1.) systemctl stop mariadb
2.) cd /var/lib/mysql
3.) cp ib_logfile* /tmp
4.) rm -f ib_logfile*
5.) systemctl start mariadb
It is worth a try. but be sure to backup ib_logfile* first and do a database dump - better be safe than sorry.
After that procedure, no crash recovery will happen, because theres nothing to recover.
Philipp Holzer likes this.
Friendica Support reshared this.
I analyzed the shutdown process and found:
db_1 | 2022-12-16 21:10:26 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
db_1 | 2022-12-16 21:10:26 0 [Note] InnoDB: FTS optimize thread exiting.
db_1 | 2022-12-16 21:10:26 0 [Note] InnoDB: Starting shutdown...
db_1 | 2022-12-16 21:10:26 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
db_1 | 2022-12-16 21:10:26 0 [Note] InnoDB: Restricted to 746368 pages due to innodb_buf_pool_dump_pct=25
db_1 | 2022-12-16 21:10:26 0 [Note] InnoDB: Buffer pool(s) dump completed at 221216 21:10:26
opensocial_db_1 exited with code 137But "Exit 137" isn't a normal exit, it indicates a "OOM" shutdown.
like this
Roland Häder and Raroun like this.
Friendica Support reshared this.
Iโm sorry, I donโt use docker and I am not familiar with it - but that Exit Code looks like a good hint to start with :)
Philipp Holzer likes this.
Friendica Support reshared this.
Friendica Support reshared this.
Philipp Holzer likes this.
Friendica Support reshared this.
And you ran mysqlcheck -A -o I guess?
Philipp Holzer likes this.
Friendica Support reshared this.
Raroun likes this.
Philipp Holzer reshared this.
I'm not used to do this, but with the large influx of new users and node admins recently coming from #Twitter, our small team is now behind the curve for handling support requests, bug reports and bring about much-needed features.
The project is built on a #PHP / #MySQL platform, but we also need people to be able to assist others just using the software to give developers some space.
If you're willing and able to help, please follow @Friendica Support and the project on Github: https://github.com/friendica/friendica
Thank you!
GitHub - friendica/friendica: Friendica Communications Platform
Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.GitHub
like this
Roland Häder, Philipp Holzer and Matthias Moritz like this.
reshared this
Robert Lender, Griff Ferrell ๐๐, clacke: looking for something ๐ธ๐ช๐ญ๐ฐ๐๐, Lohan Gunaweera, servisoficial ๐ฒ๐ฝ๐ท๐บ, Alecu ศtefan-Iulian :verified:, Mehrad :kdenew: :emacs: ๐ช๐บ, Tagomago, Jon W, wakest, marcelcosta, Wirry Loberts, Thomas Cloer ๐ช๐บ ๐บ๐ฆ, polarity :wig:, poetaster, Salvatore detto Rino, Rag. Gustavino Bevilacqua, Roland Häder, Pirate Bady, asdf, Leo, rewarp, Blume, die, #WikiParty, Artur Weigandt, Carsten Raddatz, daaitoulaam, Tamanna, ํฌ์ค aka ์ํ ๐ฅ, Paula Unger, โด๏ธPsส-๐๐ก๐๐๐๐ค๐ชฌ, Phillip Jordan, SeigeA, Le Général Midi, Philipp Holzer, Matthias Moritz and jay ๐บ:disabled_heart: reshared this.
I'm trying to do posts introducing people to platforms besides Mastodon. but I don't want to direct people there if it makes situation worse?
No worries if you are overwhelmed, many other projects are too!
Friendica Support reshared this.
Friendica Support reshared this.
@Hypolite Petovan what will be best practice to get started to support developers? Unfortunately, I not that much experience in open source community social culture. I guess participating the discussion on the git site?
Friendica Support reshared this.
Yes! Open source community social culture is pretty much "do what you can on your own". Even inaccurate answers are better than no answer at all. Adding your support for new features or enhancements go a long way to motivate developers, acknowledging bug reports is good etiquette, and assisting support requests by gathering as much details as possible often helps troubleshoot the issue.Finally, correcting existing documentation or guides or writing updated ones is absolutely stellar.
Roland Häder likes this.
Friendica Support reshared this.
Friendica Support reshared this.
Well same here. My PHP knowledge of 2003 to 2007 is completely outdated. The last thing I did was porting the application I wrote at that time from PHP5 to PHP7, but that is some 6 or 7 years back, too. Since then I didn't write a single line of code in PHP anymore.
Friendica Support reshared this.
then see it as a challenge and you are never too old to start hitting the keys again
@Hypolite Petovan @Jonathan Lamothe (he/him) โ
Friendica Support reshared this.
Friendica Support reshared this.
I don't want to say that again, that the code base is very complex. I rather thought that you can not only win people over for the code here, but that there are some tasks, as you have already listed.
I have to say I've looked at the code quite a few times and I haven't really gotten through what works where, how and why the way it works. Although I do daily development with my own applications based on PHP.
If I were to join at some point, I see the junior jobs as a starting point, as you have often described, and then ideally as an encapsulated development without any problems that can arise with the core.
Start slowly and feel your way and not from 0 to 100 and then cause chaos all over the core. Because it's always such a thing with self-developed applications where you can already understand the workflow in your head and in contrast to other developed software that still evokes many dark corners in your head.
That's why I understand your post and I think I'll hold back there, also to motivate people here, to screw the code base is not trivial and only people who have been doing this for a long time should do it. Because a broken Friendica is of no use to anyone.
best wishes
@Jonathan Lamothe (he/him) โ @ITMC GmbH
Friendica Support reshared this.
Hypolite Petovan likes this.
Friendica Support reshared this.
this should be good - but as i understand hypolite@friendica.mrpetovan.com
it is better not to change the code if you are not firm with it.
@Jonathan Lamothe (he/him) โ
Friendica Support reshared this.
Friendica Support reshared this.
Opensocial.at reshared this.
Philipp Holzer
•Leider hat die Migration nicht geklappt und ich musste wieder zurรผckrollen.
--> Ich probiere es im August noch einmal
---
Unfortunately, the migration didn't work so I had to rollback.
--> I will retry again in august
Norz Tekh ๐ณ๏ธ๐ likes this.
Opensocial.at reshared this.
Torsten
•