Creo que la interfaz actual de !gnusocial hace que la respuesta se dirija solo a quien se marca al responder en lugar de a todas las personas que han participado así que me respondo a mí mismo.
Meses atrás andaba preocupado porque la situación social no era buena, pero descartaba todo tipo de movilización medianamente masiva.
Al ver los efectos económicos y sociales de la nueva crisis pensé que en cuanto acabase habría que buscar formas de salir a las calles a recuperar lo que habíamos perdido y lo que nos ha traído hasta aquí.
El otro día, escuchando algún podcast caí en la cuenta de que la cosa va a estar muy complicada, probablemente durante años.
Habría que re-inventar nuevas formas de lucha, pero no puede pasar por lo digital donde las multinacionales controlan Internet y las redes libres tienen poco espacio.
Sí, me ha llegado la notificación de que me sigues. :)
Genial, así tenemos más contacto y cuando pase todo esto hablamos "de pollos y huertos " :)
Hablando de #huertos y esas cosas, yo lo tengo delegado en @cayentana por si quieres seguir esa cuenta también.
Y sobre #Mastodon, el #Fediverso y esas cosas, pide #ayuda y sobre todo haz una presentación con tus preferencias o inquietudes y pon la etiqueta #amadrinaje y enseguida te echan/echamos una mano con lo que sea.
Yo no estoy en Mastodon, sino en otra red que se llama !gnusocial pero de temas generales puedes preguntar lo que quieras.
> At the bottom they say all the content is under a creative commons license and IANAL, but I'm pretty sure they don't get to reassign license like that. @drskrzyk Let's just say, it's not as easy as that. And it's a standard !gnusocial footer, so why go just to the !loadaverage's datacentre with legal threats specifically? https://fediverse.network/gnusocial – go big instead.
@dblaze09 !loadaverage had the Nodeinfo plugin disabled for a several weeks, I re-enabled it a few days ago after I added the proper indices to the "notice" table. The !gnusocial Nodeinfo plugin advertises software as "gnusocial". When Fedilab checks Nodeinfo, it expects "gnu" for some reason. As far as I can tell, neither the original @chimo's plugin, nor the included one ever had this value. Weird.
Hi @louis before the "big merge" @MMN-o (official maintainer) will review the changes in the notabug fork.
GNU.io had some issues when we were re-activating development and thus we just temporarily moved to notabug. Despite that, this is an official GNU social continuation, otherwise it wouldn't be on https://www.gnu.org/software/soc-projects/ideas-2019.html#social
This repository is under active development and our latest stable release was v1.20.9. @MMN-o is aware of all this effort and we have consistently been mentioning him in every release information on !gnusocial and chatting about the changes in the #social IRC.
I'm happy to announce the release of !gnusocial 1.20.x :)
The minimum PHP version to run GNU social is now 7.0.0.
Major changes from previous release:
- Various patches on PEAR related components - Various database related improvements - Improved XMPP support - Added Nodeinfo support (thanks @chimo) - Various i18n and l10n bug fixes - Improvements on Internal Session Handler (thanks @XRevan86) - Improvements on OpenID support (thanks @tenma) - Improved Media handling and safer upload (thanks @biodan) - Redirect to previous page after login (thanks @tenma) - Initial work on full conversion to PHP7 - Initial work on a better documentation - Allow login with email (thanks @dansup)
Do not forget to run the upgrade script to fix some incompatibilities with MariaDB 10.2 (STRICT_TRANS_TABLES).
In your particular instance, it is also important to run /plugins/Nodeinfo/scripts/fix_stats.php as you've joined GNU social 1.3.0 faster than we could add the statistics fix to the upgrade script ^^ Right now your instance is showing up as only having 3 users and 18026 notes: https://fediverse.network/herds.eu
> All the cache plugins break the system and thus aren't usable
We intend to rewrite the whole caching system during this summer.
> find out why web requests are an order of magnitude slower than other services
We intend to improve both network and load balance and, as a consequence, that should improve.
> fix database thrashing
Can you elaborate on that?
> replace qvitter with something that doesn't destroy performance, and supports GS' extensive featureset
We want to work on some UI/UX improvements and @dansup has some plans in mind, but I guess it will depend a bit on how fast we are tackling the other issues tho.
> probably other stuff I'm forgetting.
Keep them coming as you remember! :)
> I don't even know why they are bothering.
We just like GS and believe in its potential.
> It's hard to know what culture GS has now, given that a lot of people have moved on elsewhere or moved to different software. I guess we'll see what the current devs for it have in mind for the direction they want to take it.
We will remain true to the values that have always been intrinsic to *GNU* social.
I think it is hard to claim GS has a single culture. There is a collective conscience in a subscribers circle, another in an instance, another in a circle of highly connected instances and so on. We can escalate this to the point in which we analyze the fediverse's collective conscience with principles like a preference for decentralized services and eventually some technological comfort?.
People have different interests and ideologies... I guess there is space in the fediverse for everyone's interests and ideologies. GS just is, I don't think it or its devs take a role on setting a culture more than gcc devs do in who will use their compiler.
Yeah, GNU/FSF have never put any resources in to GNU social apart from maintaining the general !fs politics worldwide. Originally Evan had startup grants, I just put in my free time (which I barely have any left nowadays) and @diogo got the gsoc stuff.
While I enjoy the !ostatus solution much more than ActivityPub maybr we should see what has been generated "outside" of !gnusocial .) Think of how many people have managed to find their way out on the !fediverse even if it's maybe not via GS specifically. But it's all AGPL .)
Hey @mmn ! As I've said in IRC (It seems you aren't there :/ ), I'm looking forward to be a mentor this summer in GS's SoC (as I won't have the required time to participate as a student). Therefore I believe we can host a max of 3 students (me, dansup and you)! ^^
The ActivityPub plugin is able to interact properly with Mastodon (that was the only we tested it with so far so it might be working with others as well, we just haven't tested yet).
Despite that, it has some known key issues stopping it from being merged:
* It is unable to de-duplicate when OStatus and ActivityPub are both enabled - mostly noticed between GS instances with both enabled. * Is unable to verify signatures which is an attack vector that makes the plugin unsafe for use right now. * It also doesn't make use of queues nor collections caching nor has any kind of circuit breaker implemented. This makes its use risky for use in a highly active GS instance.
Right now I've been mostly fixing GS issues and resting a bit from the intense work on the plugin - and have been training for competitive programming :)
@dansup will test (or has tested, not sure) the plugin with Pixelfed and was going to fix those issues but Pixelfed has been consuming so much time from him that I will probably have to code the whole plugin by myself :(
@mmn is also looking forward to bring GS back to active development so I think the future is bright for !gnusocial :) cc: @chimo
For the GSoC proposal that I've originally submitted, I got it all addressed and even exceeded! ^^ (we can say it was a success).
But now there are further steps for the plugin to become truly reliable in the large GS scale that I would like to discuss with you. (cc: @dansup ).
Finally, I really enjoyed GS and I intend to keep contributing! For now I'm giving a break on the plugin (for a week or two, I think it's dansup's turn now) and will be trying to close some of the currently open issues (in a more healthy way than the full time non-stop work I did in the plugin to bring AP to GS the fastest I could) :)