[ldavid_ensiie]Need to go, so will come back later. Anyway, I was trying to connect to the wiki to add some ideas about following and interface about how to manage peoples and feeds. I think feedly do it the right way with informations about inactive feeds and others things.
[tantek]And I kinda think that's ok. Domain names are much cheaper than phone plans, computers, etc. so I think it's reasonable to keep requiring them to edit the IndieWeb wiki directly
[cleverdevil]Honestly, half the time I feel really embarrassed for all of the PHP I write for Known plugins, because I really am quite the amateur when it comes to PHP!
Loqi[manton] @Ron This came up recently in the IndieWeb chat. The links work for me (but I haven't tested on Android yet). It might be best to exclude these from the feed since Micro.blog doesn't have special support for them.
[Rose]I need to check what my likes look like in my feeds, pretty certain the way GWG set it up it adds the context that makes it rather better for sharing. But this also leads to the question of "should likes be in the default feed?"
infominer[m]hhmmmm srry been up all night setting up my new (first?) blog off of which I'll publish my indieweb site (once the domain is hooked up)... and heard about some coffeee!!
ZegnatThough I believe there has been talk about putting indieweb.org on a separate just-for-indieweb server. And if we get the 1Password, I would definitely want to discuss sharing server access with a few key players
[frank]Interesting short discussion on likes earlier. I feel the same thing with my own behaviour. I tend to like/favorite a lot of stuff, just to make sure I don't lose it somewhere. But when it ends up on my site, it goes on the feed, syndicates to micro.blog with conversations happening all over the place and pinging back to the original post. But not all conversations. Like me and [jeremycherfas] have about a post. The building blocks are there, they
ZegnatI don’t know exactly how much granular sharing control we can have over passwords in 1Password? But I think server stuff would make sense for a limited group of highly trusted peeps
neceve, anotheryou and [jeremycherfas] joined the channel
[jeremycherfas]I agree. Certainly I am not yet in a place where I can do everything I want from a single app. I still have to check 3 or 4 places to keep on top of all social activity. But I don’t mind, because I think it makes me more mindful of what I say where.
todrobbins, KartikPrabhu, hyper_rau and [Rose] joined the channel
[eddie]Yeah, regarding the likes, traditional feeds and Micro.blog do not handle likes and reposts well and I ignore them from my feeds. They do not provide a good experience
[eddie]Regarding likes in indieweb readers, it’s hit and miss. If you provide the like/repost content/context like aaronpk does in the h-feed itself, it looks great in Together and Indigenous for Android
[eddie]I very much feel that anyone on the IndieWeb sharing to Micro.blog should really follow some people on there and see what the community is like. Feeds like chrisaldrich, GWG and tantek look really out of place because it’s essentially their fire hose. I honestly think it’s a very good idea to tweak your feed to look good on Micro.blog
[Rose]I guess I'm still thinking of likes as in "I have to go looking for them", rather than the more like a repost thing which a like is in the IW world
[frank]I agree [eddie]. I activated my blogfeed a couple of days ago and I really felt like the drunken sailor in the bar just rampaging through conversations talking jibberish. I turned it off again.
[eddie]Oh no, [frank]! Lol I felt that way initially too. It takes a little bit to figure out how you can filter a feed based on your CMS and what you should filter
[eddie][Rose] yeah that definitely helps. I started by saying “don’t post these types”, then I ended up creating a syndication target for it. So only articles and things I specifically syndicate to it end up there
[frank][eddie] I have the same feeling with my homepage. I need to tweak how to present all the different types of output instead of just one big stream.
[eddie][frank] for sure! That can be a big one to handle. That’s something I’ve been working on over the last year. I’m still not fully satisfied with my homepage but happier than when it was a stream
[frank][Rose] But dont forget how conversations might end up. Just today I thought I had a conversation with [jeremycherfas] , on micro.blog. But it syndicated back to my site below a blogpost. No huge problem, but the crashing of separate domains/circles is something to consider.
[Rose]It sounds weird but I'm making an effort not to use the micro.blog app, I've added all the people I follow on it to a people feed in my Aperture install, and my mentions go into my notifications feed
[tonz][Rose] quick question on Compass, as you and [jeremycherfas] worked on it last IndieWebCamp Utrecht: is it completely php/mysql. In other words: should I be able to deploy it on a basic php/mysql hosting package (like where my blog is), or do I need more server access / privs than that?
sebselalso: it stores data in files in a folder, so the primary storage is not in MySQL, but you would still be able to use your basic php/mysql hosting for that I assume
[manton]Good discussion on Micro.blog and public likes. Thanks y'all. I think excluding items from a feed that don't exactly have counterparts in Micro.blog is a good approach. Longer term, I'd like to have more formal support for quoting blog posts, and some special items like [tantek]'s likes could automatically be supported that way.
[eddie]tantek didn’t mean to speak on your thoughts on likes in atom. I more meant your thoughts about your homepage feed. There was kind of two parallel convos that ended up interweaving. Likes in older feeds and likes in social readers
[eddie]I agree there are differences there. And I’m not saying you’re wrong about it. Rose was just asking if the wiki suggestions should be changed and I was pointing out people all have different thoughts on likes in the IndieWeb
ZegnatWhich is why Aperture is hosted as a service managed by aaronpk and does not have installation instructions at all. If you want to install it, be warned, haha
[tonz][Rose] yes, I also have a VPS where I do have command line access, true. But managing a VPS is mostly beyond my skill level, whereas doing stuff within a php / mysql hosting environment is mostly well within my skill level. I’ll put it on my VPS-only list of potential experiments (basically a backlog 🙂 ).
petermolnarI know it's rather insecure, yes; there's always a tradeoff between simple and reliable vs secure, at least in IT, at least according to my experience
[tonz][frank] unsure, not seen it, but I don’t expect judging by their approach to other things (like blocking xmlrpc. They don’t let clients play around on their own much. )
[tonz][tantek] that’s just bs. we’re talking comms w clients, peers etc here, not webppl. 99.999999 of people never talk about their comms prefs let alone publish their contact page.
LoqiAn archival copy is a copy of a web page made (often by someone other than the author) at a particular point in time, that can be used as a reference if the original disappears or is temporarily unavailable https://indieweb.org/archival_copy