Notices tagged with statusnet

Does anyone happen to know whether the old data of #identica users that weren't migrated over when it switched from #StatusNet to #pumpio has been archived anywhere? I see a mention that there was a plan to upload it to @internetarchive, but can't find anything more than that. #fediverse #ostatus

10 years ago I was running a StatusNet instance on Hyperboria (that didn't federate with clearnet)

Now I'm running Pixelfed on the internet (that federates with Threads)

Funny, how the threads of fate weave us. From isolation to connection, progress, this is.

#cjdns #hyperboria #statusNet #pixelfed #threads

@tokyo_0@mas.to Yes, because otherwise that'd mean #diaspora and #StatusNet aren't part of the #fediverse, which just seems wrong. :seija_coffee:

If you haven't heard, sadly, #ChirpSocial, one of the popular #ActivityPub “groups” platform, is shutting down “probably” on February 29th.

In an email they sent to admins, the owner and developer can no longer support https://chirp.social financially as they failed to find a new job after they were laid off by #Google last year.

So, if you have a Chirp.Social groups, either move to #Guppe (https://a.gup.pe) (as suggested by Chirp.Social), or if I may, to #FediaIO (https://fedia.io), an #Mbin [flagship] instance.

This reminds us the importance of having a built-in groups feature, and one where the groups feature actually federates.

Back in 2008, when the #Fediverse was born, we did have a built-in federated groups in #Laconica / #StatusNet (today known as #GNUsocial). We used bang (!) instead of at (@). A built-in groups feature is more stable as established instances can host them.

Today, we have #Friendica and #Hubzilla (as well as #Streams-based instances) to fill in that, as groups is a built-in feature in those software products. It's just a matter of finding an instance that's open to hosting groups for any topic for the ActivityPub protocol.

That said, any Friendica, Hubzilla, Streams-based instances you suggest for groups?

@transponderings The primary reason I can think of is reach.

With hashtags, you can only see content if:
1. you are following that hashtag (in Mastodon -- by the way, following a hashtag was a very recent feature in Mastodon); or watching that word/keyword (in #Calckey)

(Also, if a post is "unlisted", it won't appear in hashtags even if there are hashtags, but will still be seen through groups.)

2. you will only see content that your instance is aware of

But with groups, a content is “boosted” by the groups account, which is then seen by anyone following it, even those not yet known by your instance.

For example, I created a new solo instance. If I post using only hashtags, since it is a new instance, my status update will only be seen in servers already aware of my instance. However, if I tag a federated group, it will be seen by everyone following that group.

Or, if I am a new user, my #ObservableFediverse is very small that it does indeed feel lonely and the system is broken (people have forgotten that they started similarly in other #SNS). I have to follow people, discover users from other servers, to grow my Observable Fediverse. However, if I follow one or two groups, I will immediately see status updates from everywhere.

PS
It's not new actually. Federated groups has been around since 2008 when the first #fediverse software was released (called #Laconica, which was renamed to #StatusNet, then renamed and known today as #GNUsocial). And #Mastodon finally approved adding its own groups feature. There are also #Friendica and #Hubzilla (both far older than Mastodon and still exists today), and #Streams with group features.

@Jessica

@kristoff

It will depend on the platform. For example, #Friendica (and to an extent #Hubzilla and #Streams), the owner of the group (and anyone else given moderation access) can block accounts. There is also chirp.social which can also block accounts.

Then there is #GNUsocial, which is a rebranded #StatusNet itself a rebranded #Laconica (the first #Fediverse software, c. 2008) have built-in groups feature; which IIRC, can also block users if needed.

Personally, services like Guppe really need to add moderation features, otherwise, what you just described will more likely happen.

@jupiter_rowland @fediversenews

You can now join the waitlist to Mozilla.Social, Mozilla's 2nd #fediverse instance.

https://prod.oidc-proxy.prod.webservices.mozgcp.net/waitlist

* The first fediverse instance of Mozilla was 2010-02-22 to 2013-11-20. Its final name was “Social@Mozilla”.

#Mozilla #StatusNet #Laconica #Mastodon

Hey @evan

I republished your Interview because clearly, lots of folk on the Fedivers (i.e. Ex Twitter folk) don't know who you are. ?
https://ecency.com/hive-181335/@dickturpin/unruhrdt
#tdtrs #identica #statusnet

@evan this has to be one of the most under-stated introductions I have seen here!

So let me offer a better one: Evan is one of the reasons we are all here. He is credited as one of the creators of the #ActivityPub protocol:
https://www.w3.org/TR/activitypub/

Back in the day (a decade ago), he also used to run the biggest instance of #StatusNet, identi.ca. My old account is still there, even though I have lost access to it:
https://identi.ca/rysiek

StatusNet was the precursor of fedi.

Welcome, Evan!

This was our "hero image" from our #statusnet #gnusocial days. His name is Plopp Lakrits Vicious, a holland lop bunny.