| 00:14.00 | *** join/#wowuidev Gethe (~Gethe@2603-8081-2540-4606-6950-5de2-14f5-6f9e.res6.spectrum.com) |
| 00:53.13 | *** join/#wowuidev Seerah (~umsin@2600:1700:aac0:82e0:9d89:5132:a00d:bdfd) |
| 00:53.13 | *** mode/#wowuidev [+o Seerah] by ChanServ |
| 01:48.25 | znf | remind me again: you can not change the clickable area of a nameplate while in combat, right? |
| 01:48.49 | znf | ie: if you have 10 nameplates on screen, and you get in combat with 3 of them, you can not just make the other 7 disappear completely |
| 01:49.14 | znf | and by disappearing completely, not saying just messing with the alpha, but not actually being able to click them |
| 01:51.10 | *** join/#wowuidev pompy (~Mike@2601:87:4101:92f0:7027:b35b:8502:6407) |
| 01:58.41 | *** join/#wowuidev Gethe (~Gethe@2603-8081-2540-4606-a87d-c511-8e0f-b2e4.res6.spectrum.com) |
| 03:59.54 | *** part/#wowuidev Seerah (~umsin@2600:1700:aac0:82e0:9d89:5132:a00d:bdfd) |
| 05:57.08 | AcidWeb | foxlit: generally I see this api force application to locally store and maintain latest results of /addons/us/ or store separate bundle-token per addon |
| 05:57.22 | AcidWeb | Otherwise you will skip some updates when user don't want to update them in bulk |
| 05:57.58 | AcidWeb | /addons/us/ feels like i'm using database migrations not api |
| 05:59.07 | AcidWeb | I think that some people will totally ignore /addons/us/ endpoint as it will be considered unnecessary convoluted. |
| 06:27.45 | AcidWeb | Personally only reason why I think about using /addons/us/ is a fact that I respect your wishes. |
| 07:50.22 | *** join/#wowuidev VIad (~Vlad@cm-84.213.147.218.getinternet.no) |
| 08:07.28 | Chipzz | foxlit: I agree with znf and AcidWeb saying the API appears convoluted/ overengineered. especially given the "small" number of addons hosted on your site in the first place |
| 08:08.51 | Chipzz | foxlit: you don't wish to host your addons on other websites, and that's your perogative of course. But implementing a client for your API looks like quite a bit of work, with, as AcidWeb already said, the need to lcoally store state. |
| 08:10.21 | Chipzz | foxlit: the API also appears to be implemented from the perspective of the server (how it stores data), not from the perspective of the client, and it shows in multiple ways |
| 08:12.45 | Chipzz | foxlit: now the people in this channel are probably capable of implementing a client. But do you expect the regular Joe user to be able to do so? They would have to use a client implemented by someone smarter, creating the need for people to publish their client somewhere (lets say github) and teh regular Joe user to go looking for a client |
| 08:13.49 | Chipzz | I'm not sure how many people are going to bother for, and I don't mean this in a deragotory way, a grand total of what, 8 addons? |
| 08:14.08 | AcidWeb | In current form scraping the page is easier than using the api. And that speaks a lot for itself. |
| 08:14.25 | Chipzz | and with bother I mean both a) write a client and b) go looking for a client |
| 08:15.01 | Chipzz | this may be worth it if your website would host the same amount of addons as lets say curse |
| 08:16.12 | Chipzz | also: the docs state you don't want people to poll for updates. There's a nice technology available for pushing rather than polling, and it's called socket.io |
| 08:16.42 | Chipzz | but given your website is written in lua I'm going to guess you won't be supporting that :) |
| 08:17.45 | Chipzz | AcidWeb: yeah, the API looks like it's simply exposing internal server state by converting it to json, or sth very close |
| 08:18.14 | *** join/#wowuidev NiTro- (uid57822@gateway/web/irccloud.com/x-gvpublymojpfaqkp) |
| 08:19.24 | Chipzz | other than the points I raised above, there's also this: determined by the game flavour (e.g. modern/classic), realm category (live/ptr) |
| 08:19.30 | Chipzz | this seems redundant TBH |
| 08:19.49 | Chipzz | why not have one field live/ classic/ ptr/ classic-ptr ? |
| 08:22.48 | Chipzz | foxlit: TL;DR: the whole thing looks well-intended but (and I don't mean this in an offensive way) poorly thought out, and simply not worth it |
| 08:23.16 | Chipzz | foxlit: my suggestion is to rethink the API from a client POV, not as an artifact of the server state |
| 08:24.44 | Chipzz | try to write a client from scratch and implement the API in terms of what you need, as you go along |
| 08:26.52 | Chipzz | because to me it feels like what you did is: "Hey, I have all this data, how can I expose this in a way that doesn't require a lot of effort?", which is well-intended of course :) |
| 08:28.50 | Chipzz | also, I have the feeling your website may not run on a server with a lot of resources, causing you to think of the API in terms of: "How can I make sure this doesn't generate a lot of traffic/ load?", which may be a premature optimization |
| 08:33.35 | Chipzz | (I hope this wall of text didn't make me look like an arse, not trying to diss your efforts, just trying to give feedback) |
| 09:55.31 | *** join/#wowuidev Humbedooh (~humbedooh@apache/staff/humbedooh) |
| 11:29.49 | *** join/#wowuidev brykrys (~brykrys@WoWUIDev/Norganna/Dev/Brykrys) |
| 11:59.08 | *** join/#wowuidev Iriel (~Iriel@173-8-135-221-SFBA.hfc.comcastbusiness.net) |
| 11:59.08 | *** mode/#wowuidev [+o Iriel] by ChanServ |
| 11:59.08 | *** join/#wowuidev Kalroth (~Kalroth@knas.io) |
| 11:59.08 | *** join/#wowuidev Iriel (~Iriel@173-8-135-221-SFBA.hfc.comcastbusiness.net) |
| 11:59.08 | *** mode/#wowuidev [+o Iriel] by kornbluth.freenode.net |
| 12:45.15 | *** join/#wowuidev Iriel (~Iriel@173-8-135-221-SFBA.hfc.comcastbusiness.net) |
| 12:45.15 | *** mode/#wowuidev [+o Iriel] by ChanServ |
| 13:04.30 | *** join/#wowuidev Breen (~Breen@80.175.117.105) |
| 13:38.13 | *** join/#wowuidev Vardex (~vardex@62-210-79-177.rev.poneytelecom.eu) |
| 15:12.50 | *** join/#wowuidev Treeston (~stolenleg@unaffiliated/stolenlegacy) |
| 15:31.17 | Stanzilla | ;D |
| 15:35.09 | *** join/#wowuidev Meorawr (~Meorawr@cpc157781-rdng31-2-0-cust996.15-3.cable.virginm.net) |
| 15:47.45 | *** join/#wowuidev brykrys (~brykrys@WoWUIDev/Norganna/Dev/Brykrys) |
| 16:25.20 | foxlit | "foxlit: generally I see this api force application to locally store and maintain latest results of /addons/us/" << I expect applications to locally store information about an available update for managed addons. You don't have to keep the /us/ bundle, or store it in the same format -- just keep the parts relevant to you, in whatever way you like. |
| 16:27.00 | *** join/#wowuidev pompy (~Mike@2601:87:4101:92f0:7027:b35b:8502:6407) |
| 16:27.57 | foxlit | I expect you already have to store per-addon state, for example to support multiple source sites, to allow users to have an alpha/beta/release preference, or to ignore updates. |
| 16:34.18 | *** join/#wowuidev Funkeh` (Funkeh`@WoWUIDev/WoWAce/Ace3/BigWigs/funkeh) |
| 16:48.33 | *** join/#wowuidev Meorawr2918 (~Meorawr@cpc157781-rdng31-2-0-cust996.15-3.cable.virginm.net) |
| 16:48.33 | *** join/#wowuidev Treeston_ (~stolenleg@unaffiliated/stolenlegacy) |
| 17:02.03 | foxlit | Chipzz: thanks. It might be more helpful if /you/ tried to implement a client for this, and then described the difficulties you experienced. |
| 17:02.48 | Chipzz | foxlit: the thing is, I don't think I use any of your addons |
| 17:03.10 | Chipzz | a bit dificult then ;) |
| 17:04.58 | foxlit | You could start with implementing install-from-URL to fix that. :P |
| 17:08.39 | foxlit | (I actually already have an update client running against this API; it's fairly straightforward.) |
| 19:12.35 | *** join/#wowuidev LexSfX (~lexlexlex@216-180-68-238.dyn.novuscom.net) |
| 19:20.10 | *** join/#wowuidev Seerah (~umsin@2600:1700:aac0:82e0:f42e:998c:9121:77ac) |
| 19:20.10 | *** mode/#wowuidev [+o Seerah] by ChanServ |
| 21:52.47 | *** join/#wowuidev Velithris (sid290671@gateway/web/irccloud.com/x-hnwtjfcpvcylxqrq) |
| 22:49.04 | Gnarfoz | I'm just thankful that open source, community (or rather: volunteer) maintained updaters exist (hello AcidWeb), and that foxlit spent time to make it possible for those to add support for his site, and that I probably can, in the near future, update foxlit's addons that I use without additional effort on my part. they're few in number, but fantastic in benefit. =) |
| 22:52.38 | Gnarfoz | the near future is actually now :O https://hddf.eu/p/KLBktkjkaA.png |
| 22:53.09 | Gnarfoz | just noticed that despite the column being titled the same, install does not show the author, while status does. huh |
