2023-02-21 21:07:46
2023-02-21 20:21:41
2023-02-21 20:21:41
6832930
Friendica Developers reshared this.
Update JSON LD
!Friendica Developers
@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*
@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.
2023-02-19 06:45:58
2023-02-15 19:27:25
2023-02-15 19:27:25
6801213
Friendica Developers reshared this.
BaseURL components (hostname, SSL policy, urlpath)
!Friendica Developers
I'm currently reducing the whole
Do we really need the ssl_policy, urlpath and hostname separate from the
I will use for the
The only thing, which I'm unsure is the
So I would drop it as well and merge all config entries into the
Additionally, I will replace the Exception with a "CRITICAL" log entry to avoid a WSOD.
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.
@Philipp Holzer This sounds good, internally we don't make a difference between HTTP and HTTPS URLs for remote servers (thanks to the
nurl) so it wouldn't have an impact on Friendica federation.Roland Häder likes this.
Friendica Developers reshared this.
The SSL-Policy was a thing of ancient times where you could define if you had a self certified certificate, a real one or none. There had been some code around this. Just have a look if this is used somewhere.
Roland Häder likes this.
Friendica Developers reshared this.
@Michael Vogel @Philipp Holzer the self-signed cert thing is important for the VagrantVM IIRC
Roland Häder likes this.
Friendica Developers reshared this.
@Tobias I'm not sure what wouldn't work with a self-signed certificate. Unless we are checking the CA for self-requests, but I'm not sure the legacy SSL Policy configuration value is about that.
Friendica Developers reshared this.
@Philipp Holzer For a local installation, like
https://friendica.local you definitely need to ignore SSL/certificate errors because they are mostly only self-signed.Friendica Developers reshared this.
I know and I'm using local Vagrant with 
https and there is no check at all in the code that would fail here. It works fine like this
Roland Häder and Tobias like this.
2023-02-15 18:36:08
2023-02-15 17:41:21
2023-02-15 17:41:21
6800555
Opensocial.at reshared this.
Friendica.me | Opensocial.at Short Downtime because of DB adjustements
!friendica.me , !Opensocial.at
I do have to restart the Database instances because they are too resource hungry.
There's a short downtime possible.
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.
2023-01-16 21:05:17
2023-01-15 11:58:15
2023-01-15 11:05:31
6588070
![utzer [Friendica]](photo/contact/80/426?ts=1680015070)
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.
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.
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.
Ensure that the last backup of your Friendica installation was done recently.
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
cd friendica
git pull
bin/composer.phar install --no-dev
cd addon
git pull
If you want to use a different branch than the
Pulling in the dependencies with composer will show some deprecation warning, we will be working on that in the upcoming release.
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
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.
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.
Regarding the update process none as of writing.
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!
https://friendi.ca/2023/01/15/friendica-2023-01-released/
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 becd 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!
https://friendi.ca/2023/01/15/friendica-2023-01-released/
Friendica 2023.01 released
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 thestablebranch, 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 thestableone, 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 (sayfriendica_new) and copy over your existing configuration (config/local.config.phpandconfig/addon.config.php) and.htaccessfiles. Afterwards rename your current Friendica directory (e.g. friendica) tofriendica_oldandfriendica_newtofriendica.
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!
https://friendi.ca/2023/01/15/friendica-2023-01-released/
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 ๐ณ๏ธโง๏ธ๐ณ๏ธ๐ and ginAd like this.
reshared this
Poliverso - notizie dal fediverso, Aboumael, Alessandro ้ฟๅๆกๅพท็ฝ, oigreslima, Philipp Holzer, Tobias, and2099, Gidi Kroon, Hypolite Petovan, superdaigo, Debbie Goldsmith ๐ณ๏ธโง๏ธ๐ณ๏ธ๐ and As The World Turns reshared this.
2023-01-12 00:30:02
2022-12-20 19:18:56
2022-12-20 06:11:29
6399305
I'd say 8.1 is supported, not sure why you kept 8.0.
@Friendica News
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, Andreas Kilgus, Weltraumeindringling, andy, Wilhelm, Carmela, John Samuel, Jonathan Blackshire and Salva Pl like this.
reshared this
ricardo :mastodon:, butterflyoffire :mastodon:, 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, Andreas Kilgus, 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!?
This entry was edited (3 months ago)
@Falgn0n The Wizard The
rel=โmeโ presence is checked once on profile form submission, and then once a day. Please resubmit the profile edit form first.@Hypolite Petovan
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"
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 I beg to differ, I can see the checkmark next to your homepage link in your profile card!
Falgn0n The Wizard likes this.
@Hypolite Petovan strange I don't see it (yet?)
But thx - #Friendica is still the best fedi server and updates are a breeze
@Friendica News
But thx - #Friendica is still the best fedi server and updates are a breeze
@Friendica News
@Falgn0n The Wizard There it is:
This entry was edited (3 months ago)
like this
Roland Häder and ะะปะตะบัะฐะฝะดั like this.
How is the speed of Friendica these days? Has it improved at all in the last year?
Roland Häder likes this.
@ercanbrack
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
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
Depends how you define speed. I run my instance for several years now and I think Friendica became much faster and easier on server resources in last three or so versions.
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 :)
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 :)
Ach Quatsch, heute Abend. Ich habe doch so eine schรถne VM-Infrastruktur ! SnapShot machen und schon konnte das Update durchrutschen. Danach noch 5 Minuten das DB-Update abwarten und schon ist die "Zwenkauer Flaschenpost" wieder aktuell.
Danke Leute !
Danke Leute !
Jetzt muร ich aber erst mal gucken was alles neu ist 
So, when you create a post, you won't be able to insert images between text like you do now? If so, that's a very bad idea... A good idea would be to insert images where the cursor is.
With a table of pics at the end of the post it'll would look like fucking FB. :(
With a table of pics at the end of the post it'll would look like fucking FB. :(
The changelog states the following:
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
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
@AndiS ๐๐ท๐ช๐บ No, this is current to this release. You have to add a
B flag to the RewriteRule.Roland Häder likes this.
Interesting!
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
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
@AndiS ๐๐ท๐ช๐บ The change we added to
If you paste the contents of your
.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.This entry was edited (3 months ago)
Roland Häder likes this.
Ah, yes! Understood. No worries, I just copied the .htaccess-dist file over .htaccess since I never changed that one myself. Thank you for clearing that up! @Hypolite Petovan
like this
Hypolite Petovan and Roland Häder like this.
Update went smooth as ever. Big thanks to all!
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
@utzer ~Friendica~ You still had deprecated notice messages a few days before the release, I wouldn't say it's done and dusted.
@Friendica News What format should the rel-me backlink have? I tried using the same format as on Mastodon, and it does not seem to work (probably because I am using a specific service)
@Cฤtฤlin Petrescu @Friendica News It is the same expected format as on Mastodon. However, the verification isnโt immediate and its result when successful is rather discreet (a checkbox next to the homepage URL in the profile information in the left column).
Cฤtฤ likes this.
@Hypolite Petovan @Friendica News I see. I got no personal webpage to try, so I checked all the options I had in order not to create an additional account somewhere just for this. So I found that Gravatar also provides Mastodon verification and decided to try it out here as well.
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'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.
@Cฤtฤlin Petrescu It looks good on both your profile and the Gravatar page. Please try to update your profile settings even if you do not change any field. This will queue a verification task for the worker to pick up.
I also don't see the checkmark in your Friendica profile but see it on Gravatar page :)
@ะะปะตะบัะฐะฝะดั @Cฤtฤlin Petrescu I don't see it either, grmbl.
It would show the error in the Friendica log, though, you can grep for "CheckRelMeProfileLink" for more information.
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.
I did some testing on my server and seems some links indeed don't pass verification. Perhaps the parser is too strict. I noticed that one of non-working links has
https://github.com/friendica/friendica/issues/12507
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.
@ะะปะตะบัะฐะฝะดั @Hypolite Petovan @Cฤtฤlin Petrescu It worked here as well, I'm on
develop branch with a few modifications. You can see the little check next to my homepage URL.@ะะปะตะบัะฐะฝะดั @Cฤtฤlin Petrescu Yes, and it's a quick fix for anyone who wants Open Source fame and fortune!
That's what I was trying to point out :D Thanks, @ะะปะตะบัะฐะฝะดั!
@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?
@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ฤlin Petrescu @ะะปะตะบัะฐะฝะดั No worries, once the related GitHub issue is resolved, the node you're on will be soon be updated and you'll be able to re-run the check again, hopefully with success this time.
Cฤtฤ likes this.
@Hypolite Petovan @ะะปะตะบัะฐะฝะดั Thanks. For now I tried to change the link and modify it a couple of times, however gravatar seems to have some limits in the number of verifications, so I failed verification on Gravatar as well now, haha.
Thanks for using my profile as a guinea pig, hope this will help others tho.
Thanks for using my profile as a guinea pig, hope this will help others tho.
Hypolite Petovan likes this.
news@forum.friendi.ca I remember the 2022.12-rc version saying that the
.htaccess file needed to be updated on Apache. If I'm upgrading from 2022.10, do I need to do this still?@Jonathan "Mastodon" Lamothe Yes, very much so. It only affects one specific API call, but it would be difficult to troubleshoot.
@Jonathan "Mastodon" Lamothe just pull/update and then quickly look in the shipped .htaccess-dist or so and there is a rewrite rule line with an additional B compared to your current version, so only one capital letter B needs to be added.
@Hypolite Petovan
@Hypolite Petovan
@Jonathan "Mastodon" Lamothe @utzer ~Friendica~ If you didn't add any changes to your local
.htaccess file, yes.Jonathan Lamothe likes this.
@Hypolite Petovan Out of curiosity, is there a reason I would have manually changed it?
2022-12-17 18:28:10
2022-12-16 11:07:34
2022-12-16 11:07:34
6356961
Friendica Support reshared this.
opensocial.at database data seems corrupt
!Friendica Support
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
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
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
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
For the new MariaDB instance, I didn't add any customization to avoid any wrong options.
currently, it makes a recovery again:
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.
at least the instance is up and running again.
But not THAT good..
@Michael Vogel do you have any suggestions for me?
Since months, the database time for the
At first, I thought it's because of some missing optimizations. But I'm now sure that there's something wrong in the database ...
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.
This long loading normally is a sign of - for example - assigning too few memory to the SQL server.
Friendica Support reshared this.
I changed it back to my original settings:
As said, I do have 64 GB RAM, so I chose high values to optimize it as best as possible
[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.
@Philipp Holzer
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.
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.
This entry was edited (3 months ago)
like this
Philipp Holzer and Steffen K9 ๐ฐ like this.
Friendica Support reshared this.
I added these two settings and increased the nproc/nofile to 102400
And now it's incredible fast again
Thanks for your help
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.
@Philipp Holzer
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.
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.
This entry was edited (3 months ago)
Philipp Holzer likes this.
Friendica Support reshared this.
OK thanks for your suggestions, I think @Raroun is right with the unclean shutdown.
I analyzed the shutdown process and found:
But "Exit 137" isn't a normal exit, it indicates a "OOM" shutdown.
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.
Yep, itโs a OOM sigkill from docker.
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 :)
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.
@Philipp Holzer did you run the mysql update? I forgot the exact command but can look it up tomorrow before noon.
Friendica Support reshared this.
@Philipp Holzer ah, just read it is running again.
Philipp Holzer likes this.
Friendica Support reshared this.
@Philipp Holzer yes, that is what I mean. I forgot that one time.
And you ran mysqlcheck -A -o I guess?
And you ran mysqlcheck -A -o I guess?
Philipp Holzer likes this.
Friendica Support reshared this.
Wow, now it's super fast... thanks for the work. Do you have a way to receive donations?
Raroun likes this.
2022-12-04 21:36:49
2022-12-01 22:18:04
2022-11-16 16:46:53
5938452
Philipp Holzer reshared this.
#Friendica needs new contributors!
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!
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
This entry was edited (4 months ago)
like this
Roland Häder, Philipp Holzer and Matthias Moritz like this.
reshared this
Robert Lender, Griff Ferrell ๐๐ friendica, clacke: seeking ๐ธ๐ช๐ญ๐ฐ๐๐, 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, Tim, โด๏ธPsส-๐๐ก๐๐๐๐ค๐ชฌ, Phillip Jordan, SeigeA, Le Général Midi, Philipp Holzer, Matthias Moritz and jay ๐บ reshared this.
Hey, I meant to ask, do you want a shoutout or is the project being overwhelmed with users at moment?
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!
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.
@Fedi.Tips Thank you for asking, we're a bit swamped at the moment, so I feel like a shoutout would be better after the upcoming release slated for December/early January. If you follow me you'll hear about it.
Friendica Support reshared this.
Still learning a lot about #Friendica and the #fedivers myself. But I'll be always happy to help others, and maybe I'll be able to also contribute some day. The vision of an open, noncommercial decentralized social network is worth the effort.
@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?
@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.
@">Marek Bachmann 
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.
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.
@Hypolite Petovan Sadly, my PHP experience is very limited. I haven't really used it since the 00s. Am happy to help with the answering of general questions, though.
Friendica Support reshared this.
@Jonathan Lamothe (he/him) โ @Hypolite Petovan
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.
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.
@ITMC GmbH
then see it as a challenge and you are never too old to start hitting the keys again
@Hypolite Petovan @Jonathan Lamothe (he/him) โ
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.
@7homas โ @Jonathan Lamothe (he/him) โ @ITMC GmbH As much as I appreciate you trying to motivate people to contribute code, the Friendica codebase has reached a point where it is probably out of reach of amateurs and requires the attention of professional developers like Michael, Philip and I all are.
Friendica Support reshared this.
@Hypolite Petovan
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
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
This entry was edited (4 months ago)
Friendica Support reshared this.
@7homas โ @Jonathan Lamothe (he/him) โ @Hypolite Petovan Completely agree โ but not before sometime in 2024 when I will retire. Until then I'm managing a network restructuring project of a financial institution which keeps me fully occupied. Sorry. Really would like to contribute.
Hypolite Petovan likes this.
Friendica Support reshared this.
@ITMC GmbH
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) โ
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.
@7homas โ @Jonathan Lamothe (he/him) โ Completely agree again. But I think, in 2024 I'm so familiar with Friendica, that I'm able to write an extensive FAQ for administrators โ which is still missing nowadays, AFAIK. ๐
Friendica Support reshared this.
@ITMC GmbH Please do, documentation is crucial and we developers lack the, erm, time to reliably contribute to it!
Friendica Support reshared this.
@Hypolite Petovan
What can they do in the Friendica project? :thinking face:
My technical background is that I have been writing some web applications for the company since about 2000 with PHP (from version 3), mySQL/MariaDB and Postgres. I also use JavaScript and HTML, and since version 2.x Smarty as a template engine.
In addition, I used to write scripts with Perl and now 99.9% with Python. :smiling face with smiling eyes:
Version management used to be in Subversion and since GIT has been around, only in GIT, but since Github was taken over by Microsoft, I don't use the service anymore, I host it myself first with Gogs and then with Gitea. :thinking face:
What can they do in the Friendica project? :thinking face:
My technical background is that I have been writing some web applications for the company since about 2000 with PHP (from version 3), mySQL/MariaDB and Postgres. I also use JavaScript and HTML, and since version 2.x Smarty as a template engine.
In addition, I used to write scripts with Perl and now 99.9% with Python. :smiling face with smiling eyes:
Version management used to be in Subversion and since GIT has been around, only in GIT, but since Github was taken over by Microsoft, I don't use the service anymore, I host it myself first with Gogs and then with Gitea. :thinking face:
Friendica Support reshared this.
@7homas โ
What can they do in the Friendica project?
- On the GitHub project page, we have a few issues labeled as "Junior Jobs".
- The official wiki has outdated information. @Tobias can grant write access to it.
- Even the embarked documentation could use an overhaul, it's stored in the project files but it's mostly Markdown so no need for a technical background.
- Support requests on GitHub are often lacking context information, asking for it ahead of a developer would be appreciated.
- Mutual aid on the @Friendica Support forum goes a long way, it's already pretty active in German, a little less so in English.
GitHub - friendica/friendica: Friendica Communications Platform
Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.GitHub
cyia reshared this.
Friendica Support reshared this.
@Hypolite Petovan
Thank you very much,
these are all interesting areas, but I see this is all going towards Github and having to set up an account there. (This is a noGo as long as Microsoft owns it).
I'll have a look at the wiki (there's also a gitea linked, but that's probably not actively used anymore or?) and especially the forum, if I can help there.
Thank you for the quick answer and the collection of information.
@Tobias
Thank you very much,
these are all interesting areas, but I see this is all going towards Github and having to set up an account there. (This is a noGo as long as Microsoft owns it).
I'll have a look at the wiki (there's also a gitea linked, but that's probably not actively used anymore or?) and especially the forum, if I can help there.
Thank you for the quick answer and the collection of information.
@Tobias
Friendica Support reshared this.
@7homas โ Gitea is still the goal to move to, currently it's a mirror of GitHub but once we figure out the Continuous Integration on Gitea (hi @Philipp Holzer !), we should be able to fully migrate.
Friendica Support reshared this.
@Hypolite Petovan
Good idea with Gitea, I only use it for my own projects. But there are not several users working on it.
But it should bring everything what you have on Github too, except the eyes of Microsoft.
@Philipp Holzer
Good idea with Gitea, I only use it for my own projects. But there are not several users working on it.
But it should bring everything what you have on Github too, except the eyes of Microsoft.
@Philipp Holzer
Friendica Support reshared this.
@7homas โ We started the migration process a while ago, but the continuous integration has proven difficult to move over.
Friendica Support reshared this.
@Hypolite Petovan
It is a pity that this process has not gone further. Many of the large projects have turned their backs on Github for the same reasons.
Thus, it would probably also be time to set a sign here and if an own system is already available, then this is even easier.
Of course, I can not say how difficult it is to move the messages and then take over, or whether you have to make a cut, etc..
It is a pity that this process has not gone further. Many of the large projects have turned their backs on Github for the same reasons.
Thus, it would probably also be time to set a sign here and if an own system is already available, then this is even easier.
Of course, I can not say how difficult it is to move the messages and then take over, or whether you have to make a cut, etc..
Friendica Support reshared this.
@7homas โ We will make an announcement when we finally switch over. But I'm not expecting an uptick in activity when it happens. What we'll gain in privacy-conscious contributors, we'll probably lose in existing GitHub users who don't want to make the effort to create yet another account to submit their support request/bug report/new feature.
Friendica Support reshared this.
@Hypolite Petovan
Of course, if you look at it that way, that could be a fact.
It is difficult to weigh that of course, what it brings but I must say, for me and I refer now 100% to my ideas and not to the project set the data protection very high. For this reason, I also use as a messenger, for example, no Whatsapp but only Threema, Signal or Matrix.
But that's another topic and not this one.
Let's see what the future brings.
Of course, if you look at it that way, that could be a fact.
It is difficult to weigh that of course, what it brings but I must say, for me and I refer now 100% to my ideas and not to the project set the data protection very high. For this reason, I also use as a messenger, for example, no Whatsapp but only Threema, Signal or Matrix.
But that's another topic and not this one.
Let's see what the future brings.
Friendica Support reshared this.
We have to distinguish between the "normal" upstream branch and the Docker images I maintain.
For the upstream branch, I don't see any impediments anymore. It's fully merged to Woodpecker as CI/CD and most of the time, it's working fine
For the Docker images, it's really hard currently. Because I use a "standard" CI/CD action script/binaries from the Docker maintainers themself and they hardly relay on Github. Currently it's not possible to automatically test the Docker images. And as "official" and "best practice" Docker image, as Friendica is part of, we need a github repository to relay on (but we could make a "mirror" repo, so that's not a real issue :) )
For the upstream branch, I don't see any impediments anymore. It's fully merged to Woodpecker as CI/CD and most of the time, it's working fine
For the Docker images, it's really hard currently. Because I use a "standard" CI/CD action script/binaries from the Docker maintainers themself and they hardly relay on Github. Currently it's not possible to automatically test the Docker images. And as "official" and "best practice" Docker image, as Friendica is part of, we need a github repository to relay on (but we could make a "mirror" repo, so that's not a real issue :) )
Friendica Support reshared this.
@Philipp Holzer Great news, when can we migrate the upstream repo and leave a mirror on GitHub?
Friendica Support reshared this.
Gib es irgendwo ein Howto fรผr eine Entwicklungsumgebung? Reicht es einfach, lokal Friendica zu installieren und eine "Wegwerf Domain" drauf zu werfen? Oder nutzt ihr dann eine localhost Oder wie entwickelt und testet ihr lokal?
Wรผrde mir gerne mal ein paar "Junior" Issues ansehen, um damit in den Code zu kommen und dann potentiell mehr zu machen. :)
Wรผrde mir gerne mal ein paar "Junior" Issues ansehen, um damit in den Code zu kommen und dann potentiell mehr zu machen. :)
Friendica Support reshared this.
@grischa Answering in English. I have a second Friendica node at https://dev-friendica.mrpetovan.com where I test all my developments. I would advise against localhost since you wouldn't be able to test any federation feature.
Friendica Support reshared this.
Sorry, didn't get the helper mention, I'll switch to Englisch, too.
Hmm.. But do you develop on that server directly or how is your coding environment? How do you debug, when it s not your local machine? Remote debugging?
Hmm.. But do you develop on that server directly or how is your coding environment? How do you debug, when it s not your local machine? Remote debugging?
Friendica Support reshared this.
@grischa I use JetBrains phpStorm as my IDE. It has a Deployment feature where it keeps an SFTP connection open with my remote server, and any file changed locally is updated on my server as well.
I am a little ashamed to admit I don't know how to use remote debugging, so I just output/log data through the code during my work, and clean up the debugging stuff before committing my work on Git.
I am a little ashamed to admit I don't know how to use remote debugging, so I just output/log data through the code during my work, and clean up the debugging stuff before committing my work on Git.
Friendica Support reshared this.
Okay, I am using phpStorm, too. But I never saw that sync feature, maybe because I didn't use it yet, because I develop my server software local normally..
Debugging would be very helpful, but maybe it works without.
Okay, thanks for that input, I will try something. :)
(I could point a real domain to my local server maybe?)
Debugging would be very helpful, but maybe it works without.
Okay, thanks for that input, I will try something. :)
(I could point a real domain to my local server maybe?)
Friendica Support reshared this.
@grischa I'm not sure how you would point a domain to a local machine but it should be possible. Let me know if you want me to test federation with your dev setup once you're done!
Friendica Support reshared this.
Thanks for that offer! ๐
But I am running a Pleroma and a Hubzilla instance on my own, so I guess this is enough for testing whether federation works.
I'll come back to you, if it doesn't.. ๐
But I am running a Pleroma and a Hubzilla instance on my own, so I guess this is enough for testing whether federation works.
I'll come back to you, if it doesn't.. ๐
Friendica Support reshared this.
@Hypolite Petovan @grischa
If you are developing locally you could get a dyndns domain or something that points to your home router.
This then simply reverse proxy to your local system should actually be an idea for this.
Of course easier if you do the development via SFTP on your server and you also exclude any other bugs.
If you are developing locally you could get a dyndns domain or something that points to your home router.
This then simply reverse proxy to your local system should actually be an idea for this.
Of course easier if you do the development via SFTP on your server and you also exclude any other bugs.
Friendica Support reshared this.
If it helps, @grischa, I run a Knot authoritative DNS server which you can use to update your record dynamically if you prefer your own domain. Cc: @hypolite and @zwovierzwo
Friendica Support reshared this.
Thanks for that offer. ๐
But my DNS is at INWX, they already have the DynDNS feature. Never tested it yet, but it should work as they even document how I have to configure it with my FritzBox (https://kb.inwx.com/de-de/8-dyndns). ๐
But my DNS is at INWX, they already have the DynDNS feature. Never tested it yet, but it should work as they even document how I have to configure it with my FritzBox (https://kb.inwx.com/de-de/8-dyndns). ๐
Friendica Support reshared this.
@Hypolite Petovan I have setup a local #Apache and added an entry to
/etc/hosts to point to my local machine. Then in a /etc/apache2/sites-available/friendica.conf I setup a virtual host on that host name and even setup a self-signed SSL certificate so I can run #Friendica locally. To be able to receive mails locally, as I have #Linux running here, I had to a bit patch Friendica to disable a regex check on the entered email address. Now when I want to locally federate with e.g. #GNUSocial I just have to repeat above steps and I remember I was able to setup "remote" follow between these two local instances. For Windows users, there is #WinAMP around for a very long time, including #Mercury mail server so you could be able to repeat it even on Windows.Friendica Support reshared this.
@Hypolite Petovan So in the end, I don't have to sync my files with my server by SFTP, I just develop locally and independently from my server and when I'm finished with my changes, I do the usual stuff, like pushing them on my server (see https://git.mxchange.org/?p=friendica.git;a=summary ) and pulling from there through local file access.
Friendica Support reshared this.
@Hypolite Petovan True you can leave out the
/etc/hosts part and just access it through, e.g. https://localhost/friendica/ and set RewriteBase /friendica/ accordingly. With the separate host name you also have a separate error.log and access.log so it won't mix with other installations on your local machine.Friendica Support reshared this.
@grischa @tobias @zwovierzwo
i'm using DDEV for local development. I've fired up Friendica within 5 minutes with the bonus that the whole config can be added to git. No more "works on my machine" as everybody is using the same config.
i'm using DDEV for local development. I've fired up Friendica within 5 minutes with the bonus that the whole config can be added to git. No more "works on my machine" as everybody is using the same config.
grischa likes this.
Friendica Support reshared this.
Never heard about DDEV before, but found their website by searching. Thanks for that hint! I will have a look at it (atm I don't even know what it does, seems to be docker related).
Friendica Support reshared this.
@grischa @tobias @zwovierzwo
Yes. But there is defacto no docker knowledge needed. Everything you need to know is written down in the config.yaml which is located in the .ddev folder.
Check my commit here: https://github.com/Schnoop/friendica/commit/7a39be8270c1ce56c7a2df078bfbfd310601c569
Yes. But there is defacto no docker knowledge needed. Everything you need to know is written down in the config.yaml which is located in the .ddev folder.
Check my commit here: https://github.com/Schnoop/friendica/commit/7a39be8270c1ce56c7a2df078bfbfd310601c569
DDEV and some PHP8.1 fixes. ยท Schnoop/friendica@7a39be8
Friendica Communications Platform. Contribute to Schnoop/friendica development by creating an account on GitHub.GitHub
grischa likes this.
Friendica Support reshared this.
I had a plan on doing a documentation rewrite, and then was hit by a pandemic - I think I have approximately 20 minutes a week to commit to it - but maybe that's unfair - I have about a month of vacation coming up and I will try to commit some time
Friendica Support reshared this.
@silverwizard Please start small, Rome, a day, etc... If you have more ambitious plans, please present them to other people to garner support.
Friendica Support reshared this.
Remote Debugging with PHPstorm works very will. You'll need an ssh tunnel to the Tunnel and a mirror of the folders on the Server on your local drive.
here is a tutorial
here is a tutorial
Friendica Support reshared this.
@Raroun Thanks, I know it's possible but I've never included remote debugging in my toolbox so I don't even know when it would be warranted or not.
Friendica Support reshared this.
But this only works, when the remote server supports XDebug, right? This is not the case in too much environments, I guess.. ๐ค
Friendica Support reshared this.
Sadly, yes :(
I work with my own servers, so it wasnโt a problem for me to set it up :)
I work with my own servers, so it wasnโt a problem for me to set it up :)
Friendica Support reshared this.
@grischa I have XDebug installed on my remote server, I use it for more verbose error messages and also for the profiler, but not for remote debugging.
Friendica Support reshared this.
@Andreas Kilgus What do you mean by "the big picture of Friendica" ?
Friendica Support reshared this.
@Tobias
For what the write access I think I'm a bit on the line. The forum I can also comment so or not?
For what the write access I think I'm a bit on the line. The forum I can also comment so or not?
Friendica Support reshared this.
@Hypolite Petovan
another question at this point.
Does a kind of Kanban board exist for tasks that are pending or would that perhaps be a solution for development and the tasks that are currently being completed or should still be developed?
In my office, we have had relatively good experiences with this - for example, we have Taiga running here.
another question at this point.
Does a kind of Kanban board exist for tasks that are pending or would that perhaps be a solution for development and the tasks that are currently being completed or should still be developed?
In my office, we have had relatively good experiences with this - for example, we have Taiga running here.
clacke: seeking ๐ธ๐ช๐ญ๐ฐ๐๐ likes this.
Friendica Support reshared this.
@7homas โ No we don't have any sort of product management. No requirements, no schedule (apart the 3 months release schedule), no task list besides the GitHub issue tracker.
Friendica Support reshared this.
@Hypolite Petovan
well - I thought maybe there is something like a visual structuring here and you can see who is working on which tasks. We have something like that at work, so we can do sprints and see who is working on which problem, new function and which bugs.
This allows us to move them from release to release and prioritize or categorize them accordingly.
But also if it takes longer or certain dependencies still needs us to write under tasks.
well - I thought maybe there is something like a visual structuring here and you can see who is working on which tasks. We have something like that at work, so we can do sprints and see who is working on which problem, new function and which bugs.
This allows us to move them from release to release and prioritize or categorize them accordingly.
But also if it takes longer or certain dependencies still needs us to write under tasks.
Friendica Support reshared this.
@7homas โ If the Core Developers team grows even by one, I think it would be good to start having this kind of project management tool. With three people I feel like this is still manageable, but the work load isn't, so we need more people, and with more people more structure.
clacke: seeking ๐ธ๐ช๐ญ๐ฐ๐๐ likes this.
Friendica Support reshared this.
@Hypolite Petovan
What? Only three coding junkies. :laughing:
I understand that you are always on full throttle. :astonished face:
I also think that something has to be changed and now the code conversion appears to me in a different light.
So then we should gather all forces and bring the project forward.
What? Only three coding junkies. :laughing:
I understand that you are always on full throttle. :astonished face:
I also think that something has to be changed and now the code conversion appears to me in a different light.
So then we should gather all forces and bring the project forward.
Friendica Support reshared this.
@7homas โ Of us three, I believe only Michael consistently commits time to the project. My contributions have been more irregular, although I do keep an eye on the GitHub project, so even when I'm not actively contributing code, I'm looking for ways to help others.
clacke: seeking ๐ธ๐ช๐ญ๐ฐ๐๐ likes this.
Friendica Support reshared this.
@Hypolite Petovan
Well, it's a pity that there aren't more people here who can or want to contribute more time to the project.
Basically, it's a really great idea that you can host Friendica like, for example, a Wordpress. So the number of servers should actually be higher than they are currently due to this possibility.
But of course the code part is very complex and probably needs to be cleaned up and improved at one point or another.
So it is clear to me that this cannot be achieved due to the small number of heads, that one makes a big cut as I had suggested one time or another.
My goal would be to understand the code more and maybe start with a small junior point, but if something like that isn't really on the agenda and it's better not to experiment with the code, then that's the way it is.
Well, it's a pity that there aren't more people here who can or want to contribute more time to the project.
Basically, it's a really great idea that you can host Friendica like, for example, a Wordpress. So the number of servers should actually be higher than they are currently due to this possibility.
But of course the code part is very complex and probably needs to be cleaned up and improved at one point or another.
So it is clear to me that this cannot be achieved due to the small number of heads, that one makes a big cut as I had suggested one time or another.
My goal would be to understand the code more and maybe start with a small junior point, but if something like that isn't really on the agenda and it's better not to experiment with the code, then that's the way it is.
Friendica Support reshared this.
@7homas โ I have added the "Junior Jobs" to a few tasks that I would usually just do quickly myself, feel free to have at it!
clacke: seeking ๐ธ๐ช๐ญ๐ฐ๐๐ likes this.
Marek Bachmann reshared this.
Friendica Support reshared this.
@Tobias
I think I know what you meant - I hope so.
Access to the wiki? So I don't have to create an account there first and then you can give it further access.
As far as I have seen this is a Dokuwiki and there should be so. Then I would first register in the hope that this works.
I think I know what you meant - I hope so.
Access to the wiki? So I don't have to create an account there first and then you can give it further access.
As far as I have seen this is a Dokuwiki and there should be so. Then I would first register in the hope that this works.
Friendica Support reshared this.
@Andreas Kilgus Ok, I was wondering if you were talking about the philosophy of the project. I've tagged a few task I believe are good entry points into the project code, please ask questions if you're unsure of something.
Friendica Support reshared this.
Friendica Developers reshared this.
Hypolite Petovan
•Philipp Holzer likes this.
Friendica Developers reshared this.
Philipp Holzer
•like this
Hypolite Petovan and Roland Häder like this.
Friendica Developers reshared this.
Philipp Holzer
•like this
Roland Häder and Hypolite Petovan like this.