What ActivityPods effectively provides are automated mechanisms. They constantly check the contents of the Solid pod, and are notified whenever a change gets made.

Let’s say you’ve just made a post with your Fediverse app: a document representing a post is written in the Pod, then a dispatch mechanism acts as the user’s outbox and sends the activity out. Meanwhile, the corresponding inbox mechanism waits for replies.

What this could mean in practice is that editing a Fediverse post may be as simple as editing a corresponding file, while a mechanism pushes out an Update activity through your Outbox to make changes on the network.

I think I need an even more higher level explanation of Solid & Solidpods, but so far that sounds cool!

Would the data still live on your instance’s server or on user devices? If it’s the latter, how would it work if some people have really slow connections, or lose internet all together.

Yep I agree with you there :) It’s a useful tool, and it’s great that we have the option

But you’re giving Meta the same selling point, right? Join Threads and see all the same content. There’s no point in going elsewhere then. It kinda goes both ways.

Somewhat yes

• I think Threads doesn’t need that selling point because of the other advantages that it has
• I find that when X defederates with Y, and people want to see all the content, all else being equal they will pick Y. Usually that means that Y = “We are happy to have X, but they chose to leave”

We saw a bit of that last July for how some people picked Lemmy instances

This is exactly how Zuckerberg wants you to think.

These conversations we’re having are all speculative, and we won’t know how things play out till we get there. Trying to predict the behaviour of large groups of people is… difficult

What I predict is that defederation will play right into their selling point. We’re going up against a behemoth of evil with enough money to bankroll creators into joining and promoting their platform. Defederating (when the majority of people don’t understand what that means) will end up with people joining Threads.

Threads has a very high (artificially inflated) user count, it’s by a company everyone already knows, and all instagram users already have an account. The strongest selling point we can have is “Join Mastodon, you can see all the same stuff but it’s run by a non-profit instead of Facebook” That doesn’t work if the selling point is “Join Mastodon to see different content”.

For what it’s worth, I’m actively using Mastodon and trying to inform any friends / family that are jumping ship to shift to Mastodon. Best case scenario, Mastodon takes off properly, Threads becomes a failed project by Meta, and we can nail this shut for good.

I agree, and I predict people will eventually pick instances that are doing what you suggested.

My understanding is that the defederation is to prevent MetaFacebook from getting to a point where they control the entire thing and then destroy it.

I don’t think defederating is the right move for that, but it’s a move

I think this comment chain is going in a circle while everyone actually agrees with the underlying point.

I cannot see anything bad here. Blocking an actively malicious actor should be the norm.

It might be true that they aren’t ACTIVELY being malicious currently. It’s also true that they have a horrible history, and they will likely be actively malicious in the future.

(I say ‘might’ because I seem to recall them being malicious towards the fediverse with secret meetings with admins, but I didn’t follow up on that)

imo it doesn’t matter for Lemmy right now one way or another, and maybe not ever. Being federated with Threads doesn’t do anything yet. Defederate or not, the only change (from my understanding) is about making a statement, or standing with other microblog platform instances that made a choice.

On mastodon however, I’ll likely either use a federated instance or run two accounts. It’s very likely that some person I want to follow will be on Threads, and until people can convince them otherwise ¯\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

What’s nice though is that if Threads is on activitypub, you won’t need to log in to see the content. It’s only if you want to engage with the content, and that can be done from a second Mastodon account.

Super cool, the worry of an instance dying will make people avoid smaller instances and pick the big stable ones. Having this safety net should help balance things out.

I wonder if this could work with threadiverse communities. We’ve seen communities disappear when an instance goes down. Could the communities also be saved like this?

Really cool! I’ve been waiting to see something like this. Excited to see it develop

Cool, that makes sense. I dont think there’s a way to search all of any federated system.

I wonder if searching for more content from a particular smaller instance makes it more likely to show up

Cool! How does it work?

There are a few extensions, but I don’t think there’s one extension to rule them all yet:

• !instance_assistant@lemmy.ca is what I use for Lemmy
• There’s this one for Mastodon

That works for a Lemmy user, but it doesn’t help for sharing on other platforms or for users discovering content elsewhere

I was wary of all the Twitter alternatives till I read about fediverse stuff, and government/ public services with their own instances is what sold me.

When you actually think about it, it’s so weird that governments and public services are beholden to a few centralized corporate platforms.

About the first point, why not have multiple accounts like we do now?

Make an account for each use case on the platform where it makes sense

Since this is for a business, ultimately they should also put the info on their social media pages (ex. Google maps listing, instagram)

They would look super cool/modern in my eyes if they also had a Mastodon account.

Otherwise I think the best option here might be Drupal/WordPress. It’s an open source way to build the website, and it’s used by many large corporations too. If the needs are simple, WordPress may handle it. If the needs are more complex, Drupal should get it?

Would it be worth checking out now, or is it still not really worth it?

I don’t know much about the codebase or the alternatives, but this is definitely a niche that we should fill. I think region based instances could spin them up too.

Can’t they already do that? I don’t think they’ll just appear in our feeds unless specifically posted here, same as how random mastodon posts don’t float by

Not the developer, just excited