New Github/Gitea Label
!Friendica Developers
I'd like to introduce `Refactoring` as a new label. I feel like we should distinguish between "real" enhancements and "just" refactorings. What do you say?
I'd like to introduce `Refactoring` as a new label. I feel like we should distinguish between "real" enhancements and "just" refactorings. What do you say?
Friendica Developers reshared this.
@Philipp Holzer Refacturing tasks are not fixing (maybe they even break some old stuff, AKA regressions) any code nor they add any new functionality. Therefore they can be seen as neither a bug (as nothing is fixed, just heavily rewritten and/or cleaned up) nor a new feature (as nothing new is added).
Locks with hostname
!Friendica Developers
Calling @Hypolite Petovan and @Michael Vogel for support at https://github.com/friendica/friendica/pull/10601
I do want to alter the way how locks are working to make parallel hosts/nodes possible. I think the logic itself is pretty straight forward and final.
BUT - how can I upgrade the lock table without using it during the update process itself, it's a gordon knot
I think about using a new method at
Do you think it works? At least my local nodes are working, but I'm totally unsure about it yet ..
I'd like to finish this PR for 2021.12 as another preparation for making Friendica "cluster ready" :D
Calling @Hypolite Petovan and @Michael Vogel for support at https://github.com/friendica/friendica/pull/10601
I do want to alter the way how locks are working to make parallel hosts/nodes possible. I think the logic itself is pretty straight forward and final.
BUT - how can I upgrade the lock table without using it during the update process itself, it's a gordon knot
I think about using a new method at
DBStructure: https://github.com/friendica/friendica/pull/10601/files#diff-eda5315231a6379d57916642e302e3525c3de2161e7dedb209526c7cfc8afcd6R543 and execute it before using the lock.Do you think it works? At least my local nodes are working, but I'm totally unsure about it yet ..
I'd like to finish this PR for 2021.12 as another preparation for making Friendica "cluster ready" :D
Add hostname to Locks by nupplaphil · Pull Request #10601 · friendica/friendica
Superseded #9114 This should help with #9095 We now add the hostname to each lock as well. The hostname is detected based on either uname -n or per environment variable NODE_NAME. This will have th...GitHub
This entry was edited (4 months ago)
Roland Häder likes this.
Friendica Developers reshared this.
@Michael Vogel @Hypolite Petovan @Friendica Developers but wouldn't that possibly create a race condition, because a 2nd worker would start another update and wouldn't find the lock anymore so update it again?
Questions Depository
!Friendica Developers
Calling @Hypolite Petovan for help
Why did you introduce a separate "Navigation" directory under "src"?
My guess: this is really a DDD practice using a directory for a use cases and define the different class-types under it (creating boundaries between differently purposed code). But if so, why don't you include the Modules/Notification as well?
And "Navigation/Notification" triggers for me, that the focus of this class is only the notifications at the top of the navbar, am I right?
I'm trying to follow your pattern and refactor the ProfileField / PermissionSet.
Would it be a new "src":
"src/Profile" , where PermissionSet and ProfileField are Entities/ValueObjects ? Or how would you structure these repositories/models?
Calling @Hypolite Petovan for help
Why did you introduce a separate "Navigation" directory under "src"?
My guess: this is really a DDD practice using a directory for a use cases and define the different class-types under it (creating boundaries between differently purposed code). But if so, why don't you include the Modules/Notification as well?
And "Navigation/Notification" triggers for me, that the focus of this class is only the notifications at the top of the navbar, am I right?
I'm trying to follow your pattern and refactor the ProfileField / PermissionSet.
Would it be a new "src":
"src/Profile" , where PermissionSet and ProfileField are Entities/ValueObjects ? Or how would you structure these repositories/models?
This entry was edited (4 months ago)
Roland Häder likes this.
Friendica Developers reshared this.
Aaahh sounds like the "good old" Model View Controller (MVC) pattern:
- Model --> where the business logic is (=> Entity, Depository, ...)
- View --> the presentation layer (=> Renderer / smarty templates)
- Controller --> The logic to show the right business logic (glue between model & view) (=> Modules)
=> And I like it
I'll give it a try after finishing the WebDav class
- Model --> where the business logic is (=> Entity, Depository, ...)
- View --> the presentation layer (=> Renderer / smarty templates)
- Controller --> The logic to show the right business logic (glue between model & view) (=> Modules)
=> And I like it
I'll give it a try after finishing the WebDav class
Roland Häder likes this.
@Philipp Holzer So I can finally setup my @Nextcloud instance as storage back-end for files being uploaded here on my Friendica instance or how do I have understand it? That is I was looking for!
Yes you can
But Disclaimer: I was the only one who tested it yet, so please test it for your own before using it in production
But Disclaimer: I was the only one who tested it yet, so please test it for your own before using it in production
Roland Häder likes this.
Endlich wieder mal ein cooles Konzert gehört.. 1,5 Jahre ist es her :) - "Last Decission,
Steffen K9 🐰 likes this.
A test Post from Friendica
Hi all, I'm trying to reach Twitter with my new Friendica Twitter plugin
Steffen K9 🐰 likes this.
@Hypolite Petovan I got a lot of posts mirrored to my feed as well .. Do you know any other test for twitter plugin?
Not yet, but there's the unfollow API call in a PR: https://github.com/friendica/friendica-addons/pull/1173
Mozilla, die bekannt für den Webbrowser Firefox und das Emailprogramm Thunderbird sind, stellen jetzt auch einen öffentlichen Riot ( https://about.riot.im/ ) Matrix Chat Server zur Verfügung
https://chat.mozilla.org/
Friendica Logo for andOTP
With release 0.7.0 (currently beta) and above, the official Friendica Logo is now part of the thumbnail list :)
Hypolite Petovan likes this.
Maybe you shouldadd, that andOTP is an Open source two-factor authentication for Android application https://github.com/andOTP/andOTP
Hey FEDIVERSE 🌏
2 people are currently working on an #opensource federated #reddit alternative, called #lemmy.
They need some open source #developers to help them enable the federating function.. #activitypub
BOOST to help development...
https://dev.lemmy.ml/post/29164
Friendica 2019.12 released
Wrapping up for the end-of-the-year? We too; and therefore we are happy to announce the release of Friendica “Dalmatian Bellflower” 2019.12.
This release bundles up some bug fixes, but mostly enhancements to existing features and adds some new ones as well. For a full list of changes, please have a look at the CHANGELOG file in the repository. For a short summery, the highlights are:
The titles of all the pull requests of the 2019.12 release summarized as word cloud.
- The ACL dialogue introduced in the 2019.09 release on the new compose page for the frio theme was now adopted to all themes.
- The handling of reshares was made more native for the federated platforms and federation with Diaspora*, Mastodon, Pixelfed and Peertube was improved.
- The API was improved and got some new endpoints to improve the experience of using Friendica with mobile apps like Fedilab.
- Postings can now be pinned to your profile wall and
- if you like, you can connect to Discourse forums via email.
Thanks to all the people who have made this release possible!
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2018.09 release, please first update your Friendica instance to that version as there were several important changes in that version.
Please note, that we moved the shipped.htaccessfile to.htaccess-distin the 2019.01 version. Make sure that you have saved a copy of the file if you made any changes to it, so that you can copy the file from the backup after the upgrade.
Please further note, that since Friendica 3.6 we use Composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Furthermore, we raised the minimal requirements with the 2019.06 version to PHP 7. Before updating please ensure that you are using a supported PHP version on your server. We suggest PHP 7.2 or later.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better safe than sorry.
Using Git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to update the dependencies with composer as well.
cd friendica
git pull
bin/composer.phar install
cd addon
git pull
If you want to switch the branch (e.g. if you helped to test the release candidate) please do so after the pull usinggit checkout master(ordevelop).
Be aware that the.htaccessfile was removed from the git repository in the 2019.01 version. You might have to restore yours from a backup (if you have done local changes) or from the.htaccess-distif you had not done it before.
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 (friendica-full-2019.12.tar.gz and friendica-addons-2019.12.tar.gz) 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.phpandconfig/addon.config.php) and.htaccessfiles. 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 thefriendica-full-2019.12archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format in the 2019.03 version. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Post Update Tasks
The database update should be applied automatically, but maybe 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.
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/2019/12/23/friendica-2019-12-released/
I have planned some improvements with Fedilab.
#Mastodon :
- I will replace the discover users feature (currently done via the Trunk API) with the profile discovery.
#Pixelfed :
- History! I am on it.
#Friendica :
- Huge improvements planned. Even the cross-account actions.
- Its custom layout/actions like for Peertube or Pixelfed.
Friendica 2019.09 released
We are proud to release the new version of Friendica ‘Dalmatian Bellflower‘ 2019.09. As usual this release contains many bug fixes (we closed some 60 issues from the list) and code enhancements alongside of some new features. Some highlights are:
- A Japanese translation was added to the Friendica core and some addons.
- The two factor authorisation got improved. If you are using client apps, those now need a separate password set in the user configuration.
- One can now search for the URL of any public ActivityPub posting to interact with the posting. You need to copy the postings address and paste it into the search field.
- Users of the frio theme can now choose to use a separate compose page instead of the modal dialog.
- Admins can now block servers based on URL patterns and enable a trending tags widget for the community page.
for a complete overview please see the CANGELOG file.
Many thanks to everyone who made this release possible.A wordcloud generated from the titles of pull requests of Friendica 2019.09. In the background a Dalmatian Bellflower.
Known Issues
One of the bug fixes that was applied in this release will cause old contact requests that were discarded initially to reappear. Users will have to reevaluate the request. We are sorry for the inconvenience this may cause to you and your users.
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2018.09 release, please first update your Friendica instance to that version as there were several important changes in that version.
Please note, that we moved the shipped .htaccess file to .htaccess-dist in the 2019.01 version. Make sure that you have saved a copy of the file if you made any changes to it, so that you can copy the file from the backup after the upgrade.
Please further note, that since Friendica 3.6 we use Composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Furthermore we raised the minimal requirements with the 2019.06 version to PHP 7. Before updating please ensure that you are using a supported PHP version on your server. We suggest PHP 7.2 or later.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better safe than sorry.
Using Git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica
git pull
bin/composer.phar install
cd addon
git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull usinggit checkout master(ordevelop).
Be aware that the.htaccessfile was removed from the git repository in the 2019.01 version. You might have to restore yours from a backup (if you have done local changes) or from the.htaccess-distif you had not done it before.
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 (friendica-full-2019.09.tar.gz and friendica-addons-2019.09.tar.gz) 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.phpandconfig/addon.config.php) and.htaccessfiles. 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 thefriendica-full-2019.09archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format in the 2019.03 version. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Post Update Tasks
The database update should be applied automatically, but maybe 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.
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/2019/09/29/friendica-2019-09-released/
Friendica 2019.06 Release
Friendica 2019.06 Released
Thanks everyone who contributed, be it directly by committing patches or new features, doing translations or reporting issues.
And now, we happily announce the availability of Friendica 2019.06. It contains many bug fixes, enhancements of existing functionality and some new features. The most noteworthy changes since the last release in March are:
You can find a complete overview of the changes in the CHANGELOG file.
- Added native two-factor authentication
- Added reshare counts
- Added mascot to error pages (thanks to @lostinlight)
- Moved Friendica private message and contact request to ActivityPub
How to Update
Updating from old Friendica versions
If you are updating from an older version than the 2018.09 release, please first update your Friendica instance to that version as there were several important changes in that version.
Please further note, that since Friendica 3.6 we use Composer for dependency management. If you are updating via git, you have to remember to update the dependencies as well.
Pre-Update Procedures
Ensure that the last backup of your Friendica installation was done recently. While testing, we did not encounter problems, but better safe than sorry.
With this release we raised the hard requirements to PHP 7. If you are still using PHP 5.6+, this version won’t work anymore on your system and we urge you to upgrade to PHP 7.1 at least.
Using Git
Updating from the git repositories should only involve a pull from the Friendica core repository and addons repository. Remember to also update the dependencies with composer.
cd friendica
git pull
bin/composer.phar install
cd addon
git pull
If you want to switch the branch (e.g. if you helped testing the RC code) please do so after the pull usinggit checkout master(ordevelop).
Be aware that the.htaccessfile was removed from the git repository in the 2019.01 version. You might have to restore yours from a backup (if you have done local changes) or from the.htaccess-distif you had not done it before.
Using the Archive Files
If you had downloaded the source files in an archive file (zip or tar.gz) please download the current version of the archive (friendica-full-2019.06.zip and friendica-addons-2019.06.tar.gz) 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.phpandconfig/addon.config.php) and.htaccessfiles. 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 thefriendica-full-2019.06archive), so you don’t have to worry about them.
Please be aware of the changes in the configuration format in the 2019.03 version. You should follow the instructions linked from your admin panel as soon as possible to move your configuration to the new location.
Post Update Tasks
The database update should be applied automatically, but maybe 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.
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/2019/06/23/friendica-2019-06-released/
#Friendica #Fediverse #Release
Top 15 Best Global Brands
Wow, it's spooky how quick apple was setting itself appart of his competitors (BTW. Don't get me wrong, I'm not an apple fanboy, it's just impressive)
Top 15 Best Global Brands Ranking (2000-2018)
The ranking video compare Top 15 Best Global Brands since 2000. It comparing brand value calculated by Interbrand. Datasource: https://www.interbrand.com/ Me...m.youtube.com
Calling all #Fediverse admins of instances in the #EU. The #CopyrightDirective is coming, we need to show the MEPs how massively the EU Internets will be affected.
We are preparing a list of all EU-based #Pleroma, #Mastodon, #GNUSocial, #Peertube, #Funkwhale, and any other instances.
Please *contact me*. All I need is the domain name, which EU Member State it's located in, and the rough topic of the instance. Approximate user count welcome, but not necessary.
Please help. This is important.
Conversations - sicherer Android Messenger
Ein äußerst interessanter Artikel 
Conversations: Sicherer Android Messenger
Conversations ist ein Messenger für die sichere und datenschutzfreundliche Kommunikation über das XMPP-Protokollwww.kuketz-blog.de
ᏇᎥᏇᎥᏋ likes this.
:-(
BVT-Affäre und 12-Stunden-Tag haben das Raucherthema verdrängt. Dabei hätten die Initiatoren des Volksbegehrens eigentlich gute Argumente auf ihrer Seite.Anti-Raucher-Kampagne geht die Luft aus
BVT-Affäre und 12-Stunden-Tag haben das Raucherthema verdrängt. Dabei hätten die Initiatoren des Volksbegehrens eigentlich gute Argumente auf ihrer Seite.diepresse.com
Willkommen bei https://opensocial.at / Welcome at https://opensocial.at
Der deutschsprachige Knoten https://opensocial.at heißt alle Neuankömmlinge willkommen.
Willkommen im dezentralen, sozialen Netzwerk, wo deine Daten dir gehören
-----
The germanspeaking node https://opensocial.at welcomes every new arrival.
Welcome to the decentralized, social network, where your data belongs to you.
DSGVO
Jan Phillip Albrecht, einer der Schöpfer der DSGVO hat einen Artikel zu häufigen Fragen und Myten verfasst.
!Deutschsprachige Nutzer
Tobias •
Philipp Holzer
Tobias •
I'm using develop at c0db96e84f51639cd2d8bdc1fbe5f67c413a5f7c.
Philipp Holzer
Tobias •
What version are you using?
Philipp Holzer
What I did:
Tobias •
Tobias •
Steffen K9 🐰 likes this.
Michael Vogel •
Test Post
2 people like this
Philipp Holzer and Fabián Bonetti like this.
Fabián Bonetti •
Test Post
Philipp Holzer likes this.
Fabio •
Philipp Holzer
Fabio likes this.
Hypolite Petovan •
8 people like this
Steffen K9 🐰, Philipp Holzer, Marco R., Fabio, Damien Goutte-Gattat, Andy H3, Jakob :friendica: and Wilhelm like this.
Philipp Holzer