!Friendica Support Today I installed friendica through yunohost (now 2023.03-dev). When adding a contact, it is normal if the contact does not need to manually approve the follow request. However, when the contact needs to manually approve the follow request, even if the contact approves it, this contact is still shown in Contact - Pending. I tested this with my other accounts (Mastodon / Friendica). How can I solve this problem? Thank you!
2) try to add [email protected] (Mastodon, require follow requests). After I approve the request, fedibird.com said [email protected] is following me, while on tomoe.fedipen.xyz, [email protected] is in the Pending contacts. I try to follow [email protected] on fedibird.com, follow request is sent but tomoe.fedipen.xyz can't receive it.
3) try to add [email protected] (friendica, Account types set to "Soapbox") and this time succussed.
"yunohost (now 2023.03-dev)" first of all the YNH package should NOT use the dev version of Friendica, but the latest stable "2022.12~ynh1" - what does your Friendica YNH install says for the version? 2022.12~ynh1? But in yourdomain/friendica you see 2023.03-dev?
Yes that's bad and we are trying to fix it now. It is the second time this was done....I will take charge of the updates for the YNH package from now on so I make sure the commits are from stable and not random from dev.
It seems OK now...all I have done is just disabled the blockbot addon(which I don't think it's the reason...) Maybe a new install friendica site just needs more time to finish some work before everything ready. I will do more tests in the next days😀
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.
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.
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!
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!?
@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.
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).
That makes sense. I noticed, during the last Twitter Migration influx, that my Mastodon instance slowed down a couple of times, just like I experienced when I was using Friendica.
What was it about Akkoma that you liked over Pleroma? What made you switch?
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 :)
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.
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. :(
@AndiS 🌞🍷🇪🇺 The change we added to .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.
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
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 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).
@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.
@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 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 link HTML tag instead of a and the other has several values in rel attribute - maybe this is what breaks the check?
@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.
@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.
Edit: here's the message I receive now, haha, oups
Edit2: Just managed to add the link back on Gravatar side. Not gonna edit any longer for now unless there is a sure fix for it. Looking forward for this :D
@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.
As far as I know there's no possibility to hide reshares completely. I guess, the advanced content filter could be used to collapse reshares. But I don't know how.
“a group of romance writers”说 > “… Zlibrary多年来一直是个麻烦，之所以2021年尤为糟糕，是因为TikTok在其中煽风点火。每个月我们都看到新的TikTok视频说: “Never pay for another book! Find them here on Zlibrary.”浏览量数十万。过去我们至少可以让Google撤下搜索词条 … 当TikTok变成Zlibrary的免费宣传版时，我们彻底没办法了 … Zlibrary可能真的会让我们崩溃。”
It took a bit longer then expected, but we are very happy to announce the avail-ability of the new stable version of Friendica the “Giant Rhubarb” 2022.10. Kudos to everyone who made this release possible by their contributions! In addition to fixing bugs
It took a bit longer then expected, but we are very happy to announce the avail-ability of the new stable version of Friendica the “Giant Rhubarb” 2022.10.
Kudos to everyone who made this release possible by their contributions!
In addition to fixing bugs and improving the performance of Friendica, the highlights of the changes since the 2022.06 release are
the Gàidhlig translation was added to the repository, thanks to the work of @gunchleoc,
node admins using relays can now configure languages of postings arriving over the relay that should be discarded automatically,
the 2FA login has been reworked, and
it was discovered that using the Blowfish algorithm is implying a password length limit of 72 characters. Should you use a longer password, this will be transparently dealt with upon your next login.
For details, please the CHANGELOG file in the repository.
Since version 2022.06 the lowest required PHP version Friendica needs on the server was raised to PHP 7.3 and PHP 8.0 is supported.
What is Friendica
Friendica is a decentralised 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.
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.10 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 then 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.
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.10 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!
@Friendica News I was a bit unsure because it was my first version with a database update and my timelines were empty. But now everything seems to be back. Thank you for the great work!
First of all, thanks a lot for your awsome work. I really like friendica! WIth the new release 2022.10 i get a lot of warnings ("cat: /proc/loadavg: Datei oder Verzeichnis nicht gefunden") while executing the "worker.php". Might this be a new feature? My friendica instance is running on a provided server and unfortunately there is no /proc directory (linked/mounted). I will suppress/ignore the error messages for a while. I would be glad by a tip from anyone. Thanks in advance.
My friendica instance runs on a webspace/light server. "uname output" => Linux xb1.serverdomain.org 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux "ls -al /proc" output => ls: Zugriff auf '/proc' nicht möglich: Datei oder Verzeichnis nicht gefunden I will ask my webhoster for support. Maybe they can unlock/mount the proc directory. But I have just a little hope.
@Frank Schönfelder ah, yes, hosting on webspace might work but is not endorsed. Depending on your Linux Skills and other needs I can suggest to use @uberspace.de instead, it costs 5€/mo at least, but they give you full CLI access, so it is much better for Friendica.
@Frank Schönfelder this /proc/loadavg is needed for the worker to know the current system load (I assume), but maybe there is some other way around this, I think this might be something @Michael Vogel or @Hypolite Petovan can answer, as at least Michael knows if there is some config parameter to circumvent this.
Thank you very much @utzer ~Friendica~ for your pleasant and good support. I asked my webhoster about /proc access and he denied it for the small product package i have. So I'll wait a bit for response from @Michael Vogel or @Hypolite Petovan, if any. And think about my options.
Hi Frank, this error message has been suppressed in the latest version of the develop branch. You can either wait for the next release planned late-December/early-January or check out the develop branch using Git right now.
Hi @Hypolite Petovan, @utzer ~Friendica~ and @Michael Vogel. I will wait for the next stable release to get the fix. Until then, i suppress the error messages. Thank you again all for your awesome work and support! :D
@Friendica Support When I publish this post (link) I used the tag "ikura". Then I wanted to change the tag to "幾田りら". So I edited and saved the post. However, the post now has two tags, and the old tag "ikura" is still there.
I tried to edit the post again, but just can't find a way to remove the old tag. It just didn't exist in the post.
I wonder if there is any way to remove the unused tag? Thank you!
Elsewhere on the Fediverse, Friendica has already had hashtag following for years now, across all servers.
Whichever platform you're using, it works the same way:
1. Log in through the website 2. Search for a hashtag 3. Click the follow logo (or + sign) in the top right corner of the results
You will then see posts with that hashtag in your normal timeline even if you don't follow the account posting it. Note that it only shows posts published after the follow happened, so you may not see tagged posts in your timeline immediately.
This only works with posts visible to your server anyway, it won't pull posts in just on the basis of the tag. It's effectively a filter of the Federated timeline.
可以略过的废话我一开始是按照Misskey官方文档的推荐用Docker装，但不知道为什么一顿操作后装好的Misskey媒体文件却不可用……后来再翻官方文档发现还推荐了一种用YunoHost安装的方法，尝试了之后感觉很好！非常丝滑，完全不需要编程知识。并且除了Misskey以外，Mastodon、Pleroma等Fediverse软件也已经在YunoHost的官方应用库里打包好了，只需要动动鼠标就能轻松安装。 不过通过YunoHost面板似乎无法很方便地编辑配置文件。当然，对小白来说不需要更高级的配置，而对高手来说无法通过面板编辑也不算什么问题（笑）。 在这里写个简单的教程，参考YunoHost官方文档，主要面向像我一样的真正零基础小白，如有错漏请轻拍……T T
error
in reply to Pen² L • • •Pen² L
in reply to error • •Pen² L
in reply to error • •error likes this.
error
in reply to Pen² L • • •Pen² L likes this.