This magazine is from a federated server and may be incomplete. Browse more on the original instance.

stevecrox , (edited ) in Time to ditch Twitter/X, what are you guys switching to?
@stevecrox@kbin.social avatar

Your posting this on KBin which implements the twitter style fediverse API and federates with Mastodon.

Click the microblog button ... Behold twitter replacement

NateSwift , in FBI Seizure of Mastodon Server is a Wakeup Call to Fediverse Users and Hosts to Protect their Users

Just a reminder that nothing on the Fediverse is private. Because of the distributed nature, anyone with an instance can scrape everything you’ve ever posted and this is working as intended.

Direct messages are readable to whoever is hosting your instance and the instance of the person you send them to.

Be careful what you share on the Fediverse and be careful what you share when setting up an account

lol3droflxp ,

It’s strange that this even has to be said. This should be basic internet knowledge.

bigblekkok ,
@bigblekkok@kbin.social avatar

It used to be the norm back when common sense still existed on this planet.

woshang ,

A correction/clarification for those people who are trying to find freedom of speech on Fediverse,
as Nate says, nothing on the Fediverse is private.
Because everything is transparent, and they all link to your personal email address.

Freedom of speech on Fediverse is still limted cuz it is not private, and still has moderator.

Remember, Freedom can't exist without Privacy.

okawari ,
@okawari@kbin.social avatar

This doesn't seem entirely accurate to me.

Most public platforms interacting with the Fediverse today does require you to register an email address out of practical considerations but this is not a requirement of the system in itself. It is possible to both post and read an unmoderated fediverse with enough effort.

If you don't like the moderation of your particular server, you are fully able to create your own or set up an existing solution yourself that gives you 100% control over what kind of content you post, and in turn which content you federate to your server. Of course, you can't control which servers decide to allow your content on their server, but any user of servers where your content is blocked can do the same and have access to your content again.

As far as privacy goes, you can rent servers and purchase domains with crypto currencies which are not traceable back to you where you can host your own service that interacts with the fediverse, making you 100% able to control the information you post into it.

mightysashiman ,
@mightysashiman@kbin.social avatar

Freedom can't exist without Privacy

Of course it can. They are simply 2 unrelated concepts. Expressing yourself on reddit was like going into public space, and yelling whatever you had in mind. Doing so on fediverse is the same, but with microphones picking up your yelling to propagate it around the world.
You can have Freedom to express yourself while respecting your privacy: just don’t yell it (i.e. chose a closed private invite only community) or go to som remote forest / desert where there is nobody to hear you yell. Join an invite-only group/room on signal or matrix.

Freedom and Privacy can only exist with common sense.

metaStatic , in Multiple lemmy instances are getting hit with a js injection

you are being redirected to a porn site. sorry for the convenience.

wetnoodle ,

it's also preventing all other content and (hopefully) temporarily killing the instance, I know you're probably just joking but this ain't good

metaStatic ,

oh hell no, I mean heck no, this is totally bad news bears. They just got clowned and if you don't laugh at yourself someone will do it for you.

Midnitte ,
@Midnitte@kbin.social avatar

I used to watch porn. I still do, but I used to, too.

herpderpedia , in Twitter alternatives for the Musk-averse
@herpderpedia@kbin.social avatar

Team Mastodon over here. Best part is I don't have to explain why a federated social media is the way to go on Kbin.

Spaghetti_Hitchens , in Lemmy and Kbin: The Best Reddit Alternatives?

I absolutely adore kbin. It gets better every day!

illi ,

Any app for it yet?

00 ,
@00@kbin.social avatar

Artemis should enter open beta in a few days.

Correction: It is in public beta!

livus , in Lemmy and Kbin: The Best Reddit Alternatives?
@livus@kbin.social avatar

Good article, this person federates.

I don't get why the author seems to be saying we can't see lists of lemmy communities from kbin, though.

czech ,
@czech@no.faux.moe avatar

From kbin- how do you see a list of communities on lemmy.world? I've been navigating to https://lemmy.world/communities in a separate browser window to discover communities to individually search/subscribe to from kbin.

livus ,
@livus@kbin.social avatar

Go to https://kbin.social/magazines and turn on local and federated, then hit the search button. For some reason all the top "hot" are kbin but the "new" and "active" are various.

Then if you specifically want, say, lemmy.world, type that into the search field and hit search again. It will all show.

czech ,
@czech@no.faux.moe avatar

This shows the lemmy.world communities that are already federated to my instance. Its not a full list.

Teppic ,
@Teppic@kbin.social avatar

True, but searching from a Lemmy instance will still only show you the ones which that one instance knows about. (I think?)

czech ,
@czech@no.faux.moe avatar

Yea, a lemmy instance will show the same kinds of results for federated communities but there is no substitute for viewing the local communities from that instance.

dan ,
@dan@upvote.au avatar

Right. I usually use lemmyverse.net to search for communities.

Niello ,

Click on the tab Magazines at the top, select local and federate, put lemmy.world in the search box to see all lemmy.world communities. If you want to check for community with certain keywords you can try putting [keyword]@lemmy.world. It can search for the keyword in both the name and description, but not extensive as if you'd search on lemmy.world.

This can use some improvement, but it's not a Kbin problem though, since Lemmy is even worse when it comes to searching for communities outside each instance.

czech ,
@czech@no.faux.moe avatar

Edit: this just shows me the lemmy.world magazines that are federated to my instance

Niello ,

Ah, I see what you mean now. In that case I don't think you can do it on Kbin natively rn. There is this website though, which might help a bit. At least imo it's easier to use. https://lemmyverse.net/communities

You can just filter for only lemmy.world. When you find a community you want to join you'll have to type the handle of the community in the search icon to the right rather than in the Magazine tab for communities that doesn't already have a copy on your instance.

Teppic ,
@Teppic@kbin.social avatar

The article specifically says you can't search federated communities from kbin, but you can from Lemmy. This is just incorrect, both allow you to search local or local and federated.

czech ,
@czech@no.faux.moe avatar

Oh, right on then.

trynn , in Could popular forums implement ActivityPub and connect to the Fediverse?
@trynn@kbin.social avatar

Sure. Just look at Wordpress... it's a blogging platform rather than a forum, but it has an ActivityPub plugin available that allows federation of blog posts and comments. ActivityPub is a standard published by the W3C (the same organization that oversees the HTML standard, among many others). Anyone can implement the standard in their software if they want to.

HeinousTugboat ,

Small point of fact, but HTML is actually overseen by WHATWG primarily, not W3C. W3C agreed back in 2019 to just follow WHATWG's process.

Pons_Aelius , in Time to ditch Twitter/X, what are you guys switching to?

One does not have to switch from something that was never used.

Twitter has been a short form outrage machine since the beginning.

furrowsofar ,

The interesting thing about Twitter is how it shows how a significant part of our society works. It is kind of about amplifying fame and suggesting that we should all cares about meaningless 240 character posts or what these guys think.

That news media types love Twitter is kind of an indictment of how news works.

Pons_Aelius ,

Humans have neolithic hunter-gather brains and emotional reactions, medieval civil intuitions while using tech that borders on magic.

Twitter used to call itself the town square, and it is/was just like the square of old. Dominated by those that yelled the loudest and longest.

Jarmer ,
@Jarmer@kbin.social avatar

That's not really true. When it first came out, before the ads, before the algorithm, when they embraced 3rd party apps with an open api, it was really great. It was full of techy personalities and interesting folks. Hashtags were fun to follow, live events were amazing in real time, so much more. That was before it got inundated with politics and celebrities though. I think that honeymoon phase only lasted a tiny while, then it all went downhill into the outrage machine pretty quickly. But for a quick minute there, it was glorious.

Itty53 ,
@Itty53@kbin.social avatar

This is a wildly over generalized take.

Twitter was also an important tool for journalists and researchers worldwide. Military targets have come from Twitter posts. It is a reflection of a huge chunk of society. You may as well call all of internet technology "just a porn box" for how wildly over generalized that statement is. The reality is your generalization comes from arrogance. "I never engaged in such frivolous behavior". You're here now. Yes you have and yes you do.

Even your comment is the first cousin of outrage, it's pure disdain. Nothing more or less, and exactly as valuable as outrage.

Emperor , in A proposal for a sane transfer of useful information trapped on Reddit
@Emperor@feddit.uk avatar

Another, more complicated, possibility would be to include a user editable wiki with each community

This would be my preference. Given some of the big tasks that still need to be done (advanced moderation tools, for example) adding a wiki is relatively trivial - you can piggyback off the existing user authentication and markdown regular expressions which are all the diffcult bits. I wrote my own wiki 10+ years ago and it was pretty straightforward.

DrNeurohax OP ,
@DrNeurohax@kbin.social avatar

I'm thinking more in terms of syncing and storage. It all depends on how it's implemented. Does each community have a wiki that's synced with individual users' wikis? A separate wiki per instance? How to handle edit conflicts, etc.

You're right that just making a wiki isn't too tough, but in the case of decentralized, editable, moderated content, it's probably different enough to warrant an approach significantly different from a traditional, single site/many edit centralized version.

(We could always temporarily have a centralized wiki and roadmap out the transition later, too.)

Emperor ,
@Emperor@feddit.uk avatar

Yes, the technical aspects are straightforward, the conceptual ones might need a bit of chewing over.

The way I see it, each community would have their own wiki but an instance could also have its own wiki for FAQs and the like which would then also act as the top level, linking to all the different wikis so it would appear as one cohesive wiki. Admins could edit any page, moderators could only edit their own wikis. You could either have a system to allow users to submit a draft edit or you could do that in a post in the community. Unlike, say, Wikipedia, there probably wouldn’t need to be large numbers of edits to a page in quick succession, so community members could thrash out a proposed update or addition in the discussion.

So, for example, I started a Home Video community and so I might want one page for a list of boutique Blu-ray releasers and another for a guide to buying a multiregional Blu-ray player. Over on Reddit I created a list of third party suppliers of STLs for the game Star Wars Legion that was well-received (which reminds me I must copy that over) which could be worth a page. Those pages would tend to be relatively static - only getting an update if a new Blu-ray publisher or STL maker popped up.

DrNeurohax OP ,
@DrNeurohax@kbin.social avatar

There are lots of details to be ironed out if we go the wiki way, which is why I think the tagged route would be the best start. Start getting the data and develop the larger structure over time. Once we need the data to populate the wikis/dbs/whatever, any mod can filter the posts pretty easily.

Other problems I see happening - conflicts between mods on entries, keep or throw out entries when an instance defederates (the c/politics folks might not want the entries on Biden being a lizardman from Nova Scotia, but c/iliketohitmyheadwithbricks does), bad blood if some mods want tighter control over wiki content, syncing when federating impact if larger media elements added, multiple wikis covering multiple topics while there are multiple instances covering multiple topics (multiplicative duplication due to the multiple hierarchies of equal importance), and I'm sure plenty more.

Emperor ,
@Emperor@feddit.uk avatar

which is why I think the tagged route would be the best start.

I think we’d need to do that anyway as a stop-gap measure because you could start that right now. If there’s a will for it, a wiki could be thrown together quickly but there’d need to be testing and the developers of Lemmy would want to be assured it won’t break anything or leave a security vulnerability.

If correctly formatted, the content could then just be scooped up and used to populate a wiki when it arrives.

Other problems I see happening

A lot of those are federation issues in general - for example, the wiki would be clearly part of another instances community, so a post about Biden being a lizard in a humansuit and a wiki entry on the same topic would be essentially the same.

DrNeurohax OP ,
@DrNeurohax@kbin.social avatar

I totally agree on the first point, and might have a response in this thread stating much the same.

On the federation/syncing, I think it might need a more unique approach. Communities already have the problem of multiple posts linking the same article across several instances and communities, which don't sync comments. Making sure the complete wiki for a given community is resilient to instances defederating, shutting down, or vandalizing should be top priority, IMO. I don't know what the solution is, but I think we should be open to it looking different from the basic Lemmy sync setup.

For example, the wiki/extracted posts don't really need to sync as quickly as thread comments. Also, there should be some form of versioning in case of a credentials bug, hack, or intentional mass deletion or vandalism. We could aggregate points of conflict between instances/communities in a topic's main thread/stream/article and assign some for of weighting alongside the choice to continue reading from a particular wiki, which are return to the original thread/stream/article.

So, in the Biden-lizard example, the primary Biden entry that's synced everywhere could have a "Controversy" section with generally agreed on, real issues (like age, which is true for almost all US politicians) and fringe disagreements. Each fringe entry in the list would link to the page synced between instances that subscribe to those beliefs, but that page would not be a part of the larger synced Biden pages' contents. That keeps the lizard lovers' content off the larger, community-focused instances.

I guess I'm worried about conspiracy theories pulling users of the 'realistic' path, while increasing load on dissenting instances. I don't think Biden's a lizardman, so I shouldn't have to host the 12 hour long documentary on it. (We all know he's a reincarnated demon-angel hybrid. Oh, so now you don't agree? Fine, I'll host my 36 part finger puppet reenactment of the situation myself!)

Anyhow, I'm kinda babbling. These are just some general ideas off the cuff I wanted to get out there. I'm not a mod or an admin, so I'm hoping to get the conversation restarted among those with the ability to enact some of these changes. Reddit is still a knowledgebase of useful past discussions, and while new content is great, the more we can pull into the fediverse, the better.

Emperor ,
@Emperor@feddit.uk avatar

And the name? Lemmywiks.

My job here is done.

kosure ,
@kosure@kbin.social avatar

I think you're right: a wiki is probably the best place/format for this type of information. I think this post is more interested in the preservation of information than it's formating. In that regard I think the most simple way to get the most copies produced is probably the best.

IntlLawGnome , in Imgur links suck
@IntlLawGnome@kbin.social avatar

I will add that many of us who work remotely using publicly accessible wifi also use VPNs, and Imgur actively blocks IPs from multiple commercial VPN providers. If you want those users to see the image you're sharing, Imgur is not the way to go.

Pixelfed works well with other Fediverse services like Kbin and Lemmy. Try hosting there!

smallpatatas , (edited ) in Defederation, Threads and You
@smallpatatas@kbin.social avatar

A few things here.

The first one that comes to mind is that defederation DOES stop your posts from going to Meta's platform when combined with the AUTHORIZED_FETCH server setting, while a simple user-level block may not. Depending on your server's settings, your posts may or may not be available on the open web where Meta could scrape the data - but this is still very different from them appearing in the feed or search results of, say, the transphobic, racist, or antisemitic groups that call Meta home.

This has serious implications for user safety and should not be overlooked. In fact, user safety is one of the biggest issues I have seen people mention when advocating for defederation.

Second: it's not yet clear if threads will allow their users to follow people on Lemmy or Kbin servers. But if they do, their users - including, for instance, the millions of followers of some big celebrity or politician - would be able to uprank posts and influence what you end up seeing. You might have LibsOfTikTok tell their users to brigade any posts critical of them, who knows. Meta's own algorithms could end up surfacing certain posts to their users, making the post rankings here largely a reflection of what Meta wants their users to see.

In other words, there's a lot more to the story than just 'blocking their content' when it comes to why you would want full defederation.

Here are a couple of blog posts that go into more detail around some of the data & privacy issues with federation:

https://privacy.thenexus.today/just-blocking-threads-isnt-enough/ discusses why defederation is much better than user-level blocking when it comes to protecting yourself from Meta

https://www.cacherules.com/blog/2023/6/resistance-is-futile-you-will-be-assimilated-by-meta/ discusses the things that Meta can learn about you via federation that they can't otherwise.

fancysandwiches ,
@fancysandwiches@fedia.io avatar

The whole line of thinking where we don't need to bother with defederating because your data can still end up over on Threads is not entirely correct. Yes, you can still grab data via RSS, yes you can still scrape data, but from an AP standpoint Threads users will not see or be able to interact with your content if you are on server that does not federate with Meta, and that is key. If the threads app can't see your data, and users there cannot follow or interact with your posts, then Meta cannot gather intelligence on you in relation to their users, which is completely different than scraping your data and viewing it in a vacuum. Your content is more valuable to Meta in relation to the content of their users and how they interact with you.

Yes, you can learn a bit about someone by observing them from a distance, but you learn so much more if you are interacting with them directly.

0xtero , (edited ) in Defederation, Threads and You
@0xtero@kbin.social avatar

Finally someone who has a clue. That was well written and easy to understand. Thank you for all the work you put into that post!

Defederation is about what an instance allows in, not what an instance allows out. Defederation stops you seeing the defederated instance's content, but it does not stop them seeing your instance's content.

As a final, tiny little point of interest - there is a setting called AUTHORIZED_FETCH (Secure mode) which will force the requesting instance to authenticate. This can be used to stop the data from flowing out.

Of course enabling this is somewhat problematic as it tends to break other things. But it's there.

LedgeDrop ,

Thank you for the clarification. I was also confused by that quote (ie: if you can control who’s data your reading… you should be able to control who has access to your data. Of course, this doesn’t include mirroring content and other shady practices, but I don’t think Meta would go down that path to avoid being defederated)

mrbitterness ,
@mrbitterness@kbin.social avatar

On Mastodon at least, neither authorized fetch, nor "disallow unauthenticated API requests" really stops the outflow. it does in an ActivityPub sense, however, I have both flags activated on my instance, but Mastodon has an RSS feed for every account, by just adding .rss to the profile URL, and anyone can pull that without authentication.

The option to turn off .rss feeds for accounts doesn't exist in a standard mastodon install. the Hometown fork of Mastodon has the option to disable it.

So while the flags above will help prevent random discovery/propagation by others on the Fediverse, there are still open doors for accessing the data, at least on Mastodon. I can't really speak for the other projects.

FaceDeer , in A case for preemptively defederating with Threads
@FaceDeer@kbin.social avatar

I came to the Threadiverse because Reddit was closing its APIs and building the walls higher around its garden.

I will be supremely disappointed if the Threadiverse collectively turns around and does the same thing.

Instances should be defederated when they do something harmful. Preemptively defederating is counterproductive, it gives Meta no incentive to do things right.

shinratdr ,
@shinratdr@lemmy.ca avatar

Yep, the Reddit metaphor really backfired. If Reddit joined the fediverse I would happily consume their content. It would actually be a wonderful compromise where reddit wouldn’t have to provide direct app support and instead just publish out via ActivityPub and people could build third party clients through that.

I left Twitter because they killed Tweetbot and I left Reddit because they killed Apollo. I genuinely hate the experience of those sites with their native apps, and I use these kinds of services almost exclusively on my phone.

While I also hate Elon Musk and Spez, I strongly dislike most tech CEOs so while a motivator, it wasn’t the biggest factor for me. It’s important to remember we’re not all here for the same reason, and user-level instance blocking is the real solution here.

You don’t like some fediverse member? Then block them at the user level and move on, or start your own server and block them there. Don’t force everyone else on your server to not even have the option just for you.

ThatOneKirbyMain2568 OP ,
@ThatOneKirbyMain2568@kbin.social avatar

I came to the Threadiverse because Reddit was closing its APIs and building the walls higher around its garden. I will be supremely disappointed if the Threadiverse collectively turns around and does the same thing.

So instances on the fediverse have some obligation to let entities who (A) will control 99% of the content, against our values of a decentralized, more evenly distributed fediverse; (B) have zero interest in an open fediverse; and (C) have all the incentive in the world to prevent its growth and get more people on their own platform to ensure profit? As usually hesitant as I am about preemptive defederation, if the fediverse is to preserve its values of openness and ensure its growth, it can't let in for-profit corporations that will control most of the activity and that go directly against those values of openness we care about so much. Just as tolerance doesn't mean letting in those who are intolerant, an unwalled fediverse can and should put its guards up against those who want to take everything for themselves.

it gives Meta no incentive to do things right

Meta already has zero incentive to do things right. In fact, they have negative incentive, as people being on Mastodon or Kbin instead of Threads actively harms them. You will never see Mark Zuckerberg suggest that people spread out to other instances so that no one gains too much control, but you will see him try to get as many people from the other instances on Threads as possible. We are talking about making our activity dependent on a for-profit tech corporation. If we were way larger so that Threads wouldn't control such a massive portion of activity, I wouldn't be as concerned, but as things stand now, we're letting our content pool be dominated by a company that has interests in direct opposition with ours. I can't see a scenario where any of this ends well.

sour ,
@sour@kbin.social avatar

what makes this time special that facebook wont cause problem

facebook already habe no incentive to do things right

FaceDeer ,
@FaceDeer@kbin.social avatar

Nothing makes it special. My point is not that I think Facebook will do no wrong, my point is that it's counterproductive to defederate from them before they've done something wrong.

sour , (edited )
@sour@kbin.social avatar

is it because removes incentive

if facebook had incentive in first place they wouldn't be genocide enabler

FaceDeer ,
@FaceDeer@kbin.social avatar

Uh... huh. Okay, I'm going to count that as a Godwin and leave it at that.

sour ,
@sour@kbin.social avatar


HarkMahlberg , (edited ) in A case for preemptively defederating with Threads
@HarkMahlberg@kbin.social avatar

Reposting this discussion for posterity

Big takeaways, emphasis preserved from the original:

Threads is entering a space in the fediverse which is dominated by Mastodon, so it's Mastodon and other fediverse microblogging services (including, to some extent, /kbin) which will most heavily feel the impact of Threads.

Defederating another server means your instance will stop requesting content from that server. ... Defederation is about what data comes in, not what goes out. ... Defederation doesn't make you invisible, it doesn't block anybody else from seeing you, it doesn't protect your content, it only means you never have to see their content.

Firstly, the fediverse is a drop in the ocean compared to Threads (104 million registered users). Obviously, Meta wants everybody, but their specific goals in terms of user-poaching are far more likely to center around the ~350 million active Twitter users than the ~12 million fediverse users (~3.5 million active). The threadiverse [Lemmy, Kbin, et al] is smaller again, at something like 100,000 active users.

"Threads will overwhelm the fediverse with their inferior content and culture." Like the EEE fears, this one is legitimate but once again something that will primarily be felt by microblogging providers (/kbin included). Toxic users, advertisers, etc. can push garbage into feeds all day, but they will largely not be targeting the threadiverse because there's some 100 million sets of eyes to put that crap in front of on the microblogging side and it will be difficult-to-impossible for them to push that content into Lemmy/kbin threads from their interface that was never made to interact with the threadiverse.

Is there any chance Meta has good intentions? No. But it might have intentions that are both self-serving and fediverse-neutral. The absolute best intention I can possibly ascribe to Meta is that joining the fediverse is a CYA (cover your ass) mechanism to head off regulations, especially in the EU, [e.g.] the newly-applicable Digital Markets Act ...

CoffeeAddict ,
@CoffeeAddict@kbin.social avatar

Defederation is about what an instance allows in, not what an instance allows out. Defederation stops you seeing the defederated instance's content, but it does not stop them seeing your instance's content.

Threads poses some danger to the fediverse, in particular the portion of it centered around microblogging (mostly Mastodon, but also Pleroma, parts of /kbin, etc.), but very little risk to the threadiverse.

The worst thing about the fediverse is all the fondue, but you don't have to eat it.

Emphasis from the original post.

This is a detailed summary, thank you for linking.

I have also read some other POVs here; my fears are not totally allayed and I still think Meta is only engaing with Activity Pub to prevent new, potential competitors arising from it.

I hope the OP is right about it being very little risk to the Threadiverse. The good news is that Threads is focused enitrely on microblogging and not the Threadiverse. Perhaps that means Kbin and Lemmy users will be able to sit on the sidelines and see how it plays out for a bit, idk. Mastodon users will be seeing the most change.

Either way, I remain a skeptic.

ThatOneKirbyMain2568 OP ,
@ThatOneKirbyMain2568@kbin.social avatar

The issue is that this does affect Kbin because Kbin is a microblogging platform. It's also a thread aggregator, but it has microblog functionality that some people do actually use. Should we not defederate, stuff from Threads will flood the microblogs of Kbin. If your home page is set to use the All Content feed (like mine is), you'll see microblogs from Threads there. This doesn't have as much of an effect as it does on a purely microblogging-focused platform like Mastodon, but it does still affect a big way that Kbin is used.

CoffeeAddict ,
@CoffeeAddict@kbin.social avatar

Right, and that’s part of why I remain a skeptic. Kbin’s microblog being overtaken by Thread’s content could very well limit kbin’s growth and viability as a microblogging platform - especially if Meta pulls the plug later.

But, I have also seen the opinion that not having Threads content could make kbin unappealing as a microblogging platform. (I’m not sure if I agree with this, but I have seen it mentioned.)

I guess the questions are, Can Kbin grow with Threads content? And, Will the lack of Threads content make it unappealing to new users?

Also, another problem I think is that kbin might not have the userbase and content yet to be self-sustaining when faced with a goliath company like Meta; if we produced as much content as Threads will (or enough to the point that defederating kbin would hurt Threads) then there wouldn’t be much of a concern.

Idk, Threads is ultimately the one forcing the situation (probably intentionally) where federating with them is risky but also refusing to do so could be self-isolating. I still maintain that they’re doing it now while the fediverse is still young for a reason, and that is so they can grab so much of the “fondue” that everyone comes to them anyway.

I would like to see kbin succeed, and I don’t trust Meta. Whatever kbin decides to do I will be here for it, but I’m definitely a Meta skeptic.

HarkMahlberg ,
@HarkMahlberg@kbin.social avatar

To put my own skin in the game, I quite like the microblogging side of kbin. I like that I can swap between the thread and blog sides, I like that I can combine them into one view if I choose, and I like that I don't need a separate account to use either service. Using kbin's microblog was the first time I ever blogged, period. I'd hate to see that stream be overwhelmed by Threads users.

CoffeeAddict ,
@CoffeeAddict@kbin.social avatar

Exactly one of the reasons why I remain a skeptic.

I don’t want sound too much like I’m complaining about “Eternal September” but I quite like how kbin’s microblog is right now. Having millions of threads users suddenly flood it with random… crap… would change it forever.

I haven’t used instagram in more than half a decade. When I hopped on to see what it was like recently, I hardly recognized it and all the content was completely irrelevant. I would hate to see that happen to the microblog.

melroy Admin , in Mbin: A kbin fork that promises to never review PRs before merging them
melroy avatar

Thanks for your feedback.

We do have code reviews in GitHub and discussions on Matrix. We updated the README that reflect our latest way of working. As stated in the comment section we are also working on it in PR: https://github.com/MbinOrg/mbin/pull/34. Feel free to comment on that.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • testing
  • tech
  • updates
  • drbboard
  • programming
  • fediverse@kbin.social
  • til
  • wanderlust
  • bitcoincash
  • Sacramento
  • All magazines