aboutsummaryrefslogtreecommitdiff
path: root/lib/pleroma/object/fetcher.ex
AgeCommit message (Collapse)Author
2022-06-25Unify the logic of updating objectsTusooa Zhu
2022-06-01Inject history when object is refetchedTusooa Zhu
2022-02-25Copyright bump for 2022Sean King
2021-04-05Object.Fetcher: Fix getting transmogrifier reject reasonHaelwenn (lanodan) Monnier
2021-04-05Fix addressingHaelwenn (lanodan) Monnier
2021-01-13Bump Copyright to 2021Haelwenn (lanodan) Monnier
grep -rl '# Copyright © .* Pleroma' * | xargs sed -i 's;Copyright © .* Pleroma .*;Copyright © 2017-2021 Pleroma Authors <https://pleroma.social/>;'
2021-01-04Object: Rework how Object.normalize workslain
Now it defaults to not fetching, and the option is named.
2020-11-17Remove FedSocketsrinpatch
Current FedSocket implementation has a bunch of problems. It doesn't have proper error handling (in case of an error the server just doesn't respond until the connection is closed, while the client doesn't match any error messages and just assumes there has been an error after 15s) and the code is full of bad descisions (see: fetch registry which uses uuids for no reason and waits for a response by recursively querying a ets table until the value changes, or double JSON encoding). Sometime ago I almost completed rewriting fedsockets from scrach to adress these issues. However, while doing so, I realized that fedsockets are just too overkill for what they were trying to accomplish, which is reduce the overhead of federation by not signing every message. This could be done without reimplementing failure states and endpoint logic we already have with HTTP by, for example, using TLS cert auth, or switching to a more performant signature algorithm. I opened https://git.pleroma.social/pleroma/pleroma/-/issues/2262 for further discussion on alternatives to fedsockets. From discussions I had with other Pleroma developers it seems like they would approve the descision to remove them as well, therefore I am submitting this patch.
2020-11-12Fix object spoofing vulnerability in attachmentsrinpatch
Validate the content-type of the response when fetching an object, according to https://www.w3.org/TR/activitypub/#x3-2-retrieving-objects. content-type headers had to be added to many mocks in order to support this, some of this was done with a regex. While I did go over the resulting files to check I didn't modify anything unrelated, there is a possibility I missed something. Closes pleroma#1948
2020-09-18Federate data through persistent websocket connectionsSteven Fuchs
2020-09-11Fetcher: Correctly return MRF reject reasonHaelwenn (lanodan) Monnier
2020-09-03Merge branch 'bugfix/incoming-poll-emoji' into 'develop'lain
Fix emoji in Question, force generated context/context_id insertion Closes #1870 See merge request pleroma/pleroma!2915
2020-09-02correct pool and uniform headers formatAlexander Strizhakov
2020-09-01fetcher: Remove fix_object call for Question activitiesHaelwenn (lanodan) Monnier
2020-08-18fetcher: fallback to [] when to/cc is nilHaelwenn (lanodan) Monnier
Related: https://git.pleroma.social/pleroma/pleroma/-/issues/2063
2020-07-31Merge remote-tracking branch 'pleroma/develop' into features/poll-validationHaelwenn (lanodan) Monnier
2020-07-15fetcher: Reinject Question through validatorHaelwenn (lanodan) Monnier
2020-07-15fetcher: more descriptive variable namesHaelwenn (lanodan) Monnier
2020-07-13Use Logger.info for {:reject, reason}Haelwenn (lanodan) Monnier
2020-06-26object/fetcher: Pass full Transmogrifier errorHaelwenn (lanodan) Monnier
2020-03-03Merge branch 'develop' into gunAlexander Strizhakov
2020-03-02Bump copyright years of files changed after 2020-01-07Haelwenn (lanodan) Monnier
Done via the following command: git diff fcd5dd259a1700a045be902b43391b0d1bd58a5b --stat --name-only | xargs sed -i '/Pleroma Authors/c# Copyright © 2017-2020 Pleroma Authors <https:\/\/pleroma.social\/>'
2020-02-29Merge branch 'develop' into gunAlexander Strizhakov
2020-02-18adding gun adapterAlexander Strizhakov
2020-02-15[#1505] Restricted max thread distance for fetching replies on incoming ↵Ivan Tashkinov
federation (in addition to reply-to depth restriction).
2020-01-22Merge branch 'no-error-404' into 'develop'rinpatch
Log at debug level for object deletion, not error. See merge request pleroma/pleroma!2066
2019-12-13Don't log when users or objects are deleted.Phil Hagelberg
2019-12-10Change log levelEgor Kislitsyn
2019-11-23fetcher: move local object checking into a reusable functionrinpatch
2019-11-07Fetcher: fix local check returning unwrapped objectrinpatch
This resulted in error messages about failed refetches being logged.
2019-11-06Object Fetcher: set cache after reinjectingrinpatch
Probably fixes the issue hj had, where polls would have different counters between endpoints.
2019-10-24object fetcher error handlingstwf
2019-10-18object: fetcher: fix up formattingAriadne Conill
2019-10-18object: fetcher: improve error reportingAriadne Conill
2019-10-18object fetcher: fix up error handlingAriadne Conill
2019-10-18fix up some testsAriadne Conill
2019-10-18kill almost all of the OStatus moduleAriadne Conill
2019-09-19Merge branch 'develop' into test/activity_pub/transmogrifier.exMaksim Pechnikov
2019-09-18Fix credo issuesrinpatch
2019-09-18Do not refetch local objectsrinpatch
2019-09-18Preserve internal fields when reinjectingrinpatch
2019-09-18Set updated_at even if the object stayed the samerinpatch
2019-09-18Initial poll refresh supportrinpatch
Implement refreshing the object with an interval and call the function when getting the poll.
2019-09-11added testsMaksim Pechnikov
2019-08-22fix /inbox for RelayMaksim Pechnikov
2019-07-20Resolve merge conflictsrinpatch
2019-07-20Apply suggestion to lib/pleroma/object/fetcher.exrinpatch
2019-07-17fetcher: sign object fetches if configuredAriadne Conill
2019-07-14Object.Fetcher: Keep the with-do block as per kaniini propositionHaelwenn (lanodan) Monnier
2019-07-14Object.Fetcher: Fallback to OStatus only if AP actually failsHaelwenn (lanodan) Monnier
generated by cgit v1.2.3 (git 2.26.2) at 2025-04-24 20:15:32 +0000