|
Top-level
 @pixelfed Just finished the microservice! Now to add some basic rate limiting and caching and then I'll be publishing the source and deploying it to recovery.pixelfed.org Now for the magic part, it doesn't use a database, or rather, it doesn't have it's own - it will be running along side pixelfed.social and querying its database. 13 comments
@thisismissem Oh yeah that's a good point, heck. I don't want this to be abused, and now I think about this, it will be hard to distinguish between abusive use and legitimate. Should I just drop this?  @dansup @thisismissem I think this is an important feature and you should definitely keep it! I dont see how this could be used for abuse anymore then just searching the same username on any big server like mastodon.social and seeing all the results of the search  @thisismissem @dansup it's all using public information that instances already know about and store in its database. If you were dansup and trying to evade serial trolls you might consider signing up under a different name rather than the same one being harassed.  @cooopsspace @dansup right, but I could be running in limited federation, but need to be federating with pixelfed.social, and the act of doing that would allow all the other instances that I've not federated with to know where I am. @cooopsspace @dansup who says my account has to be public or that I wish to be found? Your threat model may not be someone else's threat model. @thisismissem @dansup it's a public social media site, if you didn't want to be found you wouldn't be on here... Or at least not under your own name.   |
Gregory's Server
@dansup @pixelfed It's just incredible how much you develop in a short time, Dan! We were also very much in agreement on that at the #FediCamp ! :D