DailyRucks Testing, Follow Behavior
The DailyRucks account has a new home with a new ActivityPub ID, tidying up the clutter and preparing for a go-live.
For this test, I will be un-following the existing account on all the platforms I tested, then searching for the new one in a few different ways, then following it.
If the correct account is shown for all searches, I will then follow it, using the first Search term.
- Search 1: https://fietkau.software/daily_rucks/ap
- Search 2: https://dailyrucks.fietkau.software/
- Search 3: @DailyRucks@fietkau.software
If a test is blank, that means I did not attempt it due to a previous issue.
Account Type | Unfollow | Search 1 | Search 2 | Search 3 | Follow | Comment |
---|---|---|---|---|---|---|
Mastodon | ||||||
GoToSocial | Used Enafore front end. Follow worked, showed "pending" until refresh | |||||
Friendica | ||||||
IceShrimp | Search 2 throws an error, see below chart. | |||||
Catodon | Search 2 took me to @DailyRucks@dailyrucks.fietkau.software | |||||
Misskey | ||||||
Sharkey | Search 2 took me to @DailyRucks@dailyrucks.fietkau.software, while Search 3 didn't work, I can enter the profile url and it works. | |||||
Micro.blog | N/A | Verified from Micro.blog that they don't officially support searching by URL. If you remove "https://" results show up, but /daily_rucks/ap throws it for a loop. | ||||
kBin | This didn't find the account in the last tests either. | |||||
Lemmy | Lemmy profile doesn't show a way to follow ANY fediverse profile. |
IceShrimp - Search 2 Error Message
Using the Search function, with "Users" selected as the filter, after entering https://dailyrucks.fietkau.software/
, I get the following error:
POST 500 Exception Message from IceShrimp
XHRPOST https://fedia.social/api/ap/show [HTTP/2 500 325ms]error Object { message: "Internal error occurred. Please contact us if the error persists.", code: "INTERNAL_ERROR", id: "5d37dbcb-891e-41ca-a3d6-e690c97775ac", … } message "Internal error occurred. Please contact us if the error persists." code "INTERNAL_ERROR" id "5d37dbcb-891e-41ca-a3d6-e690c97775ac" kind "server" info Object { e: {…} } e Object { message: "303 SEE OTHER", code: "StatusError", stack: "StatusError: 303 SEE OTHER\n at getResponse (file:///home/iceshrimp/fedia.social/packages/backend/built/misc/fetch.js:56:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async signedGet (file:///home/iceshrimp/fedia.social/packages/backend/built/remote/activitypub/request.js:45:17)\n at async Resolver.resolve (file:///home/iceshrimp/fedia.social/packages/backend/built/remote/activitypub/resolver.js:91:36)\n at async fetchAny (file:///home/iceshrimp/fedia.social/packages/backend/built/server/api/endpoints/ap/show.js:123:20)\n at async file:///home/iceshrimp/fedia.social/packages/backend/built/server/api/endpoints/ap/show.js:88:20\n at async default (file:///home/iceshrimp/fedia.social/packages/backend/built/server/api/call.js:121:12)" }