Samuel
just realised I can’t add a “posted by graysky” field to posts because then it would become embarrassingly obvious that I don’t use my own app
3 2 48
Samuel
wait so what’s the conclusion of abusing labels for this case specifically. Should I do something more like unspeccedPostedBy: “Graysky” on the post itself (if that’s possible). Or abuse facets instead?
2 10
Why
Paul and I actually disagree here, i think it’s totally fine to use labels in this way. Labels are statements made by some party about a post, and the self-labels are statements made by the author of the post. Plain and simple imo
4 2 20
Samuel
Makes perfect sense to me but I don’t want to accidentally fuck up a potentially large % of posts. Especially since this would be all posts not just a weird special case like, say, custom poll posts
1 3
P(aul) Frazee
no, they’re underdeveloped. we don’t fully understand their requirements yet and you’re asserting a view that introduces new requirements needlessly
9 18
Natanael, Tech janitor
That's why you need stuff like reserved namespaces and defined syntax so you can enforce stricter / more precise logic later without breaking stuff. This reminds me a lot of softforking in new opcodes in cryptocurrency because you can only add rules, never remove any (without unanimous support)
1 5
P(aul) Frazee
we do have mechanisms for that actually, but labels are so poorly understood at this point we haven’t decided whether to use them
1 6
R Sitze
As long as you sanatize them, might be a good opportunity to see what the community can do with them?
1
Barry Dorrans
Attacker, sorry, user controlled property bag, stored in a hash table, with the user controlling the keys. What could go wrong?
1 2
P(aul) Frazee
probably the best move would be to propose a lexicon change, second best would be an off spec field that’s maybe an object for that kind of metadata
1 6
P(aul) Frazee
if the goal is for other clients to be able to render this info then you ideally want to think very generally, like a display name and a URL
2 6
Samuel
Yeah true I’m probably not thinking big enough here. My primary motivation is so I can ask Jaz to see the stats on graysky posts lol
2 4
bryan newbold
doesn't seem that hard, you can just take the input text, render it to a jpeg, and put a sweet Greysky™ watermark on the image. you can even have festive holiday themed watermarks. default to efficient high-compression, upsell to GreyskyPlus for sharp PNG and better kerning
2 1 9
Samuel
Holy shit DLC font packs. Genius. The best part is you get to subject all the other clients to your comic sans posts too
1 3
2 more replies
3 more replies
David Buchanan
"repository" might be better named "codeRespository" or something, to disambiguate against the atproto definition of a repo
3
Why
You should make a “post to community” feature that adds a “community:fishing” type label to posts, then we can make feeds key off of that instead of hashtags or emojis
2 1 14
Why
Then the feedgen could add some curation tools to allow people to moderate those feeds (using app passwords or something) and boom you get subreddits
1 13
P(aul) Frazee
labels are designed to be used for content warnings (moderation). neutral or positive values *might* be possible in the future, but atm it would be a weird complication of the field that might make things much more difficult better options...
1 2 13
P(aul) Frazee
...would be either hashtags, the forthcoming reply-gating feature (to spec a target audience), or adding a completely separate field
3 1 14
P(aul) Frazee
I'm all for bending mechanics to create new systems, but using labels wouldn't do that. it would likely just create unpredictable outcomes
2 12
Samuel
It’d be great to have a similar but more free-form field in that case, I’m sure the 🧪 science feed folks would love to be able to just flag posts directly without wasting characters
3 3
P(aul) Frazee
we should see how hashtags and reply-gates shake out. pretty sure we can get this community-style behavior off them. if not those then something else can work
1 8
1 more reply
Natanael, Tech janitor
You don't want 100% freeform in general. Something like a few types of fixed prefixes defining general behavior, with substrings of known syntax defining more precise behavior, would be more robust. (Would be funny to support Dewey this way)
1
Why
Pauls lying labels were meant to be free. Dont let so called “developers” make you stray from the light
2 3 16
1 more reply