Emma2hmm ok so im trying to make a new page for the RSVP and it isn't working and ive notice that none of the text is green and blue, as it is on other pages that work
cmalsnarfed: @alct is going to rewrite social_stats using noapi I think we just need to focus on wrapping noapi properly (which I'm not really doing atm)
aaronpkI just added a simple view counter to my posts to track the number of times they've been viewed. I realized i didn't have that info anywhere other than google analytics, and it would at least be nice to know which of my posts are most viewed even if it's not super detailed stats.
snarfedworrying about avoiding ddoses kind of reminds me of nutrition and trying to eat healthy. i suspect in practice the cost of the effort and stress far outweighs any actual benefit or harm prevented
aaronpkthere are some pretty basic nutrition things you can do that actually do make a difference tho, likely analogous to some basic site architecture things you can do to prevent trivial DOSs
aaronpki use background queues for stuff where the tradeoff is in user experience. like if i make a post on my site and then i want to send webmentions, posse to multiple locations, etc, if the form I submit had to wait until all that was done before I saw the post it would be terrible. so I put all that on a background queue.
aaronpkwell that was fun. Just fixed a hilarious bug. since I added support for multi-photo over the weekend, I discovered that a bunch of my bookmark posts had the screenshot of the site like 20-30 times in the post. this meant the pages were showing like 30 photos in the post and bringing my browser to a crawl.
aaronpkturns out my cron job i set up at indieweb summit to make the screenshots forgot to check if it had already posted the screenshot, so they just kept stacking up
cmalthen how they get the data from the silo is their problem : can be a script switching VPNs to make it more random, could be a DHT-based pool of knowledge, for all I know :)
cmalso I think although it's hacky and can break down sometimes, it's ultimately the most portable and anonymizing way to fetch data off silo that I know of
cmalI mean better would be to have millions of users letting a silo app or a browser addon share in p2p the *public* content they receive, but we're not quite there yet :)
snarfedas an example, bridgy did have to switch to scraping instagram since they turned off much of its API for all apps, not just bridgy specifically...but we did that only when we had to
cmalwell what you say makes sense in the case of a central hub a lot of people rely on (like bridgy), but if we're talking about a really decentralized setup the pros and cons of both sort of balance each other (having to register your app regularly to Facebook Known-style is really troublesome)
aaronpkcmal: btw have you been able to sign in to the wiki? you should add yourself to https://indieweb.org/irc-people so your picture and website show up in the logs!
cmalbecause I think it's just brilliant, a PUBSUB architecture for the social web would make interconnection with XMPP-based social networks way easier
bearmy reason for stating that is, in my view, incremental implementation progress that leads to standards is soooo much saner than what has happened in the past
aaronpkindeed, "standards" which are made up before any implementation (especially before any interoperable implementations) are likely to turn out to be irrelevant in the long run