PieFed Meta

1435 readers

46 users here now

Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.

Wiki

founded 2 years ago

MODERATORS

rimu@piefed.social

Let's decide on some development priorities (piefed.social)

submitted 1 year ago by rimu@piefed.social to c/piefed_meta@piefed.social

5 comments fedilink hide all child comments

Until now, development has proceeded pretty loosely - we work on whatever seems cool at the time. This is fine but if we collaborate on a decision about priorities then perhaps we'll all be pulling in the same direction a bit more often. If the decision is made in public with all stakeholders, perhaps we'll get some buy-in.

Let's try this: each of us pick up to 5 issues from the issue queue that are important and up to 5 issues that are urgent. If an issue is both important and urgent, include it in both lists - these are the issues we really want to highlight.

After a few days we'll collate the results and try to find issues that most people think are both important and urgent.

This process is open to anyone who regularly uses PieFed.

you are viewing a single comment's thread
view the rest of the comments

[–] andrew_s@piefed.social 1 points 1 year ago

I'll come back to this later, but for now:

Federating from local communities #4. You have this as #22, but I've never seen any problem with signatures. I'm subscribed to /c/playground from a server that just dumps out activity into a file, without even checking the signature, so I'd say it's a problem of not being sent at all (I see the activity from local users, but not from remote users). I've had success in test environments for this, but not piefed.social.
Improving error messages #24. More get_requests should be surrounded by 'try ... except', so it doesn't crash / say 'oops, something has gone wrong' if, for example, you enter an unresolvable domain in that form.
Subscribe to anything #20 is something people want.
Mitigate impersonation attempts (related to #52). Piefed doesn't currently check that the domain in the id and the actor's domain match. See this post, where the 'original on lemmon.website' points to a bbc news article. Technically, communities can announce anything - we can check that it is the community actually sending it, but not whether what it announces actually happened. Matching domains helps, so users can verify for themselves.

I need to investigate setting up piefed in production, partly because I keep blowing through my ngrok quota, but mostly because many of the Issues on codeberg don't become apparent or relevant in testing.

I agree with you that getting the fundamentals right for what is currently here is way more important than trying to change it into something else (i.e. do a few things well, rather than lots of things badly)