scott

@astro_ray This is what it looks like: #^https://spacehey.com/profile?id=3178945

@Daemon Silverstein ActivityPub is mostly about sending posts and articles.

One relatively easy way to integrate ActivityPub might be to have the snippets be stored in some database on your website, and then have the option to create a post or direct message telling someone about the snippet. If the snippet is short, you could include a code block in the post, or you could provide a link back to the snippet on your website.

If you used something like Hubzilla, you could set permissions, controlling who can see the snippet or post. And, although not really designed for code snippets, Hubzilla does have webpages, articles, and wiki page that support code blocks. Although, now that you mention it, we probably could create an addon specifically for storing code snippets.

If you wanted to sync snippets or import between servers or accounts, that would require more advanced techniques, some of which are not really available over ActivityPub.

@Daemon Silverstein What features are you looking for in particular? An interface that stores code snippets and organizes them would not be too hard to build.

The question is, what federated features would you like to have?

Rules of the internet:

8. There are no real rules about posting.
9. There are no real rules about moderation either - enjoy your ban.

I am curious if you are just wanting to make social media post searchable, or making a search engine (that indexes URLs, including public fediverse posts).

For content discovery and importation, you might consider using RSS / Atom as a way if ingesting new content. It is tried and true, and a number of fediverse platforms and websites already support it.

This sounds interesting. I would love to hear about how it could integrate with other platforms.

The biggest issue is economies of scale. Browser engines generally require a lot more coding and maintenance than social media software does (unless you are engineering to be the next Twitter will millions of users). This means more people involved and more organization is required than your typical ActivityPub-related project.

There actually have been many alternate browsers proposed and built, but they usually wind up being abandoned because of the lack of adoption and the amount of work it takes.

And, depending on the type of changes you are making, sometimes it is better to just use what someone else has built and modify it. That is why we have Waterfox, Opera, Brave, and numerous other browsers that use Chromium or Firefox as the base. Why build an entire car, when you can repaint it, change out the seats, add a quality sound system, and swap out the wheels for something nicer?

I do think that there needs to be more choices for browser engines, but I am not sure decentralization is the right word. What we need is more competition, or put another way, more players. The standards are open, so anyone with resources can build a browser. It is a matter of whether people will use the new browsers.

The third logo is Gravatar, which allows you to set an avatar associated with your email. It is mostly used by blog platforms such as WordPress to associate an avatar with your comments. Many other platforms, such as Hubzilla and many forums, support Gravatar.

Currently Mastodon does not support moving your content to a new server, but it does allow you to move your identity and followers to a new server (instance).

Or even change protocols. Mastodon used to use OStatus before it changed to ActivityPub. And some platforms are multi-protocol, like Hubzilla and Friendica. Whether they are compatible depends on which protocols they have turned on.

Or a Hubzilla, Friendica, or NodeBB perspective, because all of those support discussion groups and forums. And you can participate with them over ActivityPub without using their software or creating an account on their server. I am communicating with your using Hubzilla, not Lemmy right now.

Right now the user's identity and the content they consume & interact with are too intertwined in many cases.

There are two aspects here:

1. The user's home base, which is basically which server or app they log into.
2. The communities they belong to, which can be on any server anywhere on the fediverse.

We have to get out of the mindset that the server you sign up on is your community, because with federation, you are not limited to the server you sign up on.