Items tagged with: gnusocial

@diogo Thank you for your explanation. Now I really see a page on the loadaverage site that tells its server version. And #AndStatus still successfully connects to the server (I'm writing to you using it).
This means that the authentication problem that I reported is caused by a configuration of a concrete server, and not by the latest version of #GnuSocial :-)

Using a chance to talk with you, I hope that you will find time for Client-to-Server #ActivityPub API also. I'm extending support of that API in AndStatus, and already see that not only #Pleroma, but even some #Mastodon sites begin to implement some parts of the API, allowing a Client app to request information directly from its sources, without a need to duplicate it. E.g. Notes by an Actor may be requested from the Actor's profile (from the Actor's outbox) at his site, and not from the server, at which the User of the Client app has an account...

@colegota @xrevan86
@xrevan86 @diogo One of users reported that #AndStatus app doesn't work with the new #GnuSocial server "v.2.0..x dev". I started investigation and see that /api/statusnet/config.json API point now returns 404. Looking in current Source code of the server I see that the API is documented now as /api/gnusocial/config.json - but that returns 404 also...

So the question is did Client API change radically or the server is simply broken, or... ?
And where can we see any info on Client to Server API changes / current docs?
@xrevan86 As I see you are an active #GnuSocial developer now :-), congratulations!
Could you help to boost Group support in client apps?

I see that web site has the global Group Directory https://loadaverage.org/groups
but API, as I see, shows local groups only.
Could you extend API to list All accessible groups?!
On adding Group / List support to #AndStatus

Oh, I see that #GNUSocial development is going on: https://notabug.org/diogo/gnu-social
#ActivityPub Server-to-Server support is being added (and I saw a report that it was successfully tested some days ago...)

Moreover, looking into the source code I found the first-hand info about the system's API .
And although the code, related to Groups support, didn't change for the last six years :-) https://notabug.org/diogo/gnu-social/src/nightly/actions/apitimelinegroup.php , it works and I could actually retrieve the group's timeline at loadaverage.org

The unusual "!groupname" syntax to address a group is not a big problem...

So I'm moving on adding Group support to #AndStatus (whatever it will be actually...) https://loadaverage.org/attachment/5785458
Изображение / Фото
PostgreSQL support has been merged into !gnusocial nightly. Ta-dam!
Interacting with GNU Social network over Pleroma software for fediverse social networks #gnusocial #pleroma #mastodon https://gnusocial.club/attachment/204511
Изображение / Фото
@diogo@loadaverage.org @dalme @colegota I really, really like the "when it's ready" approach. If there's an interval of several months (or a year) in which we can't communicate with mastodon accounts, well, that's their loss. It's not the end of the world.

Thanks, @diogo @xrevan86 (and others), and please, keep working in your own pace.

!gnusocial !empoderandogs
> I miss GNU social sometimes
@tealturtle Technically, I don't miss !gnusocial ;-).
Congrats to @diogo and the GNU/Social team for releasing 1.20.x!

They are working on some very exciting updates for #gnuSocial which is the oldest and first federated social network!
@1iceloops123 @mangeurdenuage MariaDB 10.2 broke it (the EmailRegistration plugin in particular), fixed now. Expect the fix in @diogo's upstream soon.
For !admins of !gnusocial: if on MariaDB 10.2 or later, update the confirm_address schema.
GNU/Social will support ActivityPub via my plugin before Mastodon and Pleroma deprecate OStatus.

I look forward to helping modernize the GS code base this summer 😄


#gnuSocial #activityPub #fediverse
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.
@drequivalent @alex @sptnkmmnt #mastodon появился весной 2016, а #gnusocial наверное в 2007. Это получено по запросу в память.
Hey Mastodonians, #GNUSocial citizens and others! Gear up for tens of millions of Nextcloud users spread over several 100K servers who can now join the #fediverse in just one click!

Join the global social network!
#mastodon #selfhosting #federation
Изображение / Фото
GNU Social (https://git.gnu.io) and Pleroma (https://git.pleroma.social) repo certs seem to have expired. I'm getting an error. #gnusocial #pleroma
Groups are like a hashtag you can follow.

GNU/Social and pixelfed might be the first AP implementations to support this! #pixeldev #gnusocial #activitypub
Message to users of quitter.no. I've decided to close this site on it's 4th birthday, that is 5th September -18. I do not have the energy and capacity to host the site anymore. Please "migrate" or find a new GNU Social home. I've decided to not handover the maintenance or data to anyone else - so please do not ask to get the data to host this site further. Thank you all for using Quitter this period and for following it's users. - A. !quitterno #gnusocial #quitter
#gnusocial isn't getting new updates anymore :(

I mean, it works fine, I just think everything can be improved. Still open for devs though
@lakwnikos @knuthollund Another thought:
3) Could this be a denial-of-service attack against quitter.se and quitter.no?? Or some misconfigured other instance flooding q.no and q.se??

Because: Some 3 weeks ago I told @knuthollund on #IRC about the issue and he said he would have a look. Soon after that the problem was completely gone and quitter.no worked flawlessly for at least the rest of the day! And moreover: quitter.se also worked flawlessly! But later it turned out @knuthollund didn't actually do anything at that point, not even restart anything.)

So I think that something on the fediverse network must have changed within those couple of hours. I think the cause of the problem is somewhere in the internet and that cause did stop its weird behaviour against quitter.se and quitter.no just for a while. Too bad the problem came back the next day.

I think one could check the logs of the webserver or use wireshark to look out for weird/excessive traffic.
@lakwnikos Regarding the "not-responding database server every few minutes" phenomenon I really wonder what the cause of it could be.

1) I think only quitter.se and quitter.no are affected. I did some research and asked on IRC but couldn't find any other instance with this problem yet

At https://fediverse.network/quitter.no we can see a visualisation of the outages: https://quitter.no/attachment/1778104 . I checked a couple of other instances and there was none with a pattern like this.

2) so why only quitter.se and quitter.no? They are independant instances. Or is there some config setting that quitter.no got from quitter.se back when .no was created? Maybe @knuthollund has an idea?

@knuthollund @hannes
[sorry for repost but I missed adding the !gnusocial tag]
Изображение / Фото
Later posts Earlier posts