People have requested a feature for a while where they could be notified of updates while away from Gaia.
Data from the mobile app turns out to be only just a set of undocumented webpages, not a true API. I tinkered with the app when it was released a few years back to see if I would be able to take advantage of fetching data that was 'lighter'. It helped develop the long defunct BetterGaia Dashboard feature which later morphed into the widgets currently found next by the username.
Unfortunately, data from the mobile app didn't contain enough information, and I have already moved away from using it for desktop notifications. BetterGaia now fetches all of the notifications that are queued for someone.
I like the new notification feature but there's one thing I'd like to see changed. I think it's better to make it a dropdown menu instead of a slide bar.
People have requested a feature for a while where they could be notified of updates while away from Gaia.
Data from the mobile app turns out to be only just a set of undocumented webpages, not a true API. I tinkered with the app when it was released a few years back to see if I would be able to take advantage of fetching data that was 'lighter'. It helped develop the long defunct BetterGaia Dashboard feature which later morphed into the widgets currently found next by the username.
Unfortunately, data from the mobile app didn't contain enough information, and I have already moved away from using it for desktop notifications. BetterGaia now fetches all of the notifications that are queued for someone.
While I know it's not a true API, I've known since day one. For simplistic purposes I call it an API.
You do have a function that accesses it.
chrome.alarms.onAlarm.addListener(function(alarm) {
if (alarm.name == 'gaia-notifications') {
$.get('http://gaiaonline.com/mobileapp/userdata/1.6', function(data) {
if (typeof data['user_name'] === 'string') {
var text = [];
if (data['user_mygaia_notice_count'] > 0) text.push({title: String(data['user_mygaia_notice_count']), message: 'Notices'});
if (data['user_mygaia_requests_count'] > 0) text.push({title: String(data['user_mygaia_requests_count']), message: 'Requests'});
if (data['user_notify_announcement_count'] > 0) text.push({title: String(data['user_notify_announcement_count']), message: 'Announcements'});
if (data['user_notify_pm_count'] > 0) text.push({title: String(data['user_notify_pm_count']), message: 'Private Messages'});
I sent you a few PMs about it, and if you care to know why if you don't know already, you can reply back and I can elaborate more; however, I'll re-iterate that your user base is just too large to use it. Which is why for one reason we asked for permission to use it. I'm in favor of GaiArch and BG working together, but that takes cooperation.
People have requested a feature for a while where they could be notified of updates while away from Gaia.
Data from the mobile app turns out to be only just a set of undocumented webpages, not a true API. I tinkered with the app when it was released a few years back to see if I would be able to take advantage of fetching data that was 'lighter'. It helped develop the long defunct BetterGaia Dashboard feature which later morphed into the widgets currently found next by the username.
Unfortunately, data from the mobile app didn't contain enough information, and I have already moved away from using it for desktop notifications. BetterGaia now fetches all of the notifications that are queued for someone.
While I know it's not a true API, I've known since day one. For simplistic purposes I call it an API.
You do have a function that accesses it.
chrome.alarms.onAlarm.addListener(function(alarm) {
if (alarm.name == 'gaia-notifications') {
$.get('http://gaiaonline.com/mobileapp/userdata/1.6', function(data) {
if (typeof data['user_name'] === 'string') {
var text = [];
if (data['user_mygaia_notice_count'] > 0) text.push({title: String(data['user_mygaia_notice_count']), message: 'Notices'});
if (data['user_mygaia_requests_count'] > 0) text.push({title: String(data['user_mygaia_requests_count']), message: 'Requests'});
if (data['user_notify_announcement_count'] > 0) text.push({title: String(data['user_notify_announcement_count']), message: 'Announcements'});
if (data['user_notify_pm_count'] > 0) text.push({title: String(data['user_notify_pm_count']), message: 'Private Messages'});
I sent you a few PMs about it, and if you care to know why if you don't know already, you can reply back and I can elaborate more; however, I'll re-iterate that your user base is just too large to use it. Which is why for one reason we asked for permission to use it. I'm in favor of GaiArch and BG working together, but that takes cooperation.
-
wow lol
you're like a pissy rainstorm purposely overtop a parade for disabled children
wow lol
you're like a pissy rainstorm purposely overtop a parade for disabled children
---
There actually are several reasons for that.
1. This actually is a serious issue that Allvanishing is using the mobile app code without the consent of Gaia. GaiArch asked for permission when using it and was granted. There is a reason that you need permission, but that's not something we're going to share disclose in public at this time. But if Allvanishing doesn't remove it, the issue might get serious enough to where we will be left with no choice but to get it removed. (And yes...there is a reason)
2. Considering how difficult it is to even find the links for the mobile app, it appears that Allvanishing stumbled upon them by looking at the code from GaiArch and taking the links. And GaiArch is NOT open source, meaning he pretty much stole our code.
Edit: Stole the mobile app link from our code is what I meant
wow lol
you're like a pissy rainstorm purposely overtop a parade for disabled children
---
There actually are several reasons for that.
1. This actually is a serious issue that Allvanishing is using the mobile app code without the consent of Gaia. GaiArch asked for permission when using it and was granted. There is a reason that you need permission, but that's not something we're going to share disclose in public at this time. But if Allvanishing doesn't remove it, the issue might get serious enough to where we will be left with no choice but to get it removed. (And yes...there is a reason)
2. Considering how difficult it is to even find the links for the mobile app, it appears that Allvanishing stumbled upon them by looking at the code from GaiArch and taking the links. And GaiArch is NOT open source, meaning he pretty much stole our code.
~Prince Awesome
I wouldn't say he necessarily stole it as the function is written in a way that takes longer to execute, but he has looked at it I'm sure.
Or maybe you just don't understand what the mobile app does.
-
are you getting all hot and heavy over the little thing in the 'draw all' daily chance feature
that checks if you got the DC on mobile app? cat_razz ---
As mentioned, it's not the the Daily Chance that's the problem. It's the optional one minute notices that are the problem.
Or maybe you just don't understand what the mobile app does.
-
are you getting all hot and heavy over the little thing in the 'draw all' daily chance feature
that checks if you got the DC on mobile app? cat_razz ---
As mentioned, it's not the the Daily Chance that's the problem. It's the optional one minute notices that are the problem.
-
how long has it even been since gayarch was last updated? i remember that add-on being old and impractical even before the tektek add-on became impractical.
how long has it even been since GaiArch was last updated? i remember that add-on being old and impractical even before the tektek add-on became impractical.
---
Chrome extension has been recently updated, and I'm in the process of doing yet another update.
Knight Yoshi is bringing the Firefox extension up to par with the Chrome extension.
Regardless, that's still not the issue.
Even if he did get the links from our code (which he shouldn't have), he still needs to get explicit permission to use it from one of the Gaia staff.
Edit: Also, why are you even arguing with us? You don't have enough information to be a part of this discussion. This conversation is between GaiArch developers and BetterGaia developers. And I don't think you are either.