Zegnat`$mailheader = "From: $email \r\n";` is an extremely dangerous line of code btw. As it allows the person submitting the form to add any headers to the email they want
ZegnatTheoretically I think mail() does validation on subject. I don’t know about message, if that accepts multi-mime messages it definitely requires filtering input, else that seems fine.
[jgmac1106]if there was paid long term storage and I could click and see category in my reader, then within specific groups, federation levels...I try to link to any of my hashtags ans use p-category and rel="tag" on them
[jgmac1106]gwg Known can provide good example but it has all the metadata and since you can add plugins a note that is 5 lines of HTML ends up 500 lines...but page weight still small
[jgmac1106]which means I am a perfect example of p-category being hard because sometimes a hashtag is also the identity of a group and used inside content
[jgmac1106]I hate the new Twitter developer process...every time, the first email they send you they ask you to answer the same four questions you answered in your application
[jgmac1106]davidmead the last seven I mported have no interactions either but I have no idea what the expectations are for behavior, welcomt o bounce off of mine and test back and forth if content won't cause too much context collapse
snarfed!tell aaronpk,cleverdevil,GWG,schmarty,jgmac1106,chrisaldrich,eddiehinkle hey podcasters, we don't yet have exact audio file size (in bytes) in mf2. how should we represent that? i'm looking at converting to RSS, where it's required. more: https://chat.indieweb.org/dev/2019-02-17#t1550418872983700
Loqi[jgmac1106]: snarfed left you a message 5 minutes ago: hey podcasters, we don't yet have exact audio file size (in bytes) in mf2. how should we represent that? i'm looking at converting to RSS, where it's required. more: https://chat.indieweb.org/dev/2019-02-17#t1550418872983700
Loqi[schmarty]: snarfed left you a message 6 minutes ago: hey podcasters, we don't yet have exact audio file size (in bytes) in mf2. how should we represent that? i'm looking at converting to RSS, where it's required. more: https://chat.indieweb.org/dev/2019-02-17#t1550418872983700
[schmarty]Like what is the consequence for a publisher if they put in the wrong byte count? A podcatcher is gonna make an http request for the file and that's going to be the real byte count, no matter what the enclosure attribute says.
snarfedbtw aaronpk you actually only have human readable size (eg 1.23mb) in your mf2. you put exact byte length in your RSS enclosures, which follows the spec
LoqiGWG: snarfed left you a message 1 hour, 39 minutes ago: hey podcasters, we don't yet have exact audio file size (in bytes) in mf2. how should we represent that? i'm looking at converting to RSS, where it's required. more: https://chat.indieweb.org/dev/2019-02-17#t1550418872983700
GWGswentel, I have a proposed ideas of private zones. For example, if you query a location inside the zone, it would automatically return a visibility parameter you could set by default
LoqiPixelFed is open source software for social image sharing, similar to Instagram, that interoperates with other sites using several open standards including rel-me and ActivityPub https://indieweb.org/PixelFed