in reply to microblog.pub
in reply to ˗ˏˋ waaakest ˎˊ˗
in reply to microblog.pub
in reply to Mayel
in reply to ˗ˏˋ waaakest ˎˊ˗
in reply to microblog.pub
@dev your project, your rules. :)

Personally, I am not a true believer in linked data, far from it, but I do think it's better for easily interpreted (meta)data to be encoded usefully, as opposed to dumping everything in the content field. Embedded hashtag and mention links never actually go where I'd like for example.

There are many devices for which an OSM link is not the ideal handler. Some duplication of information isn't pretty, but it works.

More philosophically, limiting ourselves to the most minimal feature set is no fun. Users of platforms that are missing out can always file feature requests. :)
in reply to tedu
in reply to microblog.pub
@dev btw, I've been reconsidering the correctness of putting place in tag vs location. Initially, my line of thinking was an Event takes place in a location, thus location field, but notes are more "about" a place, so it's tag. I'm not sure this distinction is helpful, and is somewhat non-standard. The AS spec simply says "associated". So basically, it's just like a tag, but it lives outside the tag property.

Will probably get more buyin from other projects if we stick to the field that's defined in AS.
in reply to tedu
in reply to infinite love ⴳ
in reply to tedu
in reply to ˗ˏˋ waaakest ˎˊ˗