Panoramax-US-NW (API) available in US northwest

Hello all!
I am pleased to announce that my instance Panoramax-US-NW (API) is now available for use by those in the northwest of the US!

  • I am using OpenStreetMap for authentication
  • I am using the panoramax.fr instance for blurring (for now)
  • Uploads are currently limited to the following states: WA, OR, ID, MT, WY
  • I’ve set aside roughly 8TB for now (storage is pricey these days!)
  • I am in the process of submitting for federation (Edit: Done!)
  • I’d like to get added to Baba’s upload targets, but may need assistance making the pull request

I am holding off on re-uploading the bulk of my imagery (several TB) to see when the ability to migrate images between instances while preserving their IDs is implemented. If you have a lot of imagery on the FR instance, I recommend doing the same so we don’t break any existing links unecessarily.

Thank you @Matija_Nalis for your walkthrough- it was what got me over my hesitation. I may be doing a write up of my experience at some point.

Please feel free to take a look, upload imagery, and let me know if you see anything that needs updating.

Edit: I have an open issue on the gitlab suggesting the ability to cap uploads when a certain storage threshhold is reached. I think this is a vital feature for smaller operators (like me). Please feel free to show you support with a thumbs up if you agree!

14 Likes

Note that in the meantime since my diary post, Baba issue #170 has been implemented, so next release of Baba should be able to fetch list of all instances automatically, without any extra work from instance admin side. Yay!

Note that there is small typo in your API summary: says the the URL is https:/.pano.locus.sbs (while it should be https://pano.locus.sbs).

Great to see you in the federation!

3 Likes

Oh! The Baba update is great to hear. That’s a perfect solution!
Edit: And that feature is already live! Wonderful.

Regarding the typo- I am not sure where to fix that. My API_SUMMARY does not specify a URL, and I don’t see the malformed URL string anywhere in my configuration files. So I am not sure where it is coming from. If you can point me to what I need to update, please do!

I asked on my federation request, and it is being discussed.

2 Likes

Just an update- I was able to resolve the URL mismatches in both Baba and the aggregator site. The update to Baba is not yet available on the Google Play store, but is on f-droid (via the izzyondroid repo).

I am seeing a steady trickle of submissions, so thank you all out there!

6 Likes