> Y se está depurando bastante código hasta dejar el log de errores en muy poquita cosa.
I want to note that many of the recently applied patches were written by @XRevan86.
Furthermore, today @XRevan86 not only re-identified a bug but also went through a careful doc study until he came with a really clean solution :) (And I also want to recall his amazing work on a faster feed query).
por cierto, sí que se hacen cosas que se pueden ver y participar en el canal #social de freenode en el irc accesible desde la sala !xmpp gnusocial@conference.bka.li
I am indeed, but don't let ActivityPub support on GNU social be a reason to drop support for a different protocol (that happens to allow the same [but not only]). Let's maximize federation! :)
Btw, it's better to mention my loadaverage profile, social.hackersatporto.com is just a test instance and is currently using the ActivityPub branch as so it can't currently federate with pleroma, not sure why as it is working fine with mastodon...
P.S.: GNU social won't deprecate OStatus. It uses the most adequate protocol for the task and when one fails it attempts with a different one (if available in the same scenario). AP will fallback to OStatus in GS case.
Do not underestimate the value of 'soft' skills! Even in groups that do tech work like software development having people whose primary skills have nothing to do with software is important. One hacker space I went to for a bit was mostly held together by a kid who came in and didn't know anything about what people were doing, they just liked to sit there and watch and talk to people as they worked. Without them I think that the space would have fallen apart.
> 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.
LoadAverage, Colegota and some other instances are already using the latest version. This is not just a fork of GS, we will be merging it all by the end of summer on git.gnu.io.