Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

siasky.net is dead #29

Open
singpolyma opened this issue Nov 10, 2022 · 8 comments
Open

siasky.net is dead #29

singpolyma opened this issue Nov 10, 2022 · 8 comments

Comments

@singpolyma
Copy link

So the app default should probably change.

@redsolver
Copy link
Owner

I recommend switching to skynet.moe

@OkyDooky
Copy link

OkyDooky commented Dec 9, 2022

Just tried that and got thrown a bunch of errors all saying:
Invalid argument(s): No host specified in URI: skynet.moe/blahblahblah
And I realized the fix was it needed the https:// before it. Now it seems to be syncing and I might finally get to try this as an app mamager and updater. Thanks for that!
I hope this app takes off (heh), because the idea is great and it seems really viable.

@Jan69
Copy link

Jan69 commented Dec 12, 2022

relatedly, there is no way to sign in to portals that require registration
skynet.moe does work fine though, that is nice

@OkyDooky
Copy link

Apparently, it's not receiving new updates. There are several apps that have been updated in the last few days on F-Droid that are not showing up in SkyDroid. Jami was updated yesterday, for instance, but in SkyDroid it is claimed it was last updated 2 months ago (it has had more than several updates in that timeframe). Should I open a separate issue for that or is here fine?

@redsolver
Copy link
Owner

I just updated all mirrored (F-Droid) apps

@OkyDooky
Copy link

Thanks, that seems to have jostled things. Everything looks up to date!
I got this error, though:
Screenshot_2022-12-27_23-49-14
And this entry keeps suggestion I "update" to a much earlier version for some reason. I think it did this the last time I looked at it:
Screenshot_2022-12-27_23-50-14
Should I make separate issues for either of these?

@redsolver
Copy link
Owner

Not sure about the SensorBox issue, but the HTTP 490s and hash mismatches are temporary downtime

@OkyDooky
Copy link

Ah, okay. I haven't had them pop up in the last couple times I opened the app, so that makes sense.
Has there been any progress on this project? I'd really like to see it succeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants