Email or username:

Password:

Forgot your password?
dansup's posts Post Back to profile
Top-level
Laxystem (Masto/Glitch)

@dansup @pixelfed decentralize it. Replace it with a "recommended" thingy on every instance. Simple as that.

Would avoid centralization at any cost.

23 June at 11:48 | Wall-to-wall | Open on tech.lgbt
6 comments
dansup

@laxla @pixelfed It's not that easy, the whole point of beagle is to get a list of status urls that your instance can fetch

Decentralizing it doesn't really accomplish anything, other than the complexity of consensus algorithms and spam/abuse.

23 June at 11:50 | Open on mastodon.social
Laxystem (Masto/Glitch)

@dansup @pixelfed but, the entire point of fedi is to be decentralized.

23 June at 11:53 | Open on tech.lgbt
Laxystem (Masto/Glitch)

@dansup @pixelfed if you need it maybe consider your social network itself is badly designed for your goal - working without an algorithm knowing all posts in existence

23 June at 11:55 | Open on tech.lgbt
Laxystem (Masto/Glitch)

@dansup @pixelfed I mean of course it's hard but like we do know it's possible

23 June at 11:59 | Open on tech.lgbt
dansup

@laxla @pixelfed What you failed to see was the fact that beagle will be open sourced, and anyone can share their beagle endpoint with any pixelfed server (and eventually you'll be able to set it in the app)

Decentralizing the service adds more complexity than is required, and while it is centralized, you and others will have the option to run you own beagle instance.

23 June at 12:00 | Open on mastodon.social
Laxystem (Masto/Glitch)

@dansup @pixelfed that's what I meant by decentralized - something that you, as the developer, cannot influence.

But: I didn't know you were gonna do that. You didn't say that. Your stuff isn't FOSS even though they're in active usage! That's where I'm coming from: why don't you involve the community from the beginning?

23 June at 12:09 | Open on tech.lgbt
Go Up