tantek* but deleted posts should still have their own nav (at least for the author view, to see what posts are immediately before/after the deleted post)
Loqi[indieweb] "Hacking on the edge with @benwerd. Open air, floating above the street, talking tombstones, , auto-expiring posts, Confirm Delete POSSE copies, gone, this post is gone. #indieweb #nofilter" http://tantek.com/2016/123/t2/hacking-on-the-edge-open-air
Loqi[Tantek Çelik] a jpg. Hacking on the edge with @benwerd. Open air, floating above the street, talking tombstones, <meta http-equiv="Status" content="410 GONE"/>, auto-expiring posts, Confirm Delete POSSE copies, gone, this post is gone. #indieweb #nofilter...
terminalpixelHey all, just wondering if there is currently a recommended way to do galleries / collections when using micropub? Can't see anything about it on the wiki.
ben_thatmustbemeGWG, its okay, i basically stopped developing it. it works for me at the moment, especially since i made my endpoint work in offline mode
Loqiben_thatmustbeme meant to say: GWG, its okay, i basically stopped developing it. it works for me at the moment, especially since i made my html client work in offline mode
GWGMy goal right now is to finish enhancing the webmentions code and related code, get it committed so I can start using the changes I made to add new features.
tantekone side effect I realized (pointed out to benwerd last night) of using dt-deleted for my tombstoning is that I can "automatically" get /expiring posts (as a feature) by setting dt-deleted date in the future.
tantekto be clear: I'm using dt-deleted purely in the backend flat-file storage — I have no intention of publishing a dt-deleted property at this time (seems more privacy sensitive to *not* publish it, just like blanking the slug makes sense as part of user-expectations of deleting a post)
bearthe openssl one is really specific if you manage X509 SSL certificates in code IMO - still needs to be upgraded but it's not as evil as the imagemagick one
[benatwork]kbs: I think the separation between app and web is about to get really blurry. Nothing to base that on; that’s my intuition. The way to compete with the “app store” is to make apps work like the web.
hongponghi everyone I am working on getting Drupal 8 microformats related stuff implemented - i was made the maintainer of abandoned drupal.org/project/microformats a few minutes ago . first will get the library on there via composer, then will work on hcard/vcard and webmentions. webmentions are currently on 'vinculum' in D7 but will be able to go to more intuitive 'linkback' once we have something functional. please let me know if anyone wants to do
bearaaronpk - the best way to mitigate the issue is to use a policy file for imagemagick, tht way it will never try to evaluate the image items that are used for evil
hongpongi also have reviewed and tweaked a D8 sitewide vcard/hcard module, it works for sure , the patch is here but the maintainer isn't really engaged so i might put it into microformats (leveraging the correct library) https://www.drupal.org/node/2624866
hongpongthank you tantek . someone wrote a h-card for users Drupal 7 version so i will look at adapting that if possible. i think this will be a good architecture to minimize duplication
bearthere are mulitple implementations of image processing tools - imagemagick happens to be the oldest one around and became a default in different language cultures
[shaners]Insofar as code is a creative work owned by its copyright holder, it’s copyright runs for as long as: its owner is alive and Disney keeps getting the US government to extend the length of copyright after death (to keep Mickey out of the public domain).
tantekdym_cx, nope, the wiki is written to capture the current state of discussions, so you can quickly reference the current state (as opposed to email, which is like reading a series of diffs)
LoqiEmail is a decentralized, non-web messaging transport, with typical user interfaces that encourage excessively lengthy messages, in contrast to texting https://indiewebcamp.com/email
aaronpkIt occurs to me that the /projects page was started before the "what is ...?" mechanism, and now that we do that all the time, we're way more focused on individual pages vs making a single page that is a list
gRegorLoveI see your point and kinda agree. It's easy for curated lists to get out of date, too. E.g. when I switched from /Nucleus to /ProcessWire, or when kylewm switched to Known
tantekaaronpk: but even that has a big curated part at the top, and the only reason the automatic list at the bottom has any value is because you made a deliberate effort to document those
gRegorLoveI like the ease of anybody being able to add a [[category]] tag and it updates a list, vs. adding a few lines of description to a curated list
aaronpkWhen a page is created from a wiki dfn, it won't be added to any lists yet. If you look at a page, you can't tell if it's already been added to the list of projects for example
wolcenhey all! Just wanted to pop in and float the idea of a dyndns service for purposes of allowing people to host known instances on their cell phone.
wolcenI know at the recent IWC that the issue of deployment was a huge inhibitor to adoption... if it were as simple as installing an app, could be pretty cool :)
bnvki'm not sure I can fit it, as just in Vienna and there's conferences here in Berlin all week. But I've been thinkin' and brainstorming on re-participating in indieweb :)
Loqi[Chris Aldrich] It looks like no one is maintaining this actively and the last patch was in 2014. Just keeping up with Twitter and Facebook API changes can be painful.
bnvkmore specifically, I'm try to convince my friend Hans (who's working on F-droid store a bunch) to use IWC protocols to implement commenting and such
wolcenin any case - should someone want to help with such an effort, I'm interested and have some domain names to donate to the cause (e.g. indieweb.site)
snarfedabout once a quarter, someone tells me, "hey, my project/community wants to adopt bridgy, and it'd be big - 10k users, 100k, etc. are you ready?"
bnvkF-droid is a software repository (or "app store") for Android applications. The main repository, hosted by the project, contains only apps which are free software. It works similarly to the Google Play store. Applications can be browsed and installed from the F-Droid website or client app without the need to register for an account. "Anti-features" such as advertising, user tracking, or dependence on non-free software are flagged in app desc
tantekwe try to keep things fairly user-friendly around here, so whenever someone uses jargon, we try to prompt to get it defined in a way that is generally understandable / accessible
wolcentantek: lol... I suppose I'm on my own then? Not even a "uh, no wolcen - your wasting your time because X" or "YES! That would work, don't forget to add Y"
wolcencool... well, I'll keep investigating then. It's been percolating a little while - I think it's quite do-able personally. Guess I'll start with testing availability of my phone with DynDNS first off.
aaronpkwolcen: fwiw i started doing something similar for serving websites off of my laptop. I reverse tunnel from my laptop to tunnlr.xyz and serve sites from my laptop from that domain
gRegorLoveSpeaking of confusing link syntax: MediaWiki internal links use a pipe between page name and link text, but external links don't, actually append the pipe to the URL and break it.
LoqiA store (or marketplace) is a service for installing applications on a device, typically a mobile client device, but also on web servers, typically remotely https://indiewebcamp.com/store
bearmy reasoning is pendantic possibly - dreamhost installes application bundles (code + configurations) into the user space ... it's not installing apps onto a remote web server
j12tIMHO, an "app store" has several functions. 1) present available apps 2) allow user to make purchase/install decision, 3) do whatever necessary to deliver app onto device/target, 4) invoice and collect
j12tApple etc do more, but that's arguably not a "store" function, such as 5) filter/curate possible listings, 6) update installed apps after the purchase etc
[benatwork]From a vendor perspective, 6) is completely crucial. You need to be able to update apps seamlessly. Most users won’t. And depending on the vulnerability of the platform, 5) is pretty essential too: you need to be able to yoink out malware.
bearyea, care and feeding of end-user installs is, IMO, the more important part -- anyone can install something, but keeping it up to date... priceless
snarfedloves the contrast of "anyone can install something, but keeping it up to date... priceless" vs "Would you like to restart now or later? How about NO?"
snarfedtantek: but they patch the ones that are known and publicized, which is a big difference, since those are qualitatively more likely to be exploited and get you owned
KevinMarksin that they realised they couldn't patch the underlyin OS reliably, so wrapped up functionality there, and in the compatibility library for new apis
tantekmaybe I should just wait for the EU to sue Apple for all the forced app bundling nonsense the way they are suing Google for Android force app bundling nonsense