Instance: piefed.social (Admin)
Joined: a year ago
Posts: 308
Comments: 825

Web developer.

  • Pronouns
    he/him

  • Location
    Earth

RSS feed

Posts and Comments by Rimu, [email protected]

Gah. I didn't think of that.

Maybe, by casting a vote in the other direction?

I guess if it public for a second and then immediately removed that's not the end of the world.

I'll share your elaboration of this idea here because it deserves a wider audience:

For people who turn on private voting:

you click the vote button one time to vote locally, then click it again to federate that vote out if you are comfortable with that vote being public

Currently, the second click removes the previously cast vote. I guess that would continue to be how it works for those who didn't turn on this feature.

You raise some good points.

One day if PieFed is in a more dominant position we could be able to push harder for fundamental changes to how things work. But protocols are hard to change - that's why email still has spam even after 40 years.

There is interest from the Voyager dev, I think things are happening there.

In principle I agree with you.

In practice I've found that occasionally admins have a legitimate need to access to voting information. To detect vote manipulation and to detect abusive people. It is very hard to provide that access, in a federated environment with lots of different software, while also being private. At the moment I don't see a way to make it truly work.

We are not making an app, but other people are making their apps connect to PieFed. Here is one of them https://interstellar.jwr.one/

On my phone I use this method - https://join.piefed.social/docs/piefed-mobile/

Weell, it IS the default theme on https://piefed.world so depending on how things turn out that could become pretty backbone-y!

The default is whatever you used most recently.

Let's add a warning message when the default is different than the thing being replied to. https://codeberg.org/rimu/pyfedi/issues/888

lemmygrad.ml is already blocked by piefed.social.

To block an instance, find a post or comment by someone from that instance and click the 3 dot menu for options.

RSS feed

Posts by Rimu, [email protected]

Comments by Rimu, [email protected]

Gah. I didn't think of that.

Maybe, by casting a vote in the other direction?

I guess if it public for a second and then immediately removed that's not the end of the world.

I'll share your elaboration of this idea here because it deserves a wider audience:

For people who turn on private voting:

you click the vote button one time to vote locally, then click it again to federate that vote out if you are comfortable with that vote being public

Currently, the second click removes the previously cast vote. I guess that would continue to be how it works for those who didn't turn on this feature.

You raise some good points.

One day if PieFed is in a more dominant position we could be able to push harder for fundamental changes to how things work. But protocols are hard to change - that's why email still has spam even after 40 years.

There is interest from the Voyager dev, I think things are happening there.

In principle I agree with you.

In practice I've found that occasionally admins have a legitimate need to access to voting information. To detect vote manipulation and to detect abusive people. It is very hard to provide that access, in a federated environment with lots of different software, while also being private. At the moment I don't see a way to make it truly work.

We are not making an app, but other people are making their apps connect to PieFed. Here is one of them https://interstellar.jwr.one/

On my phone I use this method - https://join.piefed.social/docs/piefed-mobile/

Weell, it IS the default theme on https://piefed.world so depending on how things turn out that could become pretty backbone-y!

The default is whatever you used most recently.

Let's add a warning message when the default is different than the thing being replied to. https://codeberg.org/rimu/pyfedi/issues/888

lemmygrad.ml is already blocked by piefed.social.

To block an instance, find a post or comment by someone from that instance and click the 3 dot menu for options.

Pretty much what fxomt said. The endpoint urls are the same but on some a few parameters are different and some of the returned JSON is structured slightly differently.

When Lemmy releases 1.0 and makes big changes their API, PieFed will not be trying to make compatible changes. We'll also be wanting to add new endpoints for PieFed-only features like feeds so the differences will increase over time.

Thanks. The last couple of weeks have been pretty intense. Always looking at bugs and solving problems makes it feel like everything is broken all of the time so a bit of positivity goes a long way to balancing that out :)

There have been some problems with federation lately. I believe the cause is that following piefed communities from other instances has had some bugs, which I've just fixed.

Going to Lemmy, leave the community and then join again will probably help to make future posts arrive. I've already done that for South Africa, you don't need to - I'm just saying it so others can see it.