Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using FedBOX as storage backend through C2S ActivityPub #25

Merged
merged 93 commits into from
Nov 17, 2019
Merged

Conversation

mariusor
Copy link
Owner

@mariusor mariusor commented Sep 6, 2019

  • Remove local API functionality
  • Modify authentication to use OAuth2 on FedBOX
  • Modify frontend repository logic to use FedBOX to load information:
    • Loading items
      • self
      • federated
      • followed
      • domain based filtering
      • reply loading and threading
    • Loading votes
      • per account
      • per item
    • Loading accounts
    • Creating new items
    • Creating new accounts
    • Voting
  • Modify docker setup to include a FedBOX container Moved to Add fedbox docker to the setup #26
  • Modify bootstrap procedure to include adding an OAuth2 client for littr.go on FedBOX Moved to Add fedbox docker to the setup #26

@Cambridgeport90
Copy link

What is happening with this one. Looks pretty good so far.

@mariusor
Copy link
Owner Author

Hi @Cambridgeport90, thank you for your interest in littr.go. The status is that currently development is on a small hiatus while I deal with some other projects and some IRL stuff.

As you can see from the list at the top, the last item to tackle is the message threading, and I'm currently evaluating options for how to best express it using the ActivityPub standard properties:

In current master of littr.go (which uses an internal activitypub server) threading is being done by storing the parent of the current object (rather its IRI) in "InReplyTo" property and the top level object (also IRI reference) in the "Context" property.

In this branch I thought it's a better idea to store both of these IRIs in the "InReplyTo" as an array, and use that, but I encountered some unforseen problems.

I also tried storing the whole parent chain references in the "InReplyTo" but it seems like the worst solution, as it requires a lot of redundant information on each object.

I hope this message gives you some context. :) Let me know if I can help more.

@Cambridgeport90
Copy link

Cambridgeport90 commented Nov 11, 2019 via email

Waits for finalizing it, by walking the wrapped error tree where it applies
Currently it's a bit of a hack
Fixes a bug where users were using each other's services
@mariusor mariusor merged commit 52d5459 into master Nov 17, 2019
@mariusor mariusor deleted the fedbox-c2s branch December 11, 2019 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants