Skip Navigation

Posts
3
Comments
41
Joined
3 yr. ago

  • Do you mean you're trying to access Threads' ActivityPub endpoint(s)?

    I'm pretty certain that you have to use signed requests, and bear in mind that not all users have federation enabled.

    I just confirmed that by using the fedify CLI to test. Running fedify lookup andypiper@threads.net fails, but with fedify lookup -a andypiper@threads.net (which spins up a local server and performs authenticated requests) I get back JSON from the WebFinger endpoint.

    You'll probably get some folks able to share their experiences integrating / testing with Threads federation in some of the Fediverse Developers related Matrix rooms.

  • Cool, but Loops is not a Fediverse app until it federates, and it can't be self-hosted until the code is available.

  • I have stickers (and was sharing them at FOSDEM) but I haven't put them online anywhere yet, I need to get on that! Thanks for liking it!

  • well, except that is not actually federated yet.

  • There was a good talk about this at FOSDEM at the weekend!

  • If the user didn't make their posts as discoverable, then no, they will not be returned in a search. The search is opt-in. It is not ideal, but it is a way to respect user privacy. I was making the point that search exists now, even if it had previously been rejected as a feature to implement, so it is not impossible for folks to change their opinions on including features.

  • I do not think that is a factual representation of the team dynamics, but of course, you are free to choose that interpretation.

  • quote posts are being implemented.

  • I don't know, I was not involved if that was said at some time, but now, we have search, so I don't know what to tell you.

  • won’t implement it.

    "not sure downvotes make sense" -> it might not be a good fit for what the app is -> so maybe it would not make sense to implement.

    I should be able to search for a keyword or URL on all instances

    We're working on this. It's part of Fediscovery. Optional opt-in discovery across instances, if a user wants their content to be discoverable across instances.

  • Search exists. I'm not sure downvotes make sense in the context of a microblogging app, but YMMV. There's a lot of things to work on, for sure.

  • The 501(c(3) is a fundraising entity, and will continue to exist. There will be a new independent European non-profit that will "own" (for the want of a better word) the other entities. Legal structures and things are not my forte (IANAL), that's my understanding of what is happening in so far as I'm involved in the discussions and what I'm able to tell you.

  • now updated.

  • Checking about getting it updated.

  • there's a big difference between running a service on volunteers, and having full-time folks to keep things running / answer the regulation discussions / keep maintaining / keep adding the features that folks are looking for. This is not primarily an infrastructure spend. There's also an amount of legal work involved, unfortunately. So, those are some of the elements we're looking at.

  • These are part of the assets that will be transferred from the GmbH to the non-profit.

  • I wrote about this on my blog. I like the notion and points made here, but I also think we're not helping by re-inventing things that already exist, so I'm torn on it. I have been happy with the existing one.