-
br-m
<shortwavesurfer2009> My take on a p2pool ui. Fork away
-
br-m
-
br-m
<shortwavesurfer2009> I made it primarily for mobile use.
-
DataHoarder
how often do you run that?
-
DataHoarder
my rec as usual is to run one api call to backfill missing data
-
DataHoarder
then use events api listed on
nano.p2pool.observer/api
-
DataHoarder
which is a websocket stream of side blocks / found blocks etc.
-
DataHoarder
then just gather your shares/payouts that way in a streaming way
-
br-m
<shortwavesurfer2009> I cron run it every 5 mins > <DataHoarder> how often do you run that?
-
DataHoarder
you could cache the daily pulls tbh
-
DataHoarder
specially if this is not just your script and others want to use it as well
-
br-m
<shortwavesurfer2009> I have what I want out of it and don't really intend to continue development, so anybody is welcome to fork it and make modifications.
-
DataHoarder
if possible add some identifying user agent (for the repo for example)
-
DataHoarder
otherwise if these get out of hand the best I can do is block the entire IP
-
br-m
<shortwavesurfer2009> I just uploaded it so that it doesn't get lost if my computer crashes or something.
-
DataHoarder
cool
-
DataHoarder
sometimes end scripts break
-
DataHoarder
give it -H "User-Agent: p2pool-ui (+
github.com/shortwavesurfer2009/p2pool-ui)" for example to each curl call
-
DataHoarder
that way only the broken automation (say a user runs this every 50ms) can be targeted in temporary blocks
-
DataHoarder
and not everything
-
br-m
<shortwavesurfer2009> DataHoarder: As I said, I really don't intend to continue development on it, but if you would like to submit a pull request for doing that, I will add it in.
-
DataHoarder
I don't intend to submit a PR, but if users end up blocked, they might ask on the tool
-
DataHoarder
(I say this as the one that would need to eat the costs of operation/setting the blocks on p2pool.observer)
-
br-m
<shortwavesurfer2009> DataHoarder: At some point I'll get around to adding a readme and point that out.
-
br-m
<shortwavesurfer2009> I have it set to run every five minutes on Crawn, but somebody else might run it faster than that.
-
DataHoarder
yeah. 5 minutes is fine. I think all you have to do is add -H "User-Agent: p2pool-ui (+
github.com/shortwavesurfer2009/p2pool-ui)" on each curl call there
-
DataHoarder
I like jq outputting html :')
-
br-m
<shortwavesurfer2009> DataHoarder: Just for my local one, or the one that's submitted to Git?
-
DataHoarder
git one if that's what you run/others might find
-
DataHoarder
there aren't many so people end up stumbling upon them
-
br-m
<shortwavesurfer2009> DataHoarder: K. Yeah, I run that code as submitted, so I will add that to git.
-
DataHoarder
amazing, thanks
-
DataHoarder
feel free to share in #p2pool-log / #p2pool-mini other people might find it useful :)
-
br-m
<shortwavesurfer2009> DataHoarder: Okay, have a look now. It should be updated.
-
DataHoarder
👍
-
br-m
<shortwavesurfer2009> The main reason for it is because observer does not work well on mobile. And so I just coded up something bare-bones basic to work better.
-
br-m
<shortwavesurfer2009> I can clearly see, for example, that it's showing shares from more than 24 hours ago. But I don't really feel like dealing with it. And so it's fine the way it is. LOL.
-
DataHoarder
hahaha
-
DataHoarder
I have a bootstrap UI (like
blocks.p2pool.observer ) with semi-responsive UI in the works
-
DataHoarder
from last year, but web hasn't updated that much, still relevant. afaik the proofs page were what was left
git.gammaspectra.live/P2Pool/observer/src/branch/bootstrap-ui
-
DataHoarder
it's where I have my css-only dropdown menus from for blocks explorer as well (for small/large nav bar)
-
DataHoarder
after cleaning up that should be the p2pool explorer at some point :)