Skip to main content

Friendica Developers reshared this.

Questions about /display/
!Friendica Developers

@Michael Vogel - I'm currently moving the mod/display.php

As far as I can see, there are two main-routes for this controller:

  • /display/{guid}
  • /display/feed-item/{uri-id}.atom[/conversation.atom]



and as far as I can say, it would be better if the second route should have an own root, like `dfrn_item/{uri-id}[/conversation.atom`, as it's a DFRN only logic.
Am I right so far?

If so, can I move it to this new path or is this path necessary for the federation usage, means it could be called from other servers too?
I just found calls with prefix DI::baseUrl(), so I guess it's "just" for the server itself, but I'm not sure ...
@Michael Vogel !Friendica Developers Friendica mod refactor
10 comments - Show more

Friendica Developers reshared this.

Philipp Holzer
@Michael Vogel / @Hypolite Petovan

I still struggle at mod/update_display.php
It's the only place, where the display_content from mod/display.php is called with the parameter $update = true.

But I don't find any place inside Friendica, where we call /update_display?p=<profile_uid>.

Do you know if this is till in use and if so, what's the meaning of it?
If we wouldn't use it anymore, there's a lot of code at mod/display.php, which I could delete in that case..
@Hypolite Petovan @Michael Vogel
This entry was edited (2 weeks ago)

Friendica Developers reshared this.

API usage for Friendica Frontend
!Friendica Developers

And another question :-)

Currently, we strictly separate between API calls and the Frontend.
But, Why?

I'm currently moving the events to the Module directory.
And there's already an API for it, but as far as I understand @Michael Vogel , we must not mix API and Frontend.

But as far as I know, in modern environments, there's a backend part (= API), and a frontend part (= view)
The own frontend still uses the same API. So we don't have to implement the same business logic at different places. As I said, I came across at Event, where this issue produces significant double-code.

So at least what I would like (in a final state :-):

  • API ... Create, Update, Delete, Get, GetMultiple for our Data model, or "everything without HTML output"
  • Module ... Everything, which produces HTML output :-)



I know, this would be a BIG change :-)
@Michael Vogel !Friendica Developers Friendica

Friendica Developers reshared this.

Michael Vogel
In modern environments the frontend is calling the API. We are not there yet.

I would like having that separation since this would allow us to just test all API calls to make sure that the frontend is working as expected.

Friendica Developers reshared this.

7homas 🏳️‍🌈🖖🏻
@Michael Vogel
What is the showstopper for that? Cause that is also a thing for a new Webdesign. So The Web sould be separate from the code with all the magic.
@Philipp Holzer
@Philipp Holzer @Michael Vogel

Friendica Developers reshared this.

Hypolite Petovan
API is a misnomer in our case because it can designate several things:
- Our internal API (what you described in your post)
- The Twitter API endpoints we support
- The Mastodon API endpoints we support
- The GNU Social API endpoints we support
- The Friendica-specific API endpoints we expose (mainly for Friendiqa)

We definitely lack a unified internal API but that’s supposed to be taken care of by the Repository/Factory/Model/Entity structure that we should keep expanding.
This entry was edited (4 weeks ago)

Friendica Developers reshared this.

7homas 🏳️‍🌈🖖🏻
@Hypolite Petovan
why don't separate the api for Twitter, Mastodon, Gnu etc. and of course an api to communicate with the frontend.
No mixing the api together. Activateing the maybe Mastodon APi as main class with subclasses in one folder and subfolders.

@Philipp Holzer @Michael Vogel
@Philipp Holzer @Hypolite Petovan @Michael Vogel
This entry was edited (4 weeks ago)

Friendica Developers reshared this.

Hypolite Petovan
So far we’ve done a good job at having the business code identical for the Twitter and Mastodon API endpoints. There are some legacy Friendica endpoints (mostly the asynchronous endpoints used by Javascript) that are redundant with the page modules.

Friendica Developers reshared this.

7homas 🏳️‍🌈🖖🏻
@Hypolite Petovan
Can this endpoint not be closed and moved to an other area. So that you have the main friendica core who will do the internal magic. On the other hand the API section who is communicating with the core. Additional an internal API who is communicating with the core and the frontend section. On all APIs there is only data communication.

The Frontend Section is an additional area who will communicate with the frontend API and the user.
So the magic on the frontend section will be created only in the frontend and the API communication will only send data ... No html, no Jscript and no other magic.

In that case all three sections (Core, API, Frontend) could be developed separate with less interference between them.

Sure if you need a new function... First core the API and if needed then frontend
@Philipp Holzer @Michael Vogel
@Philipp Holzer @Hypolite Petovan @Michael Vogel

Friendica Developers reshared this.

Hypolite Petovan
I don't think we need to go that far. Separating the web frontend from the API would be a massive undertaking at this point, and also there's a trend where even Javascript frontends are starting to request already formed HTML from the backend because it turns out it's faster this way. Which means we're both behind and ahead of the curve!

However we do need to extract the business logic in a unique place so that we can reference it from the places it is duplicated.

Friendica Developers reshared this.

7homas 🏳️‍🌈🖖🏻
@Hypolite Petovan
I think this is very necessary.
Passing preformatted web content makes you very inflexible since you have to go directly to the core. That's where I see the problem, that you either have a good coder for the core but not a good designer. The other way round a designer of the frontend can't write a good core code.
For this reason the Smarty framework is currently running in Friendica, which as I understand the framework wants to separate this.

If you want to speed up the whole thing, you have to get away from PHP code which is executed at runtime and create static pages. Peppered with lots of javascript which offloads/executes the execution to the client.

But ok that's my opinion on the subject.

@Philipp Holzer @Michael Vogel
@Philipp Holzer @Hypolite Petovan @Michael Vogel

Roland Häder reshared this.

Friendica Developers reshared this.

Hypolite Petovan
Thankfully, we can have both HTML modules and API endpoints! As long as we don't duplicate business code, which is what Philipp has been encountering.

On the other hand, writing a full Javascript web frontend is a massive endeavor, there currently are almost 500 web frontend routes that each represent a part of a Friendica feature. They all would need to have a Javascript counterpart, without even counting the corresponding bespoke API endpoints that would need to be created.
Andy H3
I think I've learned something here.

Friendica Developers reshared this.

Add-on refactoring
!Friendica Developers

So this are my first thoughs about the Addons:

  • Metadata about each add-on should be in an extra file, I would prefer something like addon.json
  • I would like to replace the whole Hook class with a proper Registration class, which is loaded when activating the Add-on. So we can remove the whole Hook table.
  • All Events in Friendica should be in an events.config.php with a proper description (maybe as constants?)
  • for legacy purpose, I would create a wrapper class like the LegacyModule class, which would execute the corresponding php-functions
  • I'm thinking about a giving each Event a specific interface (not knowing how tbh currently, maybe the corresponding interface setting as a value for the Event inside the events.config.php?), so each event and each add-on will know exactly what parameters and which result is necessary



This is it so far..

I would like to start with creating the events.config.php and replace all text with constants.. I think this is a non invasive behaviour, but gives some insights about the next steps
!Friendica Developers Friendica addon

Friendica Developers reshared this.

Michael Vogel
Like always this is kind of foggy for me :-) But I guess it will be a good idea to implement it in parallel to the current mechanism and then to move the addons step by step.

Du you have got an idea how to keep the folder structure in a way that all addons will stay in the addon folder?

Friendica Developers reshared this.

Hypolite Petovan
The folder structure won’t change, but instead of a list of functions, addons will become classes.

Friendica Developers reshared this.

Friendica codebase restructure
!Friendica Developers

Based on the PR https://github.com/friendica/friendica/pull/12075

@Hypolite Petovan is right, I should have started this conversation first, but it made fun to restructure our code, so it is what it is *gg*

What's the issue/my pain:

I'm thinking about introducing the PSR-7 Request/Response interfaces and create an Emitter, so there's no way out anymore directly inside the code, everything is done by the emitter. With this pattern, we could add all the authentication stuff inside a "Middleware" and get rid of the different auth-places (App, Security\Authentication, Module\BaseApi)

So, now I tried to think where to start. We would need a Middleware directory for all the auth/base-load things, but we already do have a mix of domain-based directories (TowFactorAuth), functionallity based directories (Model/Object/Factory/Collection/Capabilities) and and core directories (Core, App, Console, Worker)...

And I try to start to "really" encapsulate the domain-based directories inside Friendica\Library, so we get rid of some mixings, having all domain based classes inside one directory.

In the end, I think we should have some core directories at src, directing everyone to the right place.

I hope I didn't loose you at least, I just wrote down my path to this PR :)

PS: there're "just" ~200 code changes, the rest is because of the messages.po recreation don't worry :)

Restructure Friendica Base by nupplaphil · Pull Request #12075 · friendica/friendica

I always struggle with our codebase about where to find what content .. Because we moved from pattern to pattern, we left a lot of leftovers in our codebase. This PR should restructure our codebase...
GitHub
@Hypolite Petovan !Friendica Developers Friendica Codebase structure
This entry was edited (1 month ago)
12 comments - Show more

Friendica Developers reshared this.

Philipp Holzer
So do you agree with the restructuring or shall I postpone it after mod/ is restructured? I think first, but I'm not sure :-D

Friendica Developers reshared this.

Hypolite Petovan
I think both, even if they sound unrelated.

Friendica Developers reshared this.

Friendica Woodpecker / CI in GitHub bricked
!Friendica Developers

I'm sorry, I bricked the CI with the latest Woodpecker change.. Now instead that we don't create Archives at all nodes, we now don't execute some pipelines at all and they are "stuck forever" and blocking new executions.

I'm not sure if I can fix it today, so here's the announcement :-/

I will kick the pipelines from time to time to make PR checks possible, but the "merge" pipelines aren't working (so no new archive appears currently..)
!Friendica Developers GitHub Friendica CI Woodpecker
This entry was edited (1 month ago)
3 comments - Show more

Friendica Developers reshared this.

Philipp Holzer
I think I got it! :)

It was a mix of wrong environment variable setup for $WOODPECKER_LABELS (added additional " for the value, which got escaped and added to the value) and using the `label` filter in Woodpecker, not knowing that this feature is only in the nightly builds yet

--> as far as I can see, all Archives are now deployed at https://files.friendi.ca as expected :)

Friendica Developers reshared this.

Hypolite Petovan
Good job, thanks!

Friendica Developers reshared this.

Yet another Git-Repo :D
!Friendica Developers

@Tobias - I'd like to commit changes for the computed "docs" page at https://git.friendi.ca/friendica/docs.git

Can you create this repo for me and make me admin for it? Thx :-)
@Tobias !Friendica Developers Friendica Git repo

Friendica Developers reshared this.

docs.friendi.ca
!Friendica Developers

Hi, I'd like to add a new domain `docs.friendi.ca` where we store the whole documentation. It should be versioned, like https://docs.friendi.ca/2022.09/ for the docs of the stable 2022.09 version or https://docs.friendi.ca/develop/ for the docs of the develop branch.

I think it would be possible to automatically generate it.

But before, I do need the domain - pinging @Michael Vogel - and a routing to the current files.friendi.ca vm-instance - pinging @utzer ~Friendica~ :-)

I'd like to generate it automatically during the CI, so the update would be smooth and automatically :-)
@Michael Vogel @utzer ~Friendica~ !Friendica Developers Friendica Documentation
15 comments - Show more

Friendica Developers reshared this.

Roland Häder
@Philipp Holzer Excellent work on automating updates of documentation, maybe the usual user won't care, but we developers might care.
@Philipp Holzer

Friendica Developers reshared this.

Philipp Holzer
Done: https://docs.friendi.ca/develop/ :-) .. automatically created/updated/published per CI

Friendica Developers reshared this.

Hank G ☑️
I like the new look! There are a few hiccups but overall looking sharp. Are the doc links from the wiki going to point to this as well?

Friendica Developers reshared this.

Roland Häder
@Philipp Holzer @Michael Vogel @utzer ~Friendica~ Oh, even manuals are being updated and searchable. Now it is time to put links into #Friendica code. URL: https://docs.friendi.ca/<branch>/ or only for develop?
#Friendica @Philipp Holzer @Michael Vogel @utzer ~Friendica~

Friendica Developers reshared this.

Philipp Holzer
I don't have currently that time, so it's still WIP .. When it's finished, of course there will be a sub-dir for stable releases and develop - and Release candidates, similar to our branch structure :)

Friendica Developers reshared this.

2 Factor & DB plaintext
!Friendica Developers

Hi all, I lost my mobile phone during the last festival and so my TOTP-App was gone forever. Unfortunately, I wasn't aware of my recovery codes, so I thought I would have to reset my accounts of Friendica.

But no! just use select code from 2fa_recorvery_codes where uid = 66 and used is NULL; and voilá, I used the first code and was back in.

@Hypolite Petovan , isn't this a possible security issue, is it?? Storing such sensible data as plaintext. I think we should save it as hash like for passwords to make it impossible to read it again .. Yes, the downside is that there's no possibility to save recovery_codes from the settings-panel again, but tbh I feel a little bit unsafe, but maybe it's just a feeling :-)
@Hypolite Petovan !Friendica Developers Security Friendica plaintext 2factor

Friendica Developers reshared this.

Hypolite Petovan
We hash passwords not just because we want to prevent someone having a database dump from logging in the website depending on this database, but also for the other websites users might use the same password for. There is no such risk for randomly generated recovery codes.

Additionally, the use of the recovery codes necessitates the use of the password (that you still had in your head/password manager), after all it's a second-factor authentication, which means that it can be freely compromised as long as the first factor (the password) is safe.

Still, we can hash these codes and as a result only show them once, it isn't that hard other than requiring someone™ to spend some quality time on this task.

Friendica Admins reshared this.

Large database
!Friendica Admins
Hi everyone,

last week, I struggled with the size of my database for opensocial.at .. It went full (80GB) .. I added additional 10GB to the volume, but it seems to constantly increase and I think in a few weeks, I will be at the same situation like the last week.

Is there a possibility to shrink the database, or to wipe old data?
I recently deleted about 1.200 spam accounts (and set the register option to approval first ... lessons learned...). Are there leftovers inside the db which I can delete?

It's not that I don't have enough space, but I'm afraid of my backup borg-backup space in the near future ^^
!Friendica Admins Friendica DB database size

Friendica Admins reshared this.

Philipp Holzer
nope, there're no active relays "Das System hat derzeit keinerlei Relays abonniert."

Friendica Admins reshared this.

Michael Vogel
Disable the avatar cache in the admin settings. The avatar cache is most likely the biggest table in your database. Also enable a maximum lifetime for posts (See the performance section in the admin settings)

Squeet.me with now around 5.000 users has da database size of around 100 GB.
This entry was edited (3 months ago)

Forum reshared this.

Test post
!Forum

#test Hash with #Tests
#test #Tests !Forum Friendica test forum Dev arg

Forum reshared this.

test
!Forum
!Forum

Forum reshared this.

Test post
!Forum

let's have a look ..
!Forum again

Forum reshared this.

with callstack
!Forum
A test with callstack!
!Forum

Forum reshared this.

Test again
!Forum
Test again..
!Forum

Friendica Developers reshared this.

Test Post
!Friendica Developers
Just a test if forums are still working :-) plz ignore
!Friendica Developers Friendica test Dev
7 comments - Show more
Philipp Holzer
haha, I think I will try to call her with that name and see what happens :D
Philipp Holzer
d778af0b0ee3462d6cff943e0a8d8a9a5364c67f
What I did:

  • Clicked at "Friendica Developers" under "Forums" inside the left navbar
  • Opened a new Topic per pencil-button

Friendica Developers reshared this.

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?
!Friendica Developers Friendica Git Dev Label
Hypolite Petovan
I feel like most current issue labels are meaningless beyond the Bug label we use to prioritize issues during the RC period.

So it wouldn’t do any harm to add another one, but it won’t help with any existing workflow either.
Hypolite Petovan
We never had any regression issue during refactoring tasks. 🤥

Friendica Developers reshared this.

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 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
#9114 #9095 @Hypolite Petovan @Michael Vogel !Friendica Developers Friendica Dev Cluster
This entry was edited (1 year ago)
3 comments - Show more
Philipp Holzer
Any idea @Michael Vogel ? :) I'm really stuck here and it's one major piece in the puzzle to make Friendica cluster-ready ;-)
@Michael Vogel
Philipp Holzer
@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?
@Hypolite Petovan @Michael Vogel @Friendica Developers

Friendica Developers reshared this.

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?
@Hypolite Petovan !Friendica Developers Friendica Dev depository
This entry was edited (1 year ago)
5 comments - Show more
Philipp Holzer
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 ;-)
Hypolite Petovan
I didn't think in so many terms, but it looks like it, indeed!
Philipp Holzer
I'm sorry, I'm mostly thinking that way ^^..

Friendica Developers reshared this.

Create a Post with WebDav Storage
!Friendica Developers

This is a new post, using the webdav storage backend ;-)
!Friendica Developers Friendica Storage WebDAV
6 comments - Show more
Philipp Holzer
@Olaf It's still closed alpha (my node only :D )
@Olaf von Bachgau.Social
Philipp Holzer
@Olaf - If you want to try it --> the feature is integrated so you can find the addon now at the dev-branch :-)
@Olaf von Bachgau.Social
Philipp Holzer
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
Endlich wieder mal ein cooles Konzert gehört.. 1,5 Jahre ist es her :) - "Last Decission,


A test Post from Friendica
Hi all, I'm trying to reach Twitter with my new Friendica Twitter plugin :-)
Friendica
3 comments - Show more
Philipp Holzer
@Hypolite Petovan I got a lot of posts mirrored to my feed as well .. Do you know any other test for twitter plugin?
@Hypolite Petovan

hoergen

2020-02-20 22:43:48


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 :)
Android Client 2fa otp andOTP
hoergen
Maybe you shouldadd, that andOTP is an Open source two-factor authentication for Android application https://github.com/andOTP/andOTP

Hyperlight ⚡🦚

2020-01-15 09:56:59


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
#opensource #activitypub #Reddit #lemmy #developers

Parastat

2020-01-24 08:43:20


The fediverse in 2019 https://fediverse.party/en/post/fediverse-in-2019 by people over at @feneas

@Federated Networks Association

Friendica News

2019-12-23 19:30:28


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:
2019.12 as a wordcloudThe 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 .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 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 using git checkout master (or develop).

Be aware that the .htaccess file 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-dist if 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.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-2019.12 archive), 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/

developers & documentation
This one is for @Tobias. :D
@Tobias fun Dev Documentation doc
Philipp Holzer
I found even a better one :D

Fedilab

2019-12-07 20:16:32


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 #pixelfed #mastodon

NULL ⣢

2019-10-31 11:23:14


.@Gnome UI's designer summed up in one cartoon.

677
@GNOME

utzer

2019-10-12 20:40:49


Wer ist schuld an #Halle? #AfD? #Rassisten? #Nazis? Nein, #Killerspiele!

Bild/Foto
#Nazis #AfD #Halle #Killerspiele #Rassisten

Friendica News

2019-09-29 08:23:08


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. <3

Wordcloud from the pull request titles of Friendica 2019.09A 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 using git checkout master (or develop).

Be aware that the .htaccess file 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-dist if 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.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-2019.09 archive), 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 News

2019-06-23 21:19:21


Friendica 2019.06 Released


Thanks everyone who contributed, be it directly by committing patches or new features, doing translations or reporting issues.
680


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:
  • 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
You can find a complete overview of the changes in the CHANGELOG file.

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 using git checkout master (or develop).

Be aware that the .htaccess file 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-dist if 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.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-2019.06 archive), 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
#Fediverse #Friendica #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
timeline brands

Rysiekúr (old account)

2019-02-12 21:39:15


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.
#EU #Fediverse #PeerTube #mastodon #pleroma #gnusocial #funkwhale #CopyrightDirective

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-Protokoll
www.kuketz-blog.de
Messenger federation German decentralized

:-(

DiePresse (inoffiziell)

2018-10-08 21:02:53


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

Test
Just a test with the new develop node ..

Philipp Holzer

2018-05-28 05:58:04


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.

Tobias

2018-05-17 12:19:10


DSGVO


Jan Phillip Albrecht, einer der Schöpfer der DSGVO hat einen Artikel zu häufigen Fragen und Myten verfasst.

!Deutschsprachige Nutzer

!Deutschsprachige Nutzer

Hello world ;-)
After some first installation problems, I'm now in :-)
⇧