Loqi[Kevin Marks] Twitter suspended my account for live tweeting, but Twitter Approved an Ad Pretending to Be Twitter - Slate Magazine http://nzzl.us/WBddVYa via @nuzzel
ZegnatI was wondering why I hadn’t received any webmention for your post, jeremycherfas. Turns out you go out of your way to spell out my entire name, twice, rather than just “Martijn” or “Zegnat” with a link to my site. Hehe
ZegnatThat is fine, of course. I was just surprised it wasn’t simply “to ask <Martijn> to explain” with my name linked. Would have also given me a nice ping when you send webmentions out.
ZegnatI think I may have spotted 2 mistakes, one of which seems to be just a brainfart, so you seem to have gotten the gist of it! The flowchart looks right as well
[colinwalker]sgreger’s post yesterday has certainly given pause for thought on the ethical side of things as well as the legality. The distinction between backfeed and webmentions is obvious but has made me start thinking about micro.blog where webmentions are automatically sent and, therefore, not necessarily known about/intended.
ZegnatYes, I thought sgreger’s verification of intended webmentions was very interesting. He only takes webmentions as intended if the source website itself also supports receiving webmentions, as that would mean the source website at least knows something about it.
[colinwalker]M.b can receive webmentions but only processes them under certain conditions (that they can be linked to a user account) - it’s just that people are joining m.b and maybe not knowing about the Indieweb underpinnings so would be unaware that mentions are sent regardless.
petermolnarbecause if it doesn't say anything, embedding, including linking to the source, is perfectly fine - replicating content is the actual question
ZegnatAnd from sgreger’s take, you could store that personal data, as long as you can make a good case that you have reason to do so. But even then you need to have informed the person’s who’s data it is of it. And that last step is tricky.
pindonga, iasai_, iasai and friedcell joined the channel
sknebelYes, but that doesn't necessarily matter. I personally think it shouldn't be a big deal either, but I also get that people are careful as long as these things aren't cleared up
barpthewire, iasai, [unoabraham], KapiX and [jgmac1106] joined the channel
jgmac1106the person who also used an email address to register that anonymous name. I agree with you. I think public is public and when you share on a private platform you are giving up much of your rights. But I fully understand, and current events demonstrate, why something like GDPR is needed. Most of us our noncommercial small sites but many in community will build these features not out of compliance but a shared cultural code. Plus
jmacSo the out-yonder website that linked to my blog which I was excited about yesterday, as it gave me a real-world non-Bridgy Webmention source to test? It's hosted by Tumblr, and therefore the URL that links to my site is http://t.umblr.com/redirect?blah-blah-blah.
[manton][dgold] Yes, it'll pass the date/time in the "published" parameter via Micropub so the blog posts have the Instagram-posted date. Only annoying thing is there's no time zone info from Instagram, so it might be off in some cases. It assumes your Mac local time zone is the same as what Instagram has stored for you.
[manton][aaronpk] Thanks. It's not perfect but I think it's a good default to start with. I wish Instagram's web UI showed the time so it would be easier to double-check. (I checked a few times and they seemed right, but I bet daylight savings time and whatnot will interfere.)
skippy"Due to a bug, passwords were written to an internal log before completing the hashing process." so it doesnt sound like anything leaked; unless some rogue twitter employee(s) leaked something.
petermolnarlol; the first server I had to take over because it's former admin abandoned it had debug logging on for postfix and logged all passwords in syslog as well
[kevinmarks]Twitter has automated systems that find and remove automated spam accounts and it looks like your account got caught up in one of these spam groups by mistake. This sometimes happens when an account exhibits automated behavior in violation of the Twitter Rules (https://twitter.com/rules).