@bobjonkman @bobjonkman One positive is that some #Twitter clients are now advertising #Mastodon clients. I wish they'd also look at making clients for #GNUsocial, #Misskey, #PixelFed and so on, as not everyone supports the Mastodon API.
I'm uncertain. @GNU Too indicated she can follow #friendica#forums as #GNUsocial groups. I was informed by a dev after learning gnu social fixed that, I should submit an issue to request that friendica add full support for gnu social groups, (as you can see Its shaking at best now) but I haven't got around to it, so who knows if it will ever actually happen. !gnusocial@gnusocial.club gnusocial.club/notice/2083456
> We made GNU social which had its part in starting the Fediverse! GNU social was a spin-off from GNU FM, which was the software we made to run Libre.fm -- Libre.fm has been federated for a very, very long time.
I’m not sure when FooCorp’s GS project started, but the ##Fediverse predates the merger of #StatusNet, #FreeSocial, and #GNUsocial into the modern GS project. Y’all have some historical accomplishments already, so there’s no need to overinflate your role.
Comienzo aquí un hilo sobre la #Mudanza a una nueva dirección para este servidor. Esta mudanza requiere, entre otras cosas, que vuelva a instalar #Gnusocial desde cero. Para hacerlo aún más divertido, también tendré que mudar otros servicios que se alojan en la misma máquina, por las mismas razones. Y como guinda de tanta diversión, he decidido pasar de #Apache a #Nginx. Aprendí un montón de cosas de Apache, pero a día de hoy Nginx me parece que se ajusta mejor a lo que tengo (y quiero).
Primer escollo: exportar la lista de cuentas a las que sigo.
Me las prometía felices porque lo hice alguna vez hace años, y tenía la herramienta guardada: https://github.com/benediktg/gnu-social-export Pero resulta que no funciona 😅 ¿Cómo lo he solventado? Pues tirando de imaginación, API, y mi gran capacidad de copiar y pegar 😂 Fijándome en cómo hace llamadas a la API la aplicación Andstatus, he conseguido sacar la lista mediante llamadas a esto
test of quote share to see if notification occurs to OP
♲ @fuat2mb@theres.life: i highly recommend checking out a few other services on the #fediverse to see if there is anything you like better, including #Friendica, #plemora, #soapbox, #GNUsocial etc. #mastadon is only part of the 'verse, and all of the above can still interact with your friends on Mastodon
@lxo Yes, I think that's always been a feature of #Friendica. !GNUsocial allows following PuSH/websub enabled RSS & Atom feeds ... and there's an old add-on that also supports RSScloud enabled feeds.
@evan@prodromou.pub @evan@identi.ca ( and formerly @evan@e14n.com ) has said this a few times, but here it is again.
"Every time you post on Twitter, you produce value for the advertisers.
You tell everyone in your network there that it's OK to stay. That you're all helpless to leave.
You tell the people who've lost their jobs, the people who are being hounded and harassed, that they are not important to you.
You know you're going to be ashamed of it later.
Just stop posting.
Do it here, not there. Connect here, not there.
Don't reply, don't like, don't retweet.
Stop feeding your life into the machine."
This was true before Elon #Musk bought #Twitter, but I guess it wasn't as important before.
I don't fully agree, simply because there may be some advantages to many people who continue to use Twitter instead of moving to the #Fediverse (e.g., #GNU_Social, #Mastodon, #Pleroma, #Misskey, #PixelFed, #Lenny / #Lemmy, etc) or they would have moved over already.
Also, because unless one self-hosts one's own presence, an angry instance admin is all it takes to lose all posts and connections and have to start over. Or, if one has contacts on a different instance, then irate instance admins participating in #blockwars (including #fediblock) can separate the person from some portion of their contacts.
So remember, everything that Twitter is or can do to you, your Fediverse instance can also do. Most instances will never do most of those things, but pretending that one is safe here could result in disappointment in the future.
Tagging this thread with #Fediverse #Security ... whomever made the script obviously read some protocol docs and some source code. With just a little #JavaScript, they were able to knock some #Misskey and #Mastodon instances to their knees.
This isn't the first, and it won't be the last. Remember when someone posted a humongous image and locked up any #GNUSocial instance that tried to download the image? Remember when someone's instance was replaced by some sort of cryptocurrency site and PuSH es from your site to theirs would crash your site because of their site's response? (I'll bet I still have that domain blocked at the firewall.)
We have to stop being naive about the intentions of those in the current migration. The overwhelming majority will have benign, if not good, intentions. But a select few will have bad intentions. Among those intentions is to colonize the Fediverse with #Twitter's culture, to come here and impose that culture of anger and disrespect upon the inhabitants here ... which already happened once with the first wave of people joining #Mastodon instance, except it was Twitter and #Tumblr at that time.
#Misskey security update. Someone created "instances" which trigger a denial of service in Misskey and possibly #Mastodon. From what I hear, #Pleroma is not vulnerable. #GNUsocial is likely also vulnerable.
We can expect a lot more of these kind of things now that the #Fediverse is getting attention.
En la línea temporal de inicio está activado el "infinite scroll", que va cargando nuevas páginas cuando llegas al final; si no te gusta este comportamiento, puedes añadir "?page=2" (o 3, 4, etc) al final y verás la línea de tiempo página a página. !gnusocial
Depending on my skills, available time, and whether the projects' CoCs are acceptable, I would also like to contribute to both #GNU_Social and #Friendica. I know both projects can use a little additional momentum.
I'm not sure whether the #Soapbox front-end can be used with #GNU_Social. #Pleroma started out as a front-end for #GS, as #Qvitter started falling behind. So even though #PleromaFE currently doesn't support GS, it may be possible to go back to when support was removed and re-add it.
And honestly, I'm a bit gleeful that this time it is #mastodon-run instances that crash under the load and not, like in the past, the tiny #GNUsocial instances. This time we're away from the sea spray, and some megalomaniacal "developers" of Mastodon face the brunt.
I actually think that the overwhelming majority of blocking should be done by individuals curating their own timelines. I am sensitive to the effect on the Fediverse as a whole, especially as we've already been through this.
Even the original #bifurcation (when the largest instance at the time, Identica, severed communication with #StatusNet / #GNUsocial & #OStatus and switched to the #Pump.io protocol and software) and the subsequent #ActivityPub - #OStatus split have caused untold breakage. I've seen AP-side devs, admins, users patting themselves on the back while commiserating about brokenness that is built into the protocol itself or at least its common implementations.
I have also seen people telling other people to create "alts" on various instances, so that their posts can reach all of their intended contacts. Not for resilience against instance shutdowns or separating by posts and recipients by topics and interests (which is what groups and Diaspora style Aspects / GPlus style Circles are for), but because #blockwars prevents posts and members from one instance to be seen on certain others.
For the record, I think that instance governance is something that Mastodon should include in its instances.social instance-picker, along with instances' topical foci. People should have a way to see what they're agreeing to (and what the alternatives are) before the sign up.
In other words, it isn't my way or the highway so much as it is making it possible to know what one is getting into. I am certain that there are (or were) instances with democratically chosen rules. I also believe that we're not doing the people who use an instance any favor by not making it possible for them to contribute to the financing and administration of the instance. If you're paying all the costs and doing all the work to maintain and moderate the instance, it is difficult to let an election institute a policy that you disagree with. (I've started to really disagree with the idea of individuals hosting public instances wholly out of their own financial and time resources. Besides the "truck factor", it is much easier to keep an instance going if everything was already handled by a team and at least partly member supported.)
On the other hand, if the instance encourages those in its membership who can do so to participate in keeping it going, then it is perfectly reasonable to expect the admin team to carry out the decisions voted by the membership. I do realize that not everyone can contribute funds, nor can everyone do the technical labor ... but as @simsa04 will remember, things like writing documentation, contributing in discussions about improving the software, designing and implementing themes, and even marketing-type tasks such as creating a logo and a favicon or promoting the instance to people outside the #Fediverse are beneficial.