#social 2017-06-21
2017-06-21 UTC
timbl joined the channel
# 
nightpool security "ish" for sure
# nightpool personally, I really wanted to include fa-spin on the blacklist, but in the end I couldn't justify it to myself
# nightpool s/blacklist/whitelist
# 
ben_thatmustbeme Haha thanks ajordan
KevinMarks and fkleedorfer joined the channel
# fkleedorfer Hi, I'd like to join socialcg on w3.org, but the join button here does not work: https://www.w3.org/community/socialcg/
# fkleedorfer The resulting page says: 'The requested group (id: ) doesn't exist ; contact the author of the originating page to have the link fixed.'
# 
rhiaro fkleedorfer: try https://www.w3.org/community/swicg/join
# fkleedorfer great, thanks
KevinMarks joined the channel
# puckipedia yep, that link worked for me too
KevinMarks joined the channel
ajordan, timbl, KevinMarks and tantek joined the channel
# ben_thatmustbeme rhiaro++
tantek joined the channel
# 
@regisrob Linked Data Notifications @w3c Recommandation 2 May 2017 https://www.w3.org/TR/ldn/ #linkeddata (twitter.com/_/status/877515632262225920)
# 
sandro hyper-observant readers will note https://www.w3.org/2013/socialweb/social-wg-charter.html has been updated with a new end date.
tweb joined the channel
# ben_thatmustbeme *and there was much rejoicing*
# 
Loqi Sandro made 1 edit to [[Socialwg]] https://www.w3.org/wiki/index.php?diff=103285&oldid=103213
# puckipedia I'm going to assume that's good news :P
# ben_thatmustbeme just created the agenda for next week
# ben_thatmustbeme hoping to hear back from IANA soon on jf2's media type registration, I just heard back that they wanted additional things for the security considerations section
# ben_thatmustbeme which makes me wonder if AS2 was ever actually sent over to IANA
# Loqi Benthatmustbeme made 1 edit to [[Socialwg/2017-06-27]] https://www.w3.org/wiki/index.php?diff=103286&oldid=0
# puckipedia I already joined now, I think
# puckipedia cwebber2: right, so that's in about an hour?
# puckipedia right, mumble should be set up too
# puckipedia ... trying to add better OStatus compat into my server
# puckipedia but mastodon IDs are not being considerate of my efforts
# puckipedia if you follow and unfollow someone, these two activities share the same ID ... but only if they happen on the same day
# ben_thatmustbeme rhiaro: its not listed in their registry page, but I don't know how often thats updated
# ben_thatmustbeme at least, not that I saw
# puckipedia follows use the date the follow was created
# puckipedia but unfollows have the same type in the tag, but the date of today
# puckipedia same with follow request accepts and rejects, they use the same ID and type as the follow request but with today as date
# 
cwebber2 okay, added some topics to the agenda https://www.w3.org/wiki/SocialCG/2017-06-21#Topics
# puckipedia I should probably ask if there's a reason for those tag types being the same.... it really breaks stuff for me :<
# cwebber2 puckipedia: I wonder what you think of https://github.com/w3c/activitypub/issues/234 btw because I know you're also doing flattening/unflattening
# puckipedia cwebber2: sooooo my unflattener only unflattens things once
# puckipedia e.g. if you have an OrderedCollectionPage with 10 posts all with the same actor, the first instance of that actor it unflattens, and the rest it just uses the string id
# puckipedia I mean, when sending a response
# puckipedia when getting a federated message it only gets whatever it needs to process. so that's possibly the collections/actors an activity/object is pointed to
# puckipedia and ofc the object itself, etc
zatnosk joined the channel
Gargron joined the channel
# Gargron HERE I AM
# ben_thatmustbeme waves to Gargron
RRSAgent joined the channel
# 
RRSAgent logging to http://www.w3.org/2017/06/21-social-irc
Zakim joined the channel
# puckipedia present+
# Gargron present+
# ben_thatmustbeme present+
# ben_thatmustbeme sorry, just back in a minute
# ben_thatmustbeme back
# ben_thatmustbeme scribenick: ben_thatmustbeme
# ben_thatmustbeme TOPIC: tags
# ben_thatmustbeme cwebber2: should we end up having a seperate type and wrapping it?
# ben_thatmustbeme Gargron: would it be a top level type? it would change the meaning of the content, or instead another string like a hash
# ben_thatmustbeme is a bit sick still so my transcriptions may not be as good as usual
# ben_thatmustbeme cwebber2: in the tag example (in irc) you want some sort of ID too
# ben_thatmustbeme Gargron: it feels like the tag approach is not the way to go with this. Its not the same type of thing, its not a hashtag or a mention, that would be a bit weird
# ben_thatmustbeme Gargron: I haven't looked at all the parsing of it, the parsing of this is going to be complicated
# ben_thatmustbeme cwebber2: thats true, if you open up summary to be just a string vs contain other objects
# ben_thatmustbeme ... one reason to use a tag, is to allow people to decide certain types of things they are ok with vs not ok with
# ben_thatmustbeme ... lets them set up their client to auto show vs auto block
# ben_thatmustbeme Gargron: if the name is free text, are you going to categorize it in any way
# ben_thatmustbeme cwebber2: yeah, you would want to, and maybe thats just incomaptible the way mastodon is going
# ben_thatmustbeme Gargron: there are a lot of ways trigger warnings can be used, and some people are not ok with trigger warnings
# saranix still adament that it is appropriate for tags and NOT summary
# ben_thatmustbeme ... some use them for spoilers and some for trigger warnings. it feels like it is more free text
# ben_thatmustbeme puckipedia: it feels like ... for example images are hidden like a nsfw tag?
# ben_thatmustbeme puckipedia sorry, was falling a bit behind there
# puckipedia (hidden with an invisible nsfw hashtag)
# ben_thatmustbeme Gargron: i used nsfw for compatiblity with what they had. it conflicts for user and system space information. If you add a NSFW tag by hand, it has the same effect as the checkbox, but its not obvious that it does that
# ben_thatmustbeme ... maybe its okay, and the tag content just becomes the catch all
# ben_thatmustbeme (digression to location tags and those being their own thing)
# ben_thatmustbeme cwebber2: it also may be that if we tried to move it to tags, we might see a user revolt
# 
jaywink I really don't get the summary example (of the two above). In Diaspora for example, "sensitive" content is indicated by the #nsfw tag, which to me feels appropriate here too. What it is called is irrelevant if the tag is "typed" as ContentWarning. Ie the type feels more important here than the actual tag name. But then, why not just make it a boolean "sensitive: true/false"?
# ben_thatmustbeme Gargron: the goal would be to have it not change Mastodon at all, just change the representation underneath
# ben_thatmustbeme cwebber2: that means you wouldn't really have it in mastodon.
# ben_thatmustbeme Gargron: its really somewhat a domain specific issue. I am more just concerned about encoding it in a way that others can read the same.
# ben_thatmustbeme ... it might not be necessary for content warnings
# ben_thatmustbeme cwebber2: if mastodon isn't going to use it, then it may be the case that leaving it in summary makes sense
# ben_thatmustbeme Gargron: on the other hand, the sensative content thing, i am all for the sensative attribute on documents. there is no other way that can be encoded, it needs to be an attribute
# ben_thatmustbeme cwebber2: we talked about that in the WG
# ben_thatmustbeme cwebber2 he did
# zatnosk Hello, I'm zatnosk@manowar.social on mastodon. Listening in as interested person :)
# ben_thatmustbeme Zakim: who is here?
# ben_thatmustbeme Zakim, who is here?
# 
tantek FYI for all folks here contributing to specs (e.g. CG notes / drafts) who aren't W3C members of Invited Experts already: https://w3c.github.io/repo-management.html
# ben_thatmustbeme present- (at least part of meeting)
# ben_thatmustbeme Zakim, who is here?
# ben_thatmustbeme lol
# ben_thatmustbeme cwebber2: i would be okay it not being a tag, and being a boolean property attached to the object
# ben_thatmustbeme Gargron: if we are just encoding Mastodon information 1-to-1
# ben_thatmustbeme then yes, that would work
# ben_thatmustbeme but i think it might make sense on the document
# ben_thatmustbeme even if mastodon doesn't use that, maybe someone else will, like if one image is sensative, but the others aren't
# ben_thatmustbeme cwebber2: if we move to bool prop, there is nothing stopping it from being on the sub objects
# saranix defintely not boolean. The semantics are not boolean. The semantics are client/user dependant (a client/user may want to use it to influence sorting score)
# ben_thatmustbeme cwebber2: i suppose the reason was we didn't have time and tags was simpler
# ben_thatmustbeme ... but the GW was just extended, so maybe thats ok
# ben_thatmustbeme puckipedia: i think the boolean would be nice
# ben_thatmustbeme jaywink no problem, just funny how that worked
# ben_thatmustbeme zatnosk i missed your intro, sorry
# ben_thatmustbeme cwebber2: lets actually capture this as a resolution
# cwebber2 PROPOSED: Add a "sensitive" tag to ActivityPub in next revision, a boolean, to resolve https://github.com/w3c/activitypub/issues/231 (which can be used in addition to content warnings, etc)
# Gargron +1
# puckipedia +1
# saranix -1
# ben_thatmustbeme +0 as i don't know all the details of it
# ben_thatmustbeme cwebber2: we have a minus 1 from saranix
# ben_thatmustbeme Gargron: saranix isn't on the call, so maybe missed some context, its not content warning, but just sensative
# saranix In my protocol, both content warnings and "sensitive" are handled by a special tag taxonomy
# saranix ... the same tag taxonomy
# saranix ... for both
# nightpool hey, sorry all, just woke up
# ben_thatmustbeme cwebber2: lets just continue, as i'm not sure thats resolved then
# ben_thatmustbeme TOPIC: formatting of tags
# ben_thatmustbeme cwebber2: we talked about this in the WG, evan basically said i don't think we need to specify this itself, but the AP community group needs to come to some consensus on this
# ben_thatmustbeme Gargron: i think the thing is that tags are just strings, there isn't really an "id". But with objects, there is an id, for links there is a href, where does that tag live
# nightpool q+ about ids
# nightpool fuck
# nightpool q- about, ids
# nightpool q+ to talk about ids
# ben_thatmustbeme cwebber2: for mentions, those do have an id, but for general string style tags, i think (even evan) said that most tags do exist in some global namespace
# ben_thatmustbeme ... the possibilities are to use http ids and use fragments
# ben_thatmustbeme ... its possible to use ostatus tags
# ben_thatmustbeme Gargron: Mastodon doesn't use the groups parts of ostatus
# saranix +1 uri "https://tagnamespace.example#foo"
# ben_thatmustbeme cwebber2: i think those would work well as mentions
# ben_thatmustbeme cwebber2: is the difference between having things that don't have uri vs do
# ben_thatmustbeme Gargron: yes
# ben_thatmustbeme cwebber2: part of timbl's whole idea was that fragments are supposed to refer to things that you might not actually be able to retrieve it
# ben_thatmustbeme like gps coords then fragment for the bike at that location
# ben_thatmustbeme so this works in that sense, but ...((??)
# ben_thatmustbeme Gargron: how about just using the same one for the public collection, then just tacking on the hashtag at the end of htat
# ben_thatmustbeme cwebber2: you risk people throwing in things the refer to real activitystreams properties
# ben_thatmustbeme cwebber2: i think it would need its own seperate base url
# ben_thatmustbeme nightpool: saying a hashtag doesn't have an ID doesn't really ring true to me,
# ben_thatmustbeme every hashtag i've seen links to something
# ben_thatmustbeme cwebber2: are you talking about how servers often have a collection
# ben_thatmustbeme nightpool: they always seem to link to one location
# ben_thatmustbeme Gargron: its just a keyword, you may filter that by local only or all known posts, but its just a slice of everything
# ben_thatmustbeme nightpool: that just means we need to standardize the names better, instead we should have a type that has a specific name field
# ben_thatmustbeme cwebber2: we have that
# ben_thatmustbeme nightpool: but the way to specify that its actually...
# ben_thatmustbeme cwebber2: you end up with blank nodes which go to np-complete type problems
# ben_thatmustbeme is that np-complete or np-hard? hehe
# ben_thatmustbeme nightpool: it specifies which instance that hash tag comes from, which i think is useful
# ben_thatmustbeme Gargron: you don't have different hashtags you just have one
# saranix http://somesite.example/foodie-tags#flavors -- fetching http://somesite.example/foodie-tags would pull the whole taxonomy, #flavors would point to the fragment within the spec for that tag?
# ben_thatmustbeme nightpool: suppose its like a group
# ben_thatmustbeme Gargron: they aren't groups, you would need to have a way to get a hashtag to a certain server
# ben_thatmustbeme cwebber2: i suggest we use the queue as we have a lot of people now
# ben_thatmustbeme to put this is prospective, where should it point, do we point to some abstract place, or per instance
# nightpool tantek: something we discussed this week was ways that JSON=LD specifies for resolving fragment identifiers
# ben_thatmustbeme lets say we have a federated situation, suppose on each our instances we both tag our #food
# ben_thatmustbeme do you expect to see your own server's local knowledge, or do you assume you will see only the remote server's
# ben_thatmustbeme nightpool: i think that depends on the situation
# ben_thatmustbeme sometimes you want to see only those for an account, sometimes all globally
# ben_thatmustbeme i think the best is for like federated and local timeline
# saranix This problem cropped up in Zot vs Diaspora. Diaspora treats all tags as global, zot treats them as local. When I support both protocols, I have a global tax and a site tax to distinguish.
# ben_thatmustbeme you have these resources that are fused into local resourse
# ben_thatmustbeme cwebber2: any other thoughts on that?
# saranix I think as far as the spec goes, there should be a specified url (taxonomy) for global tags
# ben_thatmustbeme Gargron: mastodon does turn all hashtags into a local link, leaving your instance to another place, is bad user experience
# ben_thatmustbeme a lot of mastodon is built on 'we fetch all the data that we need'
# nightpool to be clear, what I meant was "sometimes you want to see your local instance's view of the hashtag, sometimes you want to open up another instance's view of the hashtag"
# ben_thatmustbeme cwebber2: does it have the sense that we are transforming the global in to the local?
# zatnosk I need to leave now. It was nice to follow along :)
# ben_thatmustbeme Gargron: on one hand yes, we do transform the global into the local
# ben_thatmustbeme waves to zatnosk
# zatnosk waves! thanks for linking on mastodon, cwebber2 :)
# ben_thatmustbeme Gargron: the way mastodon works, you only load what you need, a small instance can exist because it only gets what it needs
# ben_thatmustbeme i am against having anything fully global that puts that extra weight on small instances
# ben_thatmustbeme cwebber2: if we wanted to be able to distinguish both, we have id and url
# ben_thatmustbeme we could point the id at the global version and the URL at the global version
# ben_thatmustbeme <ben_thatmustbeme> that sounds really odd
# saranix Users should have the choice, they should decide if they want their tag to be in the global namespace, or the site namespace, or some other namespace. This is what my protocol allows.
# ben_thatmustbeme Gargron: i suppose what matters for me is I don't think Mastodon will use the id or the url for parsing tags out of json, its going to use the name tag
# ben_thatmustbeme its going to be redundant to use those other tags for me
# nightpool q+
# ben_thatmustbeme s/tags/fields/
# ben_thatmustbeme Gargron: the only thing we need ids for is the metadata
# ben_thatmustbeme nightpool: id on't think the issue is how we represent it, its that we don't have tags in our ontology at all
# ben_thatmustbeme so a hashtag type is the way to solve it
# ben_thatmustbeme Gargron: i agree completely
# ben_thatmustbeme You can tell if something is a mention, because it has a mention type, the way its in AP spec, you can't tell if its a tag or something else
# ben_thatmustbeme puckipedia: i already experiemented with a tag type as i needed it
# nightpool +1
# puckipedia +1
# ben_thatmustbeme +1 seems pretty reasonable
# ben_thatmustbeme puckipedia++ for citing implementation experience
# nightpool present+
# Gargron +1
# ben_thatmustbeme waves to Gargron
# ben_thatmustbeme suggests webfinger
# ben_thatmustbeme throws explosives into the room
# ben_thatmustbeme cwebber2: we did agree that webfinger was important to resolve within the scope of AP
# ben_thatmustbeme ... we have yet to answer how webfinger fits in
# ben_thatmustbeme it was not cwebber2
# nightpool q+ to talk about userless actors
# ben_thatmustbeme ben_thatmustbeme: for me the concern has been to replace it with an improvement
# saranix on edge of seat
# ben_thatmustbeme cwebber2: its not going to disappear soon
# ben_thatmustbeme no one scribed self
# ben_thatmustbeme i know many projects rely on it
# ben_thatmustbeme sites like mastodon and gnusocial and diaspora still use it
# ben_thatmustbeme cwebber2: we need to give some sort of compatability route for them
# ben_thatmustbeme nightpool: mastodon has had some problems with webfinger, (using external services)
# ben_thatmustbeme nightpool: having actors that are a whole domain is such a niche market
# ben_thatmustbeme <ben_thatmustbeme> nightpool i would HIGHLY disagree with that
# ben_thatmustbeme nightpool: i would say if we have a simpler protocol that doesn't support userless domains we should look at the simpler
# ben_thatmustbeme puckipedia: the same could be done via subdomains
# ben_thatmustbeme sandro: this covers a lot of existing sites that aren't social
# ben_thatmustbeme ... i'd like to see them involved
# cwebber2 sandro: another argument for user-less domains are a large number of existing websites that I would like to see become entities. every business / school / etc has some way of talking to the world and we have no way to figure out what that is. currently there's no computer readable protocol to figure that out
# ben_thatmustbeme right now there is no computer readable method to do that
# ben_thatmustbeme ... i think its more than that
# nightpool q+
# cwebber2 ben_thatmustbeme: I'm not saying we should try to make it a ton more complex to support it, the enconding of webfinger right now is more complex in the discovery, the definition is user@host, if you leave off user at that and have host just be the domain, and even subfolders, it's backwards compatible (and we need to be backwards compatible to webfinger) but even the change of allowing hosts to have a path, and doesn't add a lot of
# nightpool hosts are allowed to not have periods also
# puckipedia q+
# cwebber2 nightpool: the other thing I wanted to register is an ideological disagreement to the idea of social actors that aren't users, I'm not interested in building a social network for coprorations. I'm not saying the group should hold that up, but I don't think that, aside from bots, we don't have things like brands on mastodon, and ideologically I agree with that
# ben_thatmustbeme scribenick: ben_thatmustbeme
# ben_thatmustbeme cwebber2: at least from activitypub's standpoint, we support http urls
# ben_thatmustbeme http urls work great for single user
# ben_thatmustbeme what is the debate we are haivng
# ben_thatmustbeme we aren't going to replace webfinger any time soon
# ben_thatmustbeme we have a route for single user sites
# ben_thatmustbeme sandro: we don't
# ben_thatmustbeme a single user can't talk ... lets imaging mastodon implements AP to the spec, and aaronpk supports activitypub
# ben_thatmustbeme i'm in the mastodon instance, how to i refer to him, how does it look
# ben_thatmustbeme cwebber2: if mastodon can support http uris in addition to webfinger, then they wouldn't
# ben_thatmustbeme s/wouldn't/would
# ben_thatmustbeme sandro: i don't think nightpool would want to support that, nor would the mastodon community
# ben_thatmustbeme nightpool: i don't know what Gargron's thinking on this would be
# ben_thatmustbeme .. i don't think he's considering moving away from webfinger
# ben_thatmustbeme puckipedia: another thing is that if you allow just a uri as a mention, and you have single user websites, what would be the difference between mentioning me vs my website
# ben_thatmustbeme ... allowing uri addressing but prefixing it with an @ would be the best solution with that
# ben_thatmustbeme cwebber2: in the case of https://puckipedia.com, you'd do conneg to pull down the the cotent of the actor vs
# ben_thatmustbeme sandro: are you saying you'd have to have a different URL for himself vs his blog
# saranix is confused -- seems like settled pretty easily with acct:user@host vs http://site/user/specific-collection/
# ben_thatmustbeme sandro: i think a profile url is different from a blog url
# ben_thatmustbeme cwebber2: saranix brought up the acct schema
# ben_thatmustbeme s/schema/scheme
# nightpool q+ to talk about "publically resolvable"
# saranix tells tantek I do, but not that I'm sharing just yet ;-)
# ben_thatmustbeme sandro: it seems like one quesiton to figure out on the sooner side, is mastodon and other members of the fediverse willing to move to support some kind of non-webfinger ids
# ben_thatmustbeme if yes, we can do that, if no, we need to figure out some other kind of solution
# ben_thatmustbeme nightpool: one of the problems in the spec is that every ID must be resolvable, there is no reference as to what that means, is acct:// publicly resolvable?
# ben_thatmustbeme someone brought up an issue on github of supporting non-iana urls
# ben_thatmustbeme you can't resolve those if you aren't on openDNS
# ben_thatmustbeme we need some kind of clarification behind that
# saranix I think webfinger itself references an rfc for coming up with the acct: scheme
# ben_thatmustbeme cwebber2: i think there is no where you are going to be able to resolve an open dns if you don't know what it is
# ben_thatmustbeme we have not specified what schemes are not usable
# nightpool s/non-iana/non-icann/
# nightpool s/openDNS/openNIC/
# cwebber2 ben_thatmustbeme: I want to talk about what sandro raised, I wanted to see what it would be like to support non-webfinger uris... pretty nobody was in favor of supporting just https://ben.thatmustbe.me/ but it was pointed out that you could just leave off the user and itw ould work, and it would be at-prefixed, but it would refer to a domain
# nightpool openNIC was the project I was referring to
# saranix cwebber2: ??
# ben_thatmustbeme i actually have to leave anyway
# nightpool dots vs no-dots seems like a very fragile solution
# ben_thatmustbeme +1 to wrapping up
# nightpool ben_thatmustbeme++
# RRSAgent I have made the request to generate http://www.w3.org/2017/06/21-social-minutes.html trackbot
# saranix is it bad to force the posting site to do discovery on the mentioned url to determine whether it is profile or stream?
# puckipedia saranix: depends. the receiving sites might not trust that information
# saranix puckipedia: what do you mean?
# puckipedia like, someone might say 'this url actually is a profile' but just fake a profile
# nightpool Here's the issue I was referencing: https://github.com/tootsuite/mastodon/issues/3741
# saranix No, I mean, if I mention a url in my post, the software should then discover what type of url it is, and if it is a profile then treat it as a mention, if it is a stream, treat it as a link
# nightpool which is basically a protocol question about how to work with parts of the network that can't talk to other parts of the network
# nightpool and the broader question I was raising about what counts as a "Publicly dereferencable URIs"
# nightpool definitely takes on some subtlety when seen in this light.
# saranix Because the issue raised earlier about mentioning a person vs mentioning their blog
# saranix I'm just trying to follow what everyone is talking about but I think I'm just getting more confused
# ben_thatmustbeme saranix: part of th problem is there was so much talking it was hard for me to keep up
# ben_thatmustbeme really technical discussions tend to fall behind in the logs, but we still scribe far better than some other groups do
# ben_thatmustbeme at least from what i hav eseen
evanminto joined the channel
# ben_thatmustbeme Zakim, bye
# ben_thatmustbeme cwebber2: minutes are posted, also created agenda for next week
# ben_thatmustbeme saranix: where was that raised?
# ben_thatmustbeme on IRC or do you have a link, i'd be interested to read that discussion as well
# saranix I'm referring to https://chat.indieweb.org/social/2017-06-21#t1498061135205000
# ben_thatmustbeme you said you raised that issues before though
# saranix ? "earlier" as in a few moments ago...
# ben_thatmustbeme oh okay, my missunderstanding
timbl joined the channel
# ben_thatmustbeme seems to be duel use of the sensative property though, just have to specify that in the case of obj.tag.sensative it has the meaning of obj.sensative
KevinMarks_ and timbl joined the channel
# tantek cwebber2, it can be potentially counter-productive to capture a political consensus in the absence of documented data, as it tends to imply / reinforce a culture of reaching consensus based on a set of opinions (political), rather than documented evidence / use-cases etc., which is always harder (more work), but nearly always results in better (more repeatable/reproducible by others outside that small group) decisions , designs.
# saranix would be happy to see work on issues like this wikified
# ben_thatmustbeme sandro starting to gather info from other groups on how webfinger names are used. https://www.w3.org/wiki/Socialwg/AccountDiscovery#Current_usage_and_interest
# ben_thatmustbeme bunch more info than i can put on here right now
# Loqi Benthatmustbeme made 2 edits to [[Socialwg/AccountDiscovery]] https://www.w3.org/wiki/index.php?diff=103324&oldid=103106
# saranix I think implementations wishing to meet a global standard must allow ".". Other characters such as "+" should also be allowed. Right now when federating with Diaspora I have to do a rediculous workaround with a hackish encoding. When using a global standard I'd rather not have to keep resorting to hacks.
# saranix ben_thatmustbeme++
# ben_thatmustbeme saranix, whats worse, i heard that some implementations just treat certain characters like _ as ignoreable, so john_doe@host and johndoe@host get confused to be the same user
# saranix does a flamboyant "aww, helllll no"
# saranix my aforementioned "hackish encoding" uses _ -_-
# saranix uses "-"
# saranix GAH!
# saranix uses "_"
# saranix the other was an emoticon.
# ben_thatmustbeme lol
# ben_thatmustbeme they all sort of look like emotes :)
# saranix lol
# saranix about right too
# ben_thatmustbeme from a third party, so take it with a grain of salt but, "I believe GNUsocial ignores periods, underscores, hyphens in usernames and hashtags. @you@host and @_-.you.-_@host would then be the same. However, Mastodon considers underscores significant in usernames and hashtags"
# saranix hmm. If true, that means I won't be bothering to try to federate with GNUsocial then, or it least it is absolute last priority. They should be updating to ActivityPub anyway. So as long as AP and other standards are made to allow it going forward we are good
KevinMarks joined the channel
# saranix It would be nice if the characters WERE well defined. I used https://en.wikipedia.org/wiki/Email_address#Local-part as a guide. although I must ashamedly admit I am not UTF8 compliant (yet)
# MMN-o Sorry I missed today, I was out fixing my bike .)
# MMN-o Didn't hear my alarm or anything.
# MMN-o Good evening though, my job this summer is essentially to run a bike workshop at the youth centre where I work. Very few visitors today, so I had the chance to fix my own bike .]
# MMN-o saranix ben_thatmustbeme: It's perfectly possible to subscribe and reply to remote users with _ etc. in their acct: URIs in GNUsocial.
# MMN-o But yes, in the local database they're filtered out, but it's only the local representation and does not have any significance in the federation mechanism.
xmpp-social and _xmpp-social joined the channel
# 
ajordan is currently in the room for http://opensourcebridge.org/sessions/2082 :-)
xmpp-social joined the channel
# xmpp-social [ajordan] test to see if this makes it through to IRC!
# xmpp-social [ajordan] Inspired by #pump.io
KevinMarks_ and KevinMarks joined the channel