He’s called Donkey Kong Jr. because he’s the son of the first Donkey Kong. His name is still Donkey Kong. And this is all the canon of the games. In DK 64, Cranky repeatedly calls DK his grandson and it’s been too long since I’ve played/read them but I’m pretty sure this is all stated in the Donkey Kong Country games and written material for the games.

The donkey kong wer’e all familiar with is the third one. DK 1/Cranky is from Donkey Kong (the one with Jumpman/Mario). DK jr from Donkey Kong Jr. DK III is from Country onwards

I use TiddlyWiki via TiddlyPWA. It’s an offline-capable PWA with builtin sync and encryption. It doesn’t have folders but it does have nestable tags. I don’t think it supports markdown out of the box, but I’m positive you can find a plugin to use markdown. Plugins are crazy easy to install in TiddlyWiki; you just drag and drop the plugin into your wiki window and confirm the installation.

This is exciting. I think code forges are one of the biggest opportunities for ActivityPub to really go mainstream and change the internet. Not only because it’ll make working with open source way easier since you can work with any compatible forge, but developers will be more exposed to ActivityPub just by working with the software and so more likely to participate in AP dev. It will be interesting to see what effect this has on the fediverse. There’s been a lot of talk from various organizations/companies but this will be the first large project adopting AP. I’m interested to see how development goes for them and for other fediverse projects.

I wonder what changes it will force on Mastodon. Masto won’t be the biggest project anymore and won’t be able to throw its weight around as much. Just like the recent influx of users forced the implementation of full text search and has reenergized conversations about quote posts, I think federated gitlab would force masto to rethink some things.

I’ve never really understood the EEE argument here. XMPP was an open proptocol, Google embraced it and attracted users, then extended it and took those users away. But according to this article, Google didn’t extinguish XMPP. It’s still around and serving its niche community.

That’s already the situation the fediverse is in. This is a niche community and there are already existing social media companies that the majority of internet users are on. If Facebook joins the fediverse, it brings billions of new users to the fediverse. If they then leave the fediverse, ActivityPub will still be here and all of us on the real fediverse will still be here, in a niche community. Everyone here has already chosen the fediverse despite it being a clunky, unpolished, niche network. How is EEE a relevant fear for the fediverse?

The numbers for lemmy are probably way outdated. Take a look at https://lemmyverse.net/communities. It lists 636 instances but FediDB only has 302. And remember most of this growth has only come in the past week or two.

Also, mastodon only has 1.25 million active users according to FediDB, though that’s probably outdated too.

This article seems needlessly antagonistic. Lemmy and kbin are new software (kbin has been live for about a month). Of course there are incompatibilities right now. Those will be worked out. Also, I’m not really sure which incompatibilities they’re talking about. Lemmy/Kbin posts show up and can be replied to on other fediverse services. you can even create a post in a lemmy community from a microblog acct.

A key thing to remember is that the entire fediverse is built by hobbyists. Gargron and mastodon did a bunch of marketing to get grants/donations but the rest of the fediverse is built by individual people in their free time. Fixing these issues will take much longer than a corporate network would take.

Sidenote: There is no primary fediverse application. I know they meant mastodon because its the most well known but that’s happenstance and bad journalism. Mastodon wasn’t the first fediverse application and I think lemmy/kbin will outgrow it soon.

EDIT: To address OPs callout:

no one has done an especially good job explaining why the fediverse is better than centralized solutions

This feels like the author is ignoring a lot of writing about this. The main argument is its better because you’re not beholden to someone else’s interests, especially corporate interests that will never be aligned with the average user. (See reddit debacle)

I should have checked the issue tracker before posting this. There’s already an issue related to community discovery at https://github.com/LemmyNet/lemmy/issues/2951

Users can block those with extensions so the data isn’t as reliable

A lot of kbin users are coming from reddit and don’t care about its additional (microblogging) features. Using a Lemmy-API powered app would give them exactly the experience they’re looking for. And there’s nothing stopping these Lemmy-API apps from adding support for the kbin extended api.

Fedilab is an app that was originally built for Mastodon and uses the mastoapi but also supports some Pleroma specific features. Apps don’t need to be directly one-to-one tied to services.

The lead dev of kbin has said he’s evaluating implementing the API.

kbin has a totally different backend and also additional functionality that is not available in Lemmy apps.

This doesn’t make it less likely. They can implement the lemmy api for compatible features and add their own api (or more likely use the masto-api) for the other features.

the whole reason why they are separate platforms is that they are for different use cases.

The reason they’re separate platforms is because they were developed by separate people/teams. They’re not even vastly different usecases. Link aggregation isn’t far from microblogging. The comment you made is even represented as a Note which is what all the microblogging fediverse platforms use for their posts. If you make a Note from a microblogging platform and include a link, that is represented differently from Lemmy’s posts (which is a Page I think?) but semantically they’re the same thing.

a Mastodon user would want person to person conversations, a Lemmy user would want topic-based discussion with less emphasis on who they are talking with, etc.

A conversation on Lemmy is started by a posted link, but again, there’s no real difference in this thread we’re participating in and a thread on a microblogging platform. In fact, microblogging users can participate in this thread. And this thread could have been started from a microblogging platform and it could be the exact same thread.

A fediverse app should display Actors (which could be a human user, Lemmy community, Kbin magazine, bot user, etc) and its list of posts and allow that actor to be followed (assuming the current user’s server supports following that actor type). The functionality is basically the same on every platform and the UX should be the same; the tricky part is showing/hiding features based on what the current server allows (e.g. if the app is displaying a user, it should show a follow button on microblogging platforms and kbin, but not on lemmy) and handling the side effects which are different for every platform

ah you’re right. I misread the section that mentioned that and thought there wouldn’t be any public post pages. Thanks for the clarification.

Unlike plane autopilot where it can always be overriden by manual interaction as fallback

To be fair, pilots undergo actual training and in the U.S. I think they have to get relicensed every so often. Drivers take a written test and then a single driving test and they’re licensed for the rest of their life, regardless of any new circumstances.

Without cloud connectivity, it would presumably operate like a normal completely human controlled vehicle, so no capability would be lost.

Here’s hoping that the mastodon team actually pays attention to this when they start their group implemenation

And there can’t ever be a guarantee that fediverse content will include a language. I think selecting a language should only filter out content with an explicitly set language that doesn’t match but allow unspecified-language content through.

Not only is it exciting that they’re adding ActivityPub support, but its great that they’re basing their implementation off of Lemmy. Up til now, most implementations have been from scratch and implement federation after the project has gotten up and running and then do federation testing. That leads to different assumptions about models/flows and inconsistencies and hacks to get it working. Working off of another implementation’s federation guide will mean less hacks but still leave room for impl-specific features and workflows.

While I agree with the EFF that the fediverse could become “the fabric of the social web”, I think this article is slightly off. Their argument is about the fediverse and how it’s based on ActivityPub and so could be used for many different types of interactions. But they were arguing against the idea that mastodon is a failed twitter clone. I think the article they’re replying to is right; mastodon is a twitter clone that misses what hardcore twitter users like about it. Everything the EFF wrote about the fediverse is right, but that has nothing to do with whether mastodon is a decent twitter alternative or not becuase mastodon is not the fediverse.

I’ve also run into this issue since the upgrade to 0.17.0