Using the https://bibliogram.art instance
◸―――――――――――――――――――――――――――――――――――――◹ ···< | 500. That's an error. | >··· ◺―――――――――――――――――――――――――――――――――――――◿ ╱ Are you visiting this website? Not sure what's going on? ╲ ╲ You might want to come back later. ╱ TypeError: Cannot read property 'json' of undefined at /home/cloud/bupdate/bibliogram/src/lib/collectors.js:284:18 at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Timeline.fetchUpToPage (/home/cloud/bupdate/bibliogram/src/lib/structures/Timeline.js:58:19) at async Object.code (/home/cloud/bupdate/bibliogram/src/site/api/routes.js:117:24)
Have you considered using Tor?
Edit: sorry, I just found the blog post which explains the limitations of the Tor approach.
Another option: a volunteer network of users running a Bibliogram proxy daemon on residential IPs, which instances can choose from at random to facilitate requests.
Oh hi. Tor has been considered plenty already. A volunteer network has also been considered and discarded because there's no way to know if the discovered data is correct or if it's malicious.
Trust systems are not impossible - just social in nature. If you establish a relationship with the volunteers, you can have checks in place which can remove a volunteer who abuses their position. You don't need to set up some kind of automatic system where anyone can get on board without consulting with the instance admins. And, after all, at the end of the day it's just Instagram pics.
How would you send requests to these volunteers if they're on a residential IP - i.e., behind a NAT - in a hypothetical system? I know a couple ways I could do it, websockets, or STUN, and while possible neither of those are particularly appealing.
Actually, can we split this off to a mailing list discussion? I'll close the original issue as duplicate.