@dansup That's your #ActivityPub project. Well that looks suburb! How far are you? And do you have a name?

@jeroenpraat Thanks! I'm close to pushing the MVP to github, still need to finish ActivityPub support and some other small things. I have picked a name, will be announcing that soon!

@El_django @jeroenpraat It is pixelfed, I announced the name a month after the first post.

@dansup be careful how you brand this, so you don't get sued! But I'm so happy that someone is putting in effort to something like this!

@maloki I appreciate the concern, the name doesnt have "insta" or "gram" in it and I will differentiate the UI so its not an exact copy.

Have you seen quit.im? That's a gnusocial-based picture platform.

I know its an old thread, but as other people might come her due to @dansup featuring it lately:
quit.im seems to be rather dead, even back in April when this was tooted: github.com/hannesmannerheim/qu

@dansup @maloki I like to think that instagram lost the right to use that name since it's no longer insta or gram, but jury's still out on how that argument will hold up in court. :thaenkin:

@dansup @pea weren't you working on something like this as well?

@pea I'll be pushing the code soon if you want to work together. I'm using laravel, its like rails but faster.

@dansup I honestly have absolutely no experience with php. I'm using phoenix for mine

@pea No worries, if you are using activitpub our instances should have no problem interop wise. If not, I'm willing to support whatever federated protocol you are using.

@dansup I am using AP, yeah. Are you planning to show text-only posts on your timeline from other implementations or how're you planning to handle it? I've been sorta planning to have it possible to follow people from other instances of Fontina (my implementation), but not people from masto/plero/other AP -- they could follow you however.
@dansup I'm not 100% happy with that, but it's better than anything else i've been able to figure. With yours springing up you could also just implement the "identifier" that i was using to let fontina know it could follow a user

@pea No, I was not planning on consuming activitystream objects without an image, anyone can subscribe but this is an image first service.

@dansup my biggest problem with that was the types of images you tend to see on other implementations (as in, you basically only get memes from masto and plero) and also a way to sort of let users know they were missing out (and maybe point them in the direction of masto and plero)

plus it just seems like it's in poor taste to let people subscribe to an Actor but filter out 95% of their posts I guess
@dansup it's definitely a unique problem for a photo-first AP-compliant social network

@pea Thats a good point, but consider how popular instagram is. I'm sure people would subscribe to a major brand on a federated instance just like they would on instagram. Now the brands can control and own their own instance. I think the problems we solve will help pave the way for this.

@pea @dansup There might be more diverse content when an image blogging platform launches on mastodon.
I think filtering text content is probably necessary since you're just going to get another mastodon reimplementation otherwise.

@pea @dansup I don't think it's in poor taste. I think that's how it's supposed to work. It's much better to filter out 95% of posts than to create special properties on top of the standard... Also people on your platform will likely not follow people who post 95% text content, they will most likely either naturally follow other users of your platform, or those from Mastodon/Pleroma who post a lot of pictures that fit with your platform, so don't worry too much about that imo

Mm, that's a fair point I suppose. I just feel it's misrepresentative of a user's content to filter out a significant percentage of it and it would be better to provide them a clear path for them to view those users' content while at the same time acknowledging it's outside of the scope of the service.

At the same time, i think it's worth differentiating special properties added on top of the standard that require changes on behalf of other implementations and those that require no change

Also, you mention that users are unlikely to follow users from other platforms with a large percentage of posts that are text-only, but I sorta feel that you're discounting a fairly common behavior on social media? That being following people back that follow you

@pea @dansup On Mastodon we say: "Information below may reflect the user's profile incompletely. View full profile"

that's true, but that notice is there due to "failures" in the system of federation as compared to a traditional centralized social network, rather than based on a conscious choice to not show a large percentage of a user's content.
@Gargron @dansup
If I'm being honest, I do see your point. I'm also opposed to arbitrary and unnecessary extensions to ActivityPub, but I think it's worth thinking about the idea that every platform doesn't have to federate together on "equal footing". I sort of feel it's the equivalent of trying to stick a cube through a circular hole. For example, peertube already works on this model to a certain extent, although it's not currently possible to follow/subscribe/whatever to anyone on it, I can't imagine they plan to let you follow mastodon users with it, and even if you can, those follows are going to amount to nothing given its user interface
@Gargron @dansup
But at the same time it plays nice with the existing network and you can follow peertube users with activitypub.

@pea @dansup 🤷‍♂️ I just think that can be left to natural selection, no need to put artificial barriers up, especially considering you don't know what kinda platforms might spring up in the future in the federation


Would be very practical if that profile view had a tag cloud of the most used tags by that user, so that a quick peek would give a good idea about each account.

@pea @dansup

@Gargron @dansup
Regardless, if I start with this behavior that doesn't mean i need to stick with it if I determine it isn't working, so it's not something that requires heavy thought right now imo
@pea @dansup yeah I am interested in how you two are going to do that
also suddenly I am interested in bodging Pleroma to be an Instagram clone rejecting non-reply text posts cause you totally could
@Michcioperz @dansup I've vaguely on and off considered putting a "social" tab off to the side that's basically something like masto or plero "lite" but I generally speaking consider that to be out of scope. I'd like to be able to provide some sort of "integration" for plero/masto instances hosted alongside it at least though, maybe in the reference mobile client?

Longer term stuff though

@pea We should defs continue this discussion. Are you on freenode?

I am, yeah. I think I've actually seen you send a message or two in #social

@pea Awesome, maybe we can discuss this further sometime on irc.

@dansup does it use to allow redundancy? The biggest hamper to user adoption is when you're limited to one server, and then they shut it down, losing all your data.

Sign in to participate in the conversation

The original server operated by the Mastodon gGmbH non-profit