mjit raindancerstahl said:
> Which device(s) is (are) this feature available on?
it's more a matter of the platform and the software
than the device(s). it would have started on the web,
of course, then migrated to cross-plat desktop apps,
and -- once the kindle came out -- appeared there;
then the iphone/ipad form-factors, and other tablets.
the web, web-apps, or native apps, it's all very similar.
it would have been part of a general delivery-system
bringing p.g. e-texts to any end-point asking for 'em.
error-reporting was just one of the many components,
along with change-logs, evergreen auto-updating, etc.
once the api's are in place, it's a straightforward matter
of ringing the bell with the right kinda signal, that's all.
so who knows what other capabilities could have been
built, once the set of lego-bricks had been put in place?
***
but instead, we merry-go-round the same old useless
so-called "discussions" we have re-enacted endlessly...
where greg, for instance, says "we've asked for scans,
but d.p. just won't deliver them", while d.p. counters
with "we need more support from p.g. to enable that,"
and nothing ever gets done. nothing at all. not ever.
except, of course, that _more_ e-texts get posted and
form an ever-bigger inertial drag on making changes.
when p.g. hit 10,000 e-texts, i said "ok, how about
you take a break now and reassess what you've done,
and decide how you might want to re-do some stuff,
and create a more-coherent plan for future moves?"
i repeated it when p.g. hit 15,000, and then 20,000.
25,000 as well, although by then, we all knew it was
merely a pro-forma gesture, never to happen again.
the whole bloody history sits there in the archives...
> What hardware is presumed to be in use?
anything that could access the web would be sufficient.
-bowerbird
