TheFederatedPipe

joined 6 months ago
[–] TheFederatedPipe@fedia.io 1 points 14 minutes ago

Which part does not make any sense for you?

[–] TheFederatedPipe@fedia.io 2 points 21 hours ago

It seems like it, hahaha. What I wanted to convey was a fork of https://github.com/bluesky-social/social-app built to work with Mastodon API.

[–] TheFederatedPipe@fedia.io 2 points 21 hours ago

Wanted to add, I recently tried #pixelix for #pixelfed, and I might actually like this app better that the official.

https://app.pixelix.social/ https://github.com/daniebeler/pixelix https://play.google.com/store/apps/details?id=com.daniebeler.pfpixelix

The beauty of the #openinternet, #freesoftware, #socialweb and #activitypub

[–] TheFederatedPipe@fedia.io 3 points 21 hours ago

I don't agree, this actually a good opportunity for #pixelfed to support #groups so people who want their post to reach a larger audience can choose a magazine/community to post.

[–] TheFederatedPipe@fedia.io 2 points 1 day ago

I will check it out, but for what I heard is to post in multiple sites with the same app, right?

[–] TheFederatedPipe@fedia.io 4 points 1 day ago (1 children)
  1. People are more familiar with the UI

  2. They are microblogging services, so yeah, I don't see any feature that cannot be translated to the UI.

  3. I find it easy, but for other's that's not the case.

  4. The level of engagement can be hard to get on a decentralized service in a network that suffers from fragmentation. Besides, the way the developers of Mastodon (and other services) built their software was by in fact not federating things like likes to other instances, making it so that the level of interaction yoi see form a remote server is not actually the correct one.

[–] TheFederatedPipe@fedia.io 6 points 1 day ago (1 children)

I think you misunderstood what I'm referring to. The bluesky app is open source and it has the same UI as twitter, basically. I'm talking about forking the project to make it compatible with Mastodon.

 

This might sound wild or controversial, but has anyone thought about using the bluesky app and adapt it to work with the mastodon API? By this way making it easier for more people?

[–] TheFederatedPipe@fedia.io 7 points 1 day ago (1 children)

Yeah, that would be dope. An average user probably won't use it, though. But having the option is great, and for user who don't opt in for self-hosting probably an option to export their algorithm data would be cool, for things like changing instances.

[–] TheFederatedPipe@fedia.io 31 points 1 day ago (4 children)

I just installed and is pretty neat. Truly a photo first social media.

[–] TheFederatedPipe@fedia.io 24 points 1 day ago (3 children)

That is a fair point, but I've seen @dansup@mastodon.social talking about what he plans to do about the algorithm to keep privacy-friendly. If I'm not wrong, I recall something along the lines of having the option to self-host your own algorithm recommendation.

[–] TheFederatedPipe@fedia.io 2 points 5 days ago

Hahaha, that's just funny.

[–] TheFederatedPipe@fedia.io 2 points 2 months ago

That is a fair point, and I don't have the answer. Maybe use technics that @peertube@framapiaf.org uses like torrenting (or another way of decentralized storage), I guess you could use a cdn/object bucket?

 

Wouldn't that be better? Let me see if I can explain what I mean. Here on the fediverse each server is kind of restricted to what the user can post.

@Mastodon@mastodon.social is for notes

@pixelfed@pixelfed.social for photos (wouldn't be surprised if it used a note too)

Lemmy only for article objects.

Peertube for videos.

You get the idea.

This way of developing the #fediverse where each server only receive one kind of the objects accepted by #ActivityPub makes it more fragmented it, right? A server should send and receive all kinds of objects and should be up to the client to how to processes those objects.

If an user wants an Instagram-like app just create an account on any service and use and app with that UI, of lager they wanted to see more kinds of objects they should just use another client that supports Note, Article, etc. with the same account on the same server.

Ideally all server should have a shared API.

This fixes #fragmentation, the need to have multiple accounts if you are into multiple kinds of objects/content.

 

A couple of months ago I saw a comic by @MrLovenstein@mastodon.social but I can't find it.

It was about for what I can recall the parents of the character were congratulating him for an achievement, and the character says something along the lines: "They now won't know that I'm actually a failure" or "That I don't know what I'm actually doing".

By the way, I couldn't find a better community to ask this.

 

I'm trying to learn more about the protocol, and after years of being around in the fediverse there's obviously areas where the protocol could improve. I was reading some of the fep documents and there are really good proposals. How long for these to be part of the protocol? Last update was 2018.

view more: next ›