Dimillian / Dimillian/IceCubesApp

Most Remote Local Timelines I try fail - what am I missing?

Open
#1,155 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
7.1k
Forks
720
PR merge metrics
No merged PRs in 30d

Description

Choosing one of the promoted instances works...

If I type in an instance, it says "is a valid instance". But then "An error occurred loading posts..."

I assumed it was because I was trying non-Mastodon servers, but I just tried some on Mastodon 4.10+glitch and they also failed. I can log into my own instances on glitch servers, but can't add them as "Local Timelines"...

Hope I'm using these names correctly - seems like "local" should mean what you're signed into as a member, and "remote" should be what you're just peeking at... But I'm trying to copy what the app shows.

Maybe instances can block the Remote feature? Is there a way to know what is (not) happening here?

Is there documentation somewhere?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure in the Local Timelines flow with both promoted and manually entered Mastodon instances, including the glitch instances described. Trace the loading path and its error reporting; done means the cause of the failed loads is identified and users can understand whether an instance is unsupported, blocking the request, or otherwise unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.