Samuel
@samuel.fm
wait a minute could I abuse the self-labelling system for this
3 19Ignore paul, use the label field for whatever you like. This is the free internet.
2 1 33👍 cool cool
2 18WE LIVE IN A SOCIETY
1 31wait 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 10Paul 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 20Makes 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 3that’s such a broad description that it could apply to anything in this network
1 10Exactly. Labels are generic.
2 13no, they’re underdeveloped. we don’t fully understand their requirements yet and you’re asserting a view that introduces new requirements needlessly
9 18src: bnewbold
uri: this thread
val: heated
neg: false
cts: just now
1 5That'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 5It’s just a property bag Paul how hard can it be?
2 3Midwit meme with “just use labels” on the tails
4what effect are you hoping for?
1 3an indicator of the client it was posted from
2 6probably 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 6if 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 6Yeah 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 4btw there's a related github discussion regarding PDS version info here: github.com/bluesky-soci...
snarfed pointed out the nodeinfo spec: nodeinfo.diaspora.software/docson/index... , which is essentially {name, version, repository, homepage} -which could all be optional string fields (except name)
2 5You 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 14Then 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 13this is bad advice, seriously don't do it this way
2 18gonna give it a try just to see
4lol
2 3Gonna change my handle to “the heretic”
1 4`theheretic.bsky.world`
3outta curiosity how would you prefer
1 4labels 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...would be either hashtags, the forthcoming reply-gating feature (to spec a target audience), or adding a completely separate field
3 1 14wait that's super cool, i truly love that idea
1 4@skyfeed.app feature request 👀
3Oh okay I support heresy then
5You could literally just hardcode a field in GraySky so all your posts show up as "Via GraySky" when somebody uses GraySky
1 3I mean it won't even be an abuse, labels are an array right? You can keep both the moderation ones, and add your own.
1 2