#Loqitantek: ben_thatmustbeme left you a message on 11/12 at 4:00am: I don't think #indieweb is becoming intentionally overloaded, I have been seeing indie publishing on the web slowly move toward that for a while. http://indiewebcamp.com/irc/2015-11-12/line/1447329629096
#tantekjust checking in and seeing the news about Paris. thoughts with those in the community in Paris.
#tantek!tell ben_thatmustbeme perhaps we can start by documenting the overloading of the indieweb hashtag and providing a positive / supportive / inclusive statement about it?
#tantekmarked safe is a notification feature that tells you when those you follow have marked themselves as safe in an area affected by a disaster or other physical emergency within a geographical area.
#tantekaaronpk: ^^^ Loqi bug? "message 3 weeks ago: really hope you can make it to the main annual IndieWebCamp in Portland!"
#Loqiben_thatmustbeme: tantek left you a message 30 minutes ago: perhaps we can start by documenting the overloading of the indieweb hashtag and providing a positive / supportive / inclusive statement about it? http://indiewebcamp.com/irc/2015-11-13/line/1447463042967
#tantekaaronpk, dietrich pretty sure I left that message *months* ago
#tantekben_thatmustbeme: figuring if we can passively document such apparent conflicts in a more positive / inclusive way, it may encourage more of that kind of thinking in the future
#tantekand then we can decouple the decision as to whether to weigh-in on any particular thread
#tanteksafety check is an aggregation feature that shows a list of the people you follow in a disaster affected geographical area that have marked themselves as safe. See also [[marked safe]].
#tantekI'm still trying to capture / document / describe enough of marked safe / safety check to figure out if there is something here of an implicit or explicit post type
#tanteksafety status is a particular type of post (with a permalink) that indicates a person's safety during a disaster event and can be posted by a person or by one of their friends. Such posts are shown as a [[marked safe]] notification to followers, and aggregated on a [[safety check]] page.
#Loqisilo quits are public statements by individuals announcing they have publicly quit posting on or using (at all) various silos, either with intended permanence, or temporarily (sometimes referred to as taking a "social media break") https://indiewebcamp.com/silo-quits
#tantek.comedited /projects (+230) "/* Help Update This Page With */ note why we project examples should have at least decent visual design / usability" (view diff)
petermolnar, raucao, scor, johnstorey and nitot joined the channel
#tanteknoticing that FB events seem to have lost the separate "regrets" or "Post why you can't go" page / thread
#tantekwhich now has the (unintended?) effect that many of the events I see have tons of recent comments which are all "sorry I can't go" which then puts a downer on the event as a whole
#tantekespecially since *everybody* gets notified for every new comment - checks it - just to see that it's another person declining
#tantekand since people are social animals, seeing lots of other people post that they can't go makes you not want to go
#tantekknowing all this, instead of posting a "Sorry I can't make it" comment on the event (which appears to show that you publicly care, but actually hurts the overall social dynamic of the event), the better thing to do is to privately message host(s) that you can't go.
#tantekthinking about all this from a UX for indie event posts (and RSVPs) perspective
#tanteksnarfed - I reviewed the Silo SWAT0 summary - it's a very good start
#tantekI think it may be simpler for you to pick which of the players will be using a silo, and then list everything very specifically given that assumption
#tantekrather than trying to figure it out for all three players
#tantekkevinmarks_: "so A is easy" I'm not sure you're qualified to say A is easy without having done A yourself ;)
#kevinmarks_I do have my own app that shwos twitter notifications, which is why I was thinking of it. but no notifications for person tagging in photo is weak
#tantek!tell snarfed I reviewed the Silo SWAT0 summary - it's a very good start. I think it may be simpler for you to pick which of the players will be using a silo, and then list everything very specifically given that assumption rather than trying to figure it out for all three players.
#[snarfed]we could argue that we can substitute mentions for tags, but if we're strict, SWAT0 does say tags
#Loqi[snarfed]: tantek left you a message on 11/14 at 12:34pm: I reviewed the Silo SWAT0 summary - it's a very good start. I think it may be simpler for you to pick which of the players will be using a silo, and then list everything very specifically given that assumption rather than trying to figure it out for all three players. http://indiewebcamp.com/irc/2015-11-14/line/1447533289328
#tanteksnarfed, it would be a useful exercise for us to *attempt* to do siloA indieB indieC where siloA is Facebook, or Instagram, or even Twitter, and then document the roadblocks
#[snarfed]i think we'll actually have to (pick one) due to limited API support
#tanteksnarfed, yeah, of course we'll have to pick one, I'm just saying we try them one at a time, document if/when we get stuck, then try the next one
#tantekthat documentation will help us with going to contacts at various silos and asking for more support
#tanteksnarfed, another SWAT0 variant that involves silos that could be useful is one that uses silos as posting apps, that is PESOS e.g. with OwnYourGram
#[snarfed]based on the cataloging links i mentioned, we can already tell which silos support which participants
#[snarfed]i think i mentioned PESOS. hopefully the writeup supports it too
#tantekI do think the PESOS vs silo-native use-cases are different and each valuable
snarfed joined the channel
#tanteksnarfed: I'm currently continuing to iterate on improving my own photo-posting support on my site, happy to contribute to your silo SWAT0 brainstorming - let me know when you're done editing the wiki.
#GWGI feel that I need a fresh perspective on how to integrate microformats into wordpress
#snarfedk, i'm done for now. based on the research there, it's straightforward to do the arithmetic on which silo(s) could currently do this, if any
#snarfedi'll do that later if no one else beats me to it
#snarfedok, it only took a few seconds, so i did it now. it *looks* like both FB and flickr could do this.
#snarfedmuch of the support would likely happen in bridgy, so i guess choosing one kinda depends on whether kylewm (for flickr) or me (for FB) has more free time right now :P
#GWGI am still thinking of buying a domain and putting up a WordPress Indiewebcamp tutorial site.
#tantekexcellent snarfed! if we can get a SWAT0 success with FB or Flickr, perhaps we can use that to convince Twitter, IG, G+ to provide APIs to participate as well.
#[tantek]GWG, the best way to get more people involved is to be the best example yourself that you can be. Which you're doing bit by bit - eg notifications this past weekend.
#[tantek]Perhaps blog about what you got working with notifications from WordPress, and show screenshots from your blog and phone of receiving the notifications!
#petermolnarI've been thinking of that for 2 years now and couldn't even get on board programmer friends who already has ~self-hosted WP sites
#[tantek]GWG, petermolnar I also suggest focusing on just getting 1-2 more people involved, perhaps your closest ties in that community. That kind of personal focused positive attention usually is quite effective.
#aaronpk"Iām not sure simply reverting back to what we had is the right path if we want to include people who have never experienced the open web or understand its principles."