Fediverse

Attached: 2 images And... [drumroll] Looks like the new "#Threads, an #Instagram #App" is up on the App Store Check out the Privacy notifications All adjustable, I'm sure Release date: Jul 6 2023 h/t @MattD #Meta #Project92 #Facebook #Metaverse

I'm outta the loop on why there's all these "rule" posts on the Fediverse. But there isn't an OutOfTheLoop magazine I can submit the question to. So, I am gonna try out this microblog thing. Anyone can fill me in?

#fediverse

This may have been answered before, but I cannot find a definitive answer to this.

This doesn't necessarily apply to Kbin/Lemmy as I have seen this before with Mastodon and never thought to ask

The number of people that are following https://kbin.social/m/fediverse is not the same as if it were viewed from Lemmy.world.

On Kbin, it's showing 8836 subscribers, but on Lemmy.world, it's merely 485 subscribers.

I understand that it is showing 485 lemmy.world-specific subscribers are subscribed, but my question is:

Why can't the numbers of subscribers be close to or not be the same as the actual number in other instances?

For this particular example, is it a Kbin/Lemmy thing? Is it an ActivityPub thing? Or is it a side-effect of how the Fediverse works?

My thinking was that the synchronising of numbers between instances may be either broken/disabled due to the server load or the feature on the software side of things has not been implemented.

Any help would be appreciated. :)

Chaos at Reddit and Twitter have a direct impact on the fediverse. Growth at Lemmy and Kbin. The server database of kolektive.social gets seized by the FBI.

I looked at the lemmy stats again today like the last few days (since the 1st of July), apparently tonight there has been another wave of bot signups.:

Lemmy: 1,555,395 overall users (+ 2363)
Kbin: 55,201 overall users (+ 433)

Active last 30 days:
Lemmy: 56,859 users (+ 1142)
Kbin: 55,099 users (+ 331)

^ 2023-07-02 20:15:00 CEST

Lemmy: 2,179,081 overall users (+ 623686, bots)
Kbin: 55,863 (+ 764)

Active last 30 days:
Lemmy: 59,438 (+ 2579)
Kbin: 55,532 (+ 433)

^ 2023-07-03 13:30:00 CEST

Of course "tonight" refers to tonight in central european summer time so it probably was more middle-of-the-day for you.

If you go to the site I linked at the beginning and sort by "Total users" you can see instances with 80000 users and 1 active user for example.

Open signups should be prohibited and affected instances should do something against the botted accounts or defederate. New instances should at the very least start using captchas and email verification.

TLDR: Poor discoverability impedes the threadiverse's growth by making life hard for new users. Here are some suggestions on how discoverability could be improved.

1. Make fediverse-wide search more friendly by hiding complex front-ends and grouping search results by type
2. Allow communities to be discovered more easily on unfederated instances via directory services
3. Bring over at least some content (last X posts, last Y days, all pinned posts) when first federating communities
4. Ideally bring over all content, or find a way for searches and sorts to interrogate the most complete set of community data (likely the data on the community's original instance)

I'm still learning about how the fediverse works, so if I've gotten something wrong in the following discussion (eg terminology, or even a fundamental understanding of federation works), please do correct me. There's a chance I'm making a total fool of myself with this post, but here goes anyway.

In my opinion fundamental to the popularity of reddit is the ability for anyone to create niche communities. That's what set reddit apart from predecessors like slashdot or digg, where there were only a small number of pre-determined categories, like tech, politics or gaming.

Critically, reddit it makes it very easy for new users to:

• Discover communities tailored to their - even very narrow - set of interests.
• Immediately see what people are talking about in their chosen community, ie to show it is active.
• See what people had been talking about, ie to surface high quality content

The fediverse is poor at all three of these discoverability features.

I have four suggestions on how these issues might be fixed which are summarised above. I'll post these in separate comments as the post would otherwise be too long.

(By the way, I'm generally going to use the term "community" to describe both lemmy communities and kbin magazines, simply because I think "community" is more descriptive. Similarly, "posts" will generally refer to a mix of threads, articles, comments, replies etc.)

Assuming my understanding of how the fediverse works (as I said, I'm still learning, having only heard the word fediverse for the first time a few weeks ago) isn't too far out of whack with reality, I'm guessing these solutions may all be various degrees of difficult to implement. And not necessarily implementable at the individual instance (kbin.social, startrek.website) level, or threadiverse software level (kbin, lemmy), but perhaps requiring thought and application at the ActivityPub protocol level.

But I believe that making threadiverse communities and content more easily discoverable by new users will be critical in growing the fediverse overall.

So... I see that /r/Android is also on Fediverse now @ !android@lemdro.id... How can I add this to my kbin.social Threads? In search I don't find !android@lemdro.id, shouldn't I be able to see it?

#fediverse

What fediverse is kbin a part of exactly? Is it a part of the Lemmy network? Or does it have its own network?

I thought kbin was stand alone. People seem to be comparing it to Lemmy, so I'd imagine they're distinct, but I can't find much information on it.

Any help?

Thanks to whoever chimes in.

#fediverse

Good evening, Fediverse.
(I say, noticing that it is only slightly different from shouting into The Void)

Tell me one good thing about this weekend?

#fediverse

🚨 Kolektiva.social SECURITY ALERT 🚨 This is an alert for Kolektiva.social users. Please read this post in its entirety! In mid-May 2023, the home of one of Kolektiva.social's admins was raided, and all their electronics were seized by the FBI. The raid was part of an investigation into a local protest. Kolektiva was neither a subject nor target of this investigation. Today, that admin was charged in relation to their alleged participation in this protest. Unfortunately, at the time of the raid, our admin was troubleshooting an issue and working with a backup copy of the Kolektiva.social database. This backup, dated from the first week of May 2023, was in an unencrypted state when the raid occurred and it was seized, along with everything else. The database is the heart of a Mastodon server. A database copy such as the one seized may include any of the following user data, in this case up to date as of early May 2023: - User account information like the e-mail address associated with your account, your followers and follows, etc. - All your posts: public, unlisted, followers-only, and direct ("DMs"). - Possibly IP addresses associated with your account - IP addresses on Kolektiva.social are logged for 3 days and then deleted, so IP addresses from any logins in the 3 days prior to the database backup date would be included. - A hashed ("encrypted") version of your password. 🚨 👉 As a precaution we highly recommend that all users on Kolektiva.social change their password immediately to a new, unique, and strong password. We sincerely apologize to all our users and regret this breach. In hindsight, it was obviously a mistake to leave a copy of the database in an unencrypted state. Unfortunately, what would otherwise have been a small mistake happened to coincide with a raid, due to bad luck and spectacularly bad timing. We understand that our users and other people on the Fediverse will have a lot of questions. We will try to answer them as best we can, but please be patient and bear in mind that we may be overwhelmed with messages, and may be delayed in responding or unable to provide answers to certain questions for legal or technical reasons. As a security culture reminder, it can be extremely harmful to the individuals charged and to our community to openly speculate on the Internet about alleged criminal activity or about what law enforcement may be able to do with seized data. Our present awareness is that the seized Kolektiva data is unrelated to the federal investigation and prosecution and we are exploring legal avenues to have the seized data returned and copies destroyed. Thank you for your understanding and solidarity :black_sparkling_heart: 👇 Please see our replies to this post for additional information (1/?) 👇

#fediverse

We need to talk about content/user ranking standardization.

Upvotes/boosts/reduces need to do SOMETHING, and what they do should be unified across instances.

The best way to use these three scores seems obvious to me, and needs a standard to be established.

I posit a simple standard that can be built upon, and used by all:

• Upvotes increase your "reliability" rating. (This can be used to establish trust as a person who commits bytes to a federated server.)
• Downvotes decrease that reliability rating. (Admins should be able to use this score to exclude data they're not interested in wasting space for.)
• Boosts are reposts to your federated identity (mastodon, kbin, lemmy, etc) for visibility to your subscribers. They are instance-agnostic, as they are more a user function than anything.

And did you monetize your infrastructure? If so, how?

How do this and Lemmy and Mastodon and the others connect to each other?

#fediverse

I have questions about kbin and reddit, can someone help?

#fediverse

Mastodon Users 12,921,082 accounts in past hour +4,107 last day +37,987 last week +112,094 New account growth has exploded.

Attached: 1 image Mastodon Users 12,921,082 アカウント 過去 1 時間で +4,107 最終日 +37,987 先週 +112,094 新規アカウントの増加が爆発しています。 https://mastodon.social/@mastodonusercount/110641547204033528 #prattohome #MastodonUsers

I have been Polish Mastodon's human firehose tonight. AMA.

#fediverse

Meta has not announced an official release date for the app, but it showing up on the Google Play store likely means a release is imminent.

At the first time I subscribed Mastodon account ( @wavewalnut ).
Mastodon seems to be fully-extended Twitter and I'm impressed that federated timeline is flowing at an amazing speed.
And I reconfirmed that Mastodon-like SNS is specialized in communication with followers, and Kbin-like SNS would be better for my daily using.

#fediverse

Are you sad that moving to Mastodon has deprived you of your favorite brand accounts? Don't worry, we've got you covered.

Olá fediverso

#fediverse

I think #Fediverse would be needed by more peoples from this month because Twitter starts blocking unsubscribed users.
#Kbin (kbin.social) is not a proper alternative of Twitter, but it works very well in my case. (mainly for accumulation of tech infos and my study logs)

Is it possible to block the display of comments/posts of a federated domain such as lemmi.world? Too much leftist nonsense is contaminating what could be a usable platform. If I wanted to read thoughtless leftist drivel I'd be on Reddit.

#fediverse

m/dance was created very recently on kbin.social and has only a few posts. Still, if I search for its URL on lemmy.world it is visible and I can subscribe, though I can't see any of the posts: https://lemmy.world/c/dance@kbin.social

I recently created the community c/survey_polls on lemmy.world, but when I search for it on kbin.social it is not visible. I can see the cross-posts I made on c/general and c/newcommunities, and looking at my profile through kbin.social my first post to c/survey_polls also doesn't seem to be visible.

My point is, what communities/posts are or aren't visible across lemmy.world and kbin.social? Do posts from one website only appear on the other if the community already has subscribers? Or is there some sort of time threshold?

To add to this, when looking at the post through lemmy.world you see 1 comment, while on Kbin there are 3. I'm even more confused now.

YOWSA, my masto server is on fire https://hackers.radio.

I don't actually know it to be on fire, and I really hope it isn't, it was in the vein of '..fighting fires...' in the old IT-Speak.

It sure ain't workin' thouigh, some IT Type needs to get over there and put out the fire, as it were. ;)

#fediverse