LoqiCORS is an acronym for "cross-origin resource sharing," a mechanism for allowing browsers to make JavaScript requests to fetch resources from other domains http://indiewebcamp.com/CORS
tantek!tell npdoty 1) for automated spam, I'm pretty convinced /vouch squashes it. 2) for abuse and targeted spam (which is just a form of abuse), we have /block - which frankly is a solved problem - Flickr got it right, everyone else needs to just copy their model. 3) for ways to publish blocklists, see http://microformats.org/wiki/blocklist. 4) what will you implement on your own site? write it down on /User:Npdoty.name perhaps in a new sec
Loqifiatjaf: tantek left you a message 3 hours, 58 minutes ago: CORS is a good thing. Based on CORS, we've written up some of this: https://indiewebcamp.com/subdomains
fiatjaftantek: I was thinking I could do webmentions and discovery using mf2 tags from the client side (using javascript in one page to fetch data from other pages), but I totally forgot about the Same Origin Policy and now I think it is very bad for the indieweb. javascript running in the browser could be a powerful tool, not requiring people to have and maintain their own servers, but still let them do a lot of interesting things from client side.
fiatjafI don't know exactly how this fits, because the indieweb is about having a domain name, but a domain name does not imply a full-featured webserver.
mkoAnyone have good IndieWeb examples of data displayed not in a post/entry format? I'm looking for a way to post my genome publicly, but it sits at approximately 1 million SNPs, which seems kind of absurd to try to publish as h-as-gene posts. :-)
mkoSimilarly, I've got around 300k energy usage data intervals that I want to publish, and I feel like even those might need to be displayed as something other than an entry (though they're easier to publish as an entry as they've got explicit time boundaries, unlike the gene data).
verdi, pfefferle_, chrisroos, tfontaine1, jet___, snarfed, EOGreer and danlyke joined the channel
Loqiaaronpk: kbs left you a message on 10/25 at 11:32am: oh, woops and apologies - just realized hexagon/honeycomb was from a different aaron *blush* so, ignore all of it (some PGP fingerprint visualization discussion from long back.)
chrisroosI've been working on a video service for the last few weeks. It's similar(ish) to Wistia, Vzaar and others with one main difference being that the videos are served from a domain you own.
chrisroosWe started out essentially building a self-hosted product on top of AWS but have since moved to hosting the videos in our AWS account and serving them on users' domains.
chrisroosWe're not really sure where we're going with it yet - it started out as a bit of a toy project - and it's possible we might release it all as open-source.
chrisroosOh, and just in case that looks like a completely spammy sales pitch. That's really not the intention! The service we're imagining would be zero lock-in, handle some of the challenges described in http://indiewebcamp.com/video#Web_support and result in videos served on your own domain.
chrisroos@Mark87 It allows you to upload videos, transcodes them to suitable web formats and then makes them available at a URL like videos.<yourdomain>.com
chrisroos@Mark87 They're hosted as well but we'd be looking to charge for the service - we can't afford to run it for free. The alternative is the possibility of the self-hosted version (in which case you'd pay the charges directly), although we've not discussed that in detail yet.
chrisroos@aaronpk @tantek____ No, I'm not. But, yes, I plan to. I have a (very) small number of videos on YouTube, Vimeo and directly on my site. I plan for this to replace those.
chrisroos@ShaneHudson The fact that you'll own the domain, and therefore URLs, means that it should be easy for you to move your videos anywhere else at anytime
ShaneHudsonI think the domain part of the namespace is quite important. If it is in one place and not distributed then that one place must be trustworthy. Luckily indiewebcamp.com is :)
barnabywaltersShaneHudson: that’s the case if the domain part is actually used (i.e. resolving namespaced terms actually produces content). Otherwise it’s just a string of characters :)
ShaneHudsonI find post types useful for UI. For example a photo post type doesn't always need a text box whereas my longform content has a UI that consists of [+photo, +text, +quote] etc
ShaneHudsonTrue, Facebook's UI is a very cut down version of my longform in a way. You add the content types to the post as opposed to starting with the type
Mark87What does it matter what "type" we assign to a collection of properties, if the doesn't tell us anything more than the presence of the properties themselves
Mark87If there's a p-name, we know the objects name, if there's e-content, we know its content, if there's u-url, we know its url, if there are other properties we don't know about, that's fine, we won't render them, but we can still show what we know about the object, namely its name, content, and url
julian``, barnabywalters and npdoty joined the channel
kylewmMark87: it's not article vs. note, there are also events, invites, rsvps, photos, other media (videos, audio), checkins, bookmarks, etc. that might all be displayed differently
aaronpkhe said he was relieved to be able to use ownyourgram because he missed sharing photos with people on instagram after switching to posting from his site
aaronpkright. I don't want to have to write the auth code for every project I make, so in that case I want to use indieauth.com this way https://indieauth.com/developers
kylewmjuansantiago: a good first step would be to sign in to indieauth using your own site. linking to a Twitter or Github page are common options. if you don't have those, or prefer not to publish links to them, it's possible to sign in with SMS, an email address using Mozilla Persona, or with a PGP key (https://indieauth.com/gpg)