-
Notifications
You must be signed in to change notification settings - Fork 173
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
SageTV forums down for maintenance for 48 hours #422
Comments
Yes I am aware, thanks. 🙂 |
Ah, ok. Good news I’m not the only one spending Thanksgiving working on my Sage box. Hopefully back up soon... |
Thanksgiving was six weeks ago in these parts ;-) |
Hehe - southern provinces here. But I’m getting a little nervous seeing the forum down. Is there another way Sage users communicate? The FB page hasn’t had an entry in 10 years? Is the Github site ‘the place’?
Sent from me
… On Nov 28, 2019, at 1:40 PM, wayner9 ***@***.***> wrote:
Thanksgiving was six weeks ago in these parts ;-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'll get them back up, just be patient. 🙂 |
Thanks. Good to see you’re still around. There was a point where I wondered if it would be a good idea to download the site, just in case of natural disaster, etc., or if indeed there’s an alternate place Sage-folk hang out. Cheers :)
Sent from me
… On Nov 28, 2019, at 10:41 PM, Jeffrey Kardatzke ***@***.***> wrote:
I'll get them back up, just be patient. 🙂
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Narflex, the forums are still cranking out popups. emveepee has some info here: https://forums.sagetv.com/forums/showthread.php?p=623175&postcount=23 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry to post this here but the forums have been down for about 48 hours. Just wanted to be sure that Narflex, etc were aware of that.
The text was updated successfully, but these errors were encountered: