Search
Items tagged with: friendica
Ja spinnt der Peppi..... Seit meinem Update auf
Friendica 'Red Hot Poker' 2020.09-dev - 1365
am Samstag geht bei mir in der Warteschlange die Post ab. Gestern waren es knappe 40.000 Nachrichten was schon um das x-fache mehr ist wie sonst aber aktuell schaut ea gerade so aus:
Knappe 150k Nachrichten?!?!?!?!.... Ist das ein Anzeigefehler, Berechnungsfehler oder kann das wirklich sein? 😮
#Friendica #spinntderpeppi
@Friendica Support @Friendica Admins
Thanks in advance.
Following via cURL?
I get a message that the worker didn't run for a few day in /admin, I didn't change anything, the daemon is running (I restarted it too) and I started /bin/worker.php from cli. Still I get this message.
Any ideas?
I think the post from social.yl.ms will take forever to be distributed, so here is another one from squeet.me.
!Friendica Support #Friendica @utzer
I get a message that the worker didn't run for a few day in /admin, I didn't change anything, the daemon is running (I restarted it too) and I started /bin/worker.php from cli. Still I get this message.
Any ideas?
I am conducting an anonymous survey for my MSc dissertation on the barriers to uptake of alternative social media platforms. If you're interested, please click the link below. Your input would be much appreciated!
The link is:
https://standrews.eu.qualtrics.com/jfe/form/SV_a35cj1Rjby58DxX
#fediverse #pleroma #gnusocial #diaspora #friendica #peertube
#alternative #socialhome
#pixelfed #nextcloud
Is there a way to hide posts of a user from the local /community in #Friendica, while still distributing the posts to relays?
Friendica Directory version 2.3.1 released
This update fixes a critical bug preventing normal profile/server probe that made displayed profile number plummet since version 2.3.0.
Friendica Directory 2.3.0 Released
I just pushed version 2.3.0 of #Friendica Directory.
This release notably adds back support for the zrl
query parameter that allows a directory user coming from a Friendica node to be automatically authenticated with remote nodes to make remote follow seamless.
This was a legacy directory feature that had been missing from the new directory ever since it's been initially released.
As usual, please report bugs and feature requests at https://github.com/friendica/friendica-directory/issues where I'll safely ignore them for several months before suddenly take care of one of them during an all-nighter coding frenzy!
Ist diese Anzahl normal?
#Friendica #Friendica Support @Friendica Support
Any tips which one to use besides #Friendiqa or #DiCa (which seems not to be developed anymore).
I need one of the git masters here.
git pull
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:
git config pull.rebase false # merge (the default strategy)
git config pull.rebase true # rebase
git config pull.ff only # fast-forward only
You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.
Already up to date.
How can I solve this? I do not need to keep any local changes, except for config files and .htaccess or so.
The message showed up after I did checkout "develop".
!Friendica Support
This isn't necessarily *wrong*, it's just that the mention is displaying in a way that's native to their own platform. Is there a way to improve how mentions are rendered, so that they look native on the platform that's rendering them?
Like, it'd be nice if I saw my mentions as @sean instead of @deadsuperhero or whatever. So I guess the question is, how exactly might this be fixed? Is there a way for both platforms to render the same mentions differently?
#Fediverse
Don't loose posts from rare posters anymore!
I had a problem with #Friendica, compared to Faceshit. I constantly read posts by only the most frequently posting accounts. And others were just lost on the timeline.
So I made a little script. Idea is to group contacts by posting frequency into couple of groups created just for this purpose, like "rare", "very rare" and "frequent". I run this script from time to time to automatically move contacts between these groups.
https://github.com/loziniak/red-scripts/blob/master/friendica-regroup.red
Script is written in Red, you can check the language out here: http://www.red-lang.org/
rel
tag on hashtag links, #Friendica.
#mastodon: @Horatio Velveteen 🇦🇺
#diaspora: @uxintro
#gnusocial: @uxintro
I've managed to follow a #hubzilla account from the directory but I get an error (doesn't recognise network) when trying to add a hubzilla account from the contact search area. Any clues @Hypolite Petovan ?
Hello !Friendica Support
any cool idea what to do with the domain mistpark.com? 😀
For the historical background of the name...
"Friendica (formerly Friendika, originally Mistpark) is an open, free, distributed social network."
One of those two will likely convince my friends and family to try the fediverse.. twitter-esque micro-blogging doesn’t interest them so this instance will for all intents and purposes remain a single-user instance ad infinitum.
not to insinuate that they are drawn to postgresql, or even know what it is.. that’s my line in the sand..
Sometime when I post a reply (did some tests) on my other #friendica server I only get an empty page only stating "success" as shown below.
What is wrong in this case?
Looks like this:
!Friendica Support