#Meta Discussion
1 messages ยท Page 2 of 1
im not talking about the UI, im talking about the mapping of data to interaction, and again, showcase v1 maps perfectly to showcase v2
its not about the showcase really its about the "lets turn it off and see how it goes"... like, as NB said, its small, who cares. But i hate that idea when it wasnt needed in the first place
who cares not my take. I care, that's why I went for this.
then why not keep both channels open and see "which wins"
survival of the fittest lmao
you have a bias, dont pretend you dont
do you not also have a bias?
100%, ive made mine clear, but i didnt turn anything off
my bias is the old way. But, I said that the way people interacted with that channel before I made it into what it became was different, and I saw people "enjoy" the old style more than the new style of that old channel
i dont think your bias is the old way, your bias is using a new feature :p
or at least, it was a "different kind" of enjoyment
I think the new proposed solution seems to allow people of both biases to have it their way
unless im missing something
^
(this is why java script framworks are in such a mess ๐ )
what is the new proposed feature?
both a single channel of showcases, like the old way but without responses
if my bias was the new way, wouldn't I just abandon the old way altogether? My bias is community engagement first and the "features" that facilitate that
and how does that work with "i just made this"... and why does it need a [showcase] command
/showcase will add it to the showcase channel
what, for example, is wrong with a channel, 100% like before, that, when it gets to "wordy" people ask it to be moved to a forum thread about said project X
wait what was the question
(for example)
I tended to miss most of those
its like "we have forums, we must use them", even if they dont fit (which they dont for the showcase imo, or at leas the previous version of showcase)
new way won't need a command
anyways, its all over complicated imo (im ofc willing to be proven wrong), its a problem (that didnt exist, personally) that might have been fixed by forums if used alongside
again, I personally find the new way far more engaging
[showcase] tag is for forum posts to auto crosspost into the showcase channel - this is for convenience
/showcase command will now (from the discussion with frying pan who came up with a better idea than mine) will now just be a "gatekeeper" it will specify the rules and nature of the new channel. Which will be read only by default. And you can post into the channel "freely" but now there will be active content control on the channel
great, so that proves me wrong, for you. I disagree (personally), but the two methods could happily co-exist
after agreeing to the rules and nature of the channel with /showcase command. You'll get a role showcase and then its use is the same as before, except hopefully clearer and more organised
what if the [showcase] tag wasn't limited to forums
what if you had showcase channel and forums... ... ๐ฎ
bruh
thats what is happening
i mean without the magic... forums... ... showcase channel
should have been a no brainer
splitting up showcased content between a forum and a single channel is a silly idea imo
your way is certainly the easier way, my way requires me to pay closer attention
what if any channel (assuming it's relevant to that channel) can have showcases.
so i could showcase a new flixel release in the #flixel channel
thats why I keep mentioning that the crosspost would link to the source message
people would just talk about it in the #flixel channel
why not? Or a "flixel showcase forum" that you post links to in the "show case" channel
I could do that, i didn't think of it outside of the new forum feature
mostly cause of ian's idea of autolinking back to the forum thread
which i thought was neat
yeah, that seems very necessary imo
(not as neat as just being able to post what you like in a channel ofc - assuming its relevant)
gotta find the right balance and sometimes to do that you gotta tip the scales a bit
to me the problem of having to create a forum thread is smaller than the problem of having every showcase discussion in a single channel
mostly because you don't HAVE to make a forum thread
just talk about it in the various relevant topic channels
but this is what annoys me slightly. This is exactly what im talking about. There is no balance to tip. You could have just opened a "project forum" and directed people (organically) to discuss X or Y there. Instead you went full parental mode.
I'm just having trouble seeing the downside here
im having trouble seeing the downside if either / or were a thing
like if ther was the old channel and forum with an auto cross post channel?
"wanna post a picture and someone starts a thread"... "cool, its not really how we do things anymore, but cool".... "wanna post an update to a project and discuss", "cool, we have forum system for exactly that"
Hmm, you're kind of right there. I certainly did not do this out of impulse, but I didn't discuss it. I did think hard about it for a while and it seems like the right thing to do. I guess what you have an issue with is, is my attitude of "I think this is the right way to do things".
I think I should have discussed it with the mods, which is definitely an oversight on my behalf. Dang.
my issue is simply throwing the baby out with the bathwater... no reason both couldnt have existed (and no bots, no code, no nonsense).
things tend to move organically to the "right" direction (for the community), look at SYW before you turned on slowmode
Honestly, I think both options have pros and cons, but I agree with @carmine star in the sense that having content fragmented into 2 locations (showcase channel + forums) makes me uneasy. There will be content you donโt see if you only checkout showcase channel because, for sure, not everyone will use [showcase] command etcโฆ
I have given multiple reasons as to why both shouldn't exist for a temporary period of time. I'm not going to repeat them, as you seem to just not value them to even acknowledge them.
This is not organic movement, this is still enforcement. It's just "gentler" the only difference is - is that my way is just abrupt. It's essentially efficient
(But maybe Iโm wrong and everyone will use [showcase] properly)
This is not organic movement, this is still enforcement
gotcha... ๐ฎ
i prefer forums for projects that have multiple updates
by this, i was referring to slowmode
and constantly reminding people to "stay on topic" is not really a pleasant experience either
understood - thankfully
How long has this discussion being going on? ๐
doing that immediately kills any convo that people are having
multiple days
but there wasnt anywhere else to take it
i don't know why
o god
to solve a problem that doest exist? :-p
@misty pollen We could've played factorio with all of this time!!!
would have been simpler
in your opinion
I should get factorio
Honestly a great game, a perfect programmer genre game if there was one.
actualy, someone should get factorio for me
that is better
Idk, smth like shenzhen i/o is probably better for something like that lol
omfg... its not that "this problem exists" or not. Its that clearly, there are differences in usage, and turning off one "to see how the other works" might kill both of them
It wouldn't though, this community isn't that "weak" ๐
and i was clear that it is only a temporary move
i think my "annoyance" (on this topic) is above this community, i thought we were engineers...
you have to be pretty strong headed to do anything productive with haxe 
lol
"lets turn off the fan belt, just for a minute, to see if that helps the brakes work"
Haxe is simultaneously the worst and most productive language I have used
That's the most meta thing I've heard ๐
I keep wanting to play factorio, it's on my list. seems fun
i mean, people will slot on the scales in various degrees. But, my position here has me focus on community, I'm not really sure how it wouldn't otherwise ๐
you are always fighting with it, but it will do what you tell it after enough fighting ๐
Do you have the game? or on your list as in to get it?
NotBilly, its like im talking another language: if its "all good" then why not keep the old way, introduce a new way and see what happens?
gonna talk about factorio in #casual-chat
make a forum post ๐
A few weeks of experimentations is not a big deal imo, letโs take it easy, and well, I appreciate @civic sky is trying to improve things, even if the process can be a bit chaotic sometimes. Itโs not like we canโt discuss anymore and the whole discord is cut, nobody gets hurt ๐
A good use of forums would be to move Linux Nerds and Wordle Nerdles into a more permanent thing
at this point though they are basically already permanent though
100%, if im going "overboard" its not at @civic sky 's dedication to this server, this space and this community. That is without doubt. None of us would be having this conversation if it wasnt for him. My point, simply, is that one feature didnt need to cancel out another
Yeah, we should make linux nerds into its own channel
although i think having a "general purpose" forum for talking about whatever would be neat as like an alternative to #casual-chat (but not replacing it)
freedom from the chains of the thread!
because its kinda hard to find threads right now imo
in normal text channels that is
not forum channels
i mean, it isn't that hard to mass ping people into the thread
ok but lets someone wanted to start a Windows Nerds thread, it would be kinda hard for anyone interested to find it if they happen to miss the "thread created" message
not to mention how that would be heresy ๐
If show-your-work gets killed off it'd be nice to have a channel :]
Sometimes I get the impression you don't like windows ๐
That said, it's hard to find stuff in sym if you didn't see the ping or a subsequent comment - you don't know what was to posted to look for anyway - with tags you can see topics that might be of interest
Thinking again about what has been suggested by @carmine star , and actually that could be nice: a show-your-work like before + a general purpose forum not necessarily used to present projects. Maybe thatโs not a bad idea
I also think the forum-like display could be a better fit for asking for help in haxe in general. When asking something in the current #haxe channel, something can easily get lost in the flow without any reply (it happened to me). Having a real post is probably better to get the question visible, and also to find it later
there's already #1020312969361498112 which should function exactly the same, right?
Yea that works too if the old "show your work" is just a topic in the forum-thing I guess
My point is that forum display could be a good fit not only for showcasing stuff
Currently discord forums are quite uncomfortable to use, so I'd rather not visit forums in the first place, lol.
Unless I want to visit specific discussion.
the only possible complaint I have is following too many forum threads clutters up the sidebar ๐
otherwise it seems to be exactly like a normal discord channel
Honestly, I don't think it's that bad, it has some advantages but I guess we are becoming subjective here
It's more about UI. Feature itself is overall good I think. But implementation is... eugh.
it would be nice to have the ability to collapse forum threads in the sidebar so only updated threads show up
Yeah, for me the advantage is to be able to tidy things a bit more, like some conversation is not something hidden in a big flow of messages in a single channel
I suspect they'll eventually have to add it (discord devs I mean) due to user pressure.
Hopefully user feedback will make it better
Discord getting more and more corporate. And you know what corporate is extremely, amazingly good at? That's right, making UX worse.
I think I missed something - is it possible to create threads within forums ? I couldn't see anyone having done it and I cannot see how to do it myself
the chat we're in right now is a forum thread - a little different than a regular discord thread
not by much though
Okay, look at that HUGE ASS search bar. And even a HUGE ASS blue button.
I love wasted space in discord.
Also those rounded corners look like shit, gotta love rounded corners everywhere, it makes apps look like garbage. 
lol well now you're heading off into real subjective territory
I think the biggest gripe I have with that top section is it's easy to conflate making a new thread with search
I don't think the new post button should be nested in the search bar
I mean create a thread within a forum channel on reply to an existing post
Look at my custom-ccsd discord and claim it looks worse than default garbage with rounded corners. I dare you. 
No, you can't. It's a feature exclusive to regular channels.
yeah so because we're technically in a thread you can't make new threads
that's actually a shortcoming
Forums is essentially post-threads but more persistent and have to be started manually instead of having to create them via answering.
they didn't make that mistake did they ?
groan
oh well - that's a pity
hopefully they can add it - w/o it more general channels will not be able to host very specific discussions out of band
but thanx - I missed that
looks old ๐
is it just one like of css like border-radius: 0 !important;?
Not exactly. I keep rounding on some elements + I now need to update it for forums.
but fortunately this is configurable
do you like it tighter?
yes
haha I love some whitespace
Oh, didn't knew they added that

Holy shit it now looks so much more compact.
but when chatting and coding I get that it's nice to see more verticality
as far as the layout goes in the side by side panes on a reasonable size screen I quite like it
easy to scroll the forums and checkout what might look interesting
and following what you want is good
wish they had threading
I'm okay with subtle rounding. But all apps fucking abuse it making it badly stand out.
I guess it depends on the app for me
I like rounding on entertainment or "fun" apps but don't really love it a lot with productivity apps
Sure, it's contextual. But when it's ON EVERYTHING like in discord - it looks like shit
i have a threshold, as long as the UI changes doesn't make things laggy or too inconvenient, i'm okay
new discord mobile app is garbage
UI changes doesn't make things laggy
HA.
i don't even know how they can mess that up so badly
Every fucking time I see redesigns of UIs on websites or apps they perform much less responsive + less features.
You rarely see actual improvements on those.
I don't think less features is a bad thing but I think I'm in the minority there ๐
I will stab you.

If feature is here and it suddenly get yeeted with no reason - whoever decided it being deleted deserves their arms being broken.
๐
It's because discord is FUN
(fun = rounded? ๐ )
eh features is overrated imo a great program or game does one feature as well as it can and every other feature brings diminishing returns until quickly the feature set becomes unwieldy
ironically you're complaining about a new feature
auto creating threads is kinda ugly ngl
and it'll probably take time for discord to address the issues you have with it because they also have to maintain tons of other features
title isn't very intuitive ๐
Question:
I had to make a bunch of guidelines for #1019922106370232360 when i created the channel
how does that present to you guys? I've never seen them anywhere
Never even noticed it lmao
Please do not post projects made in other languages here. If your project is 50% haxe 50% cpp that is fine to post
But HL extensions are more C than CPP
What if the project is an ocaml mod for Haxe?
I think the rule should be changed to "projects which are of interest to the Haxe community"
As there are things that are not made in Haxe, but which are interesting
Such as Haxe language support for text editors
I mean, haxe related covers both of the above?
they seem to conflict with each other
Here's my biggest issue with this format:
In the old style, I could ignore the show-your-work channel for days or weeks and then come back to it and do a scroll through and see everything that was posted since I had last checked.
and, at a glance, stop on stuff that looked interesting that might be totally new, or an exciting update to a project, etc.
With the new system, you lose that.
You either have to follow specific projects from the beginning and then go look when they say they have new posts to see if anything is new, and projects that you're not following might be posting cool new updates and you'd never know unless you go look at ALL of them.
All you have to go on is the very first image that was posted (if there was one) - you can't quickly see if a project has changed or evolved or gone from 'meh' to 'OOoohhh' since the last time you saw it...
I think this format works great for a project that wants lots of discussion or feedback about it - but as a showcase of 'here's something cool to see' I think it is a detriment to that.
just my 2 cents ๐
Agree, old channel should reopen under the new setup within a day or two
Like I said, though, for people/projects wanting deep feedback or help, I think the forum style is the way to go.
This should be renamed to "project-log"
or just projects
So the new system will be 2 channels:
#showcase
#projects
#projects - is #1019922106370232360, the forum layout
#showcase - will be a channel purely for "what is going on" in the haxe community. It will be read only, by default. To access it you have to type /showcase and just hit agree to this. Mostly so people aren't immediately surprised to see their message get deleted and they understand the rules of the channel from the get go
The channel will have 2 ways to post to it:
Regular discord chat way. Slow mode is set to 30mins on the channel.
And by using the [showcase] tag in a forum thread
If you prefix your post with [showcase] within a forum thread, it will cross post to #showcase channel with a link to your project in #1019922106370232360
Regular threads will be enabled for #showcase. Messages that are deleted from #showcase are sent to the authors DM
hmm maybe I should do in server, hidden message instead of a dm. People may have dms off not sure how that works with bots
In the forum you can sort by creation date or recent activity but you don't seem to be able to sort by unread new posts or something similar - is there anything like that ?
nah, that may come. The feature is still in open beta
I only realized that today - it's only been out a week or something
o
it has been out for a few months, but to communities bigger than ours
oh
1244 comments lol
This must be a very popular project!
My 2 cents: so far, so good. I really enjoy the thread system because it allows to post more frequent updates for a specific project without flooding a single channel. Also, just like good old forums, it allows subscriptions to projects you'd like to follow.
BTW, this could probably be very useful to have something like that for #tools as well. I would totally use a dedicated thread for LDtk related stuff ๐
Well, ldtk kinda falls under "projects" umbrella, no?
(Given that forums would be renamed into "projects")
what is "projects"? ๐ค #1019922106370232360 ?
Yes. Look a few posts up, there's explanation from Billy.
My bad! I didn't read previous messages ๐ฌ I agree
good thing I'm off work this week ๐
I think there are 2 issues with this is that the discussion around the release in a general channel can
a) it can be interspersed with help requests
b) people who are interested in the showcase, but not "flixel" may naturally just not want to follow over to #flixel or #heaps
Neither of those seem like deal breakers to me, they seem like bad executions, or rather, a good use for threads
so [showcase] within threads outside of #1019922106370232360 instead?
Or you [showcase] in say, flixel and then make a thread off that original showcasing message
So when people click the link it's the message in flixel with a "George created a thread" box right below it
Alternatively i could make a thread and then showcase inside it, but i expect this to be less common
Unless they are showcasing an update in an existing showcase thread
the issue with auto creating threads is the title
I dont mean auto creating
threads require a title parameter, which isn't really doable without directly requesting a title
I just mean they can make a thread there
ahh
i'll have a think about that, it doesn't seem like it's optimum
What I can see happening is someone creating a thread in #flixel and then someone else creating a thread in the #showcase channel
split discussions :/
Btw any reason why [showcase] is limited to #1019922106370232360 exclusively? What if I post something worth showcasing in #heaps , for example?
it's not particularly limited by intention
the intention was to just cross post showcases from the projects area, which makes sense because you can directly link to an organised location to chat about the post
I was under the impression that you couldnt make threads in the showcase channel
you will be able to make threads in the showcase channel
you just wont be able to chat in the "parent" showcase channel
Oh
doing a [showcase] tag outside of the showcase channel will likely just lead to instances where there's multiple places to talk about the same thing which doesn't seem like good design
Thats why i assumed the discussion would happen in the linked channel/thread
And showcase is just the showcase list
I still kinda think that limitation is fairly arbitrary. But you do you.
will see, the limitation is to just not segregate things. If people are chatting in #heaps but someone who's scrolling through #showcase may read a thread that's in the #showcase channel but may not go to another channel to read as you'll likely get content that you wouldn't expect to see
So they want to discuss it or read up, but dont want to click the link?
it's a ui/ux psychology thing, like if you make things a few more clicks away or increase the "journey" to get to something it creates "friction"
Look, I still consider that whole forums thing was a massive mistake on the grounds that you wanted place to discuss projects, but for some reason decided to conflate it with showcase channel in the process for no good reason.
I think you misunderstand my goals, but it's cool, we'll see how things evolve and we can discuss improvements here over time
Same number of clicks to enter a thread underneath the post
One downside to my approach, is that i fear people will showcase a post. Make a thread for it. And people who click through may type in the channel rather than than the thread
if the thread is within the #showcase channel, yes. If it's in a #lime channel I can't auto link to the thread, I have to auto link to a message and then someone has to then go find the link
it's more awkward
why cant you link to the thread?
Go find the link
I thought we were including the link in the crosspost
and then if someone presses "back" on their phone or something, rather than going back to showcases they go back to the lime channel
#956928971927339018 and #1019926282802298880 work fine, no?
for showcase posts made outside of projects
I mean i just dont see this as an issue
Discords back button use is pretty terrible in threads, but if people eant to talk about a showcase they will, despite what they are clicking, imo
Linux Nerds best thread
Again, iirc bots can do proper <a href="...">custom text</a> compared to regular users. Meaning you still can make ugly-ass link to specific message into something usable. And if someone started a discussion thread afterwards - it's in the chat log.
Yeah
But i can't link to the thread, i have to link to a message - 1 click and then someone has to "check" if a thread even exists, which it might or not.
I still prefer, personally
What do you mean tho? If message spawned a post-thread, then it's literally attached to the message:
Plus if user is interested enough to know if there was a discussion or not - one click to check is negligible.
Id rather have the old style, anything goes showcase channel, rather than ONLY* allowing threads in the new channel. And i prefer discussions entirely in external places like a forum post or other channels/threads
As I understood you still would be able to post in showcase channel as usual with slowmode, but you first would need to get posting permission via /showcase command, no?
I like this best
Okay. So here's the two scenarios.
Scenario 1: (Current)
Everything is organised into #showcase. As you scroll through the showcase channel, it is clear whether a post has more discussion or not as the user can see immediately that a thread exists without needing to go anywhere else.
Scenario 2: You're allowed to trigger [showcase] outside of #1019922106370232360
This becomes awkward. I can't auto create a thread for people because of the title issue, so I have to link to a message. So in the showcase channel I link to a message, fair enough.. That part works. But here's the issues, a user can't know from that message link whether a thread exists or not. They have to go manually check it. If there's no thread, they have to then go back to the showcase channel.
Cant you add a thread title field to the command prompt?
They have to go manually check it. If there's no thread, they have to then go back to the showcase channel.
Yes, and? I don't see it as an issue.
The one I replied to?
It's inconvenient/inefficient. Like how you find discord over padding messages is annoying as it's wasting space, this issue is similar
I feel the only time a thread in showcase is needed is if they use the command to make a new post without a link
maybe windows hiding settings under many categories is a more appropriate example
When crossposting the original message is the start of the discussion
Here's my thought process:
- I browser
- I see neat thing that I want to see what people talk about it
- I check links
- If it has a #1019922106370232360 thread link - click it. (Actually, I probably would want to click a link that links to original showcase message)
- If not - click the link, check messages and if there's any post-threads or not.
- Go back.
Yeah
Yes, it's less convenient, but not as bad as no way to post outside #1019922106370232360 or directly into #showcase .
I find it pretty convenient
bruh, that's literally normal
like, you can't post in #flixel without going to the flixel channel ๐
Plus you run into the issue of opening up to places to exchange the same thing
Also, if you really want to auto-create post-threads and need a title - just use whatever the first line of the post is. 
(Well, first non-link line)
Are titles supposed to be unique?
i think unique to the channel, yeah
ideally you would describe what your project is, no?
#casual-chat message
if (not in #projects && message.split("\n")[0].removeLinks().blank()) rejectShowcase() 
I.e. if it's just a link - don't trigger showcase and just tell the user "hey, not gonna do squat without title"
what about the multi thread issue?
someone creates a thread in #showcase and someone else creates a thread in #ceramic
The only way this works well imo is if a thread can be directly inferred
With cross-posting feature [showcase] already creates a problem that original poster won't get a notification if someone would create a post-thread inside #showcase . Even if they have link to #1019922106370232360 thread.
It doesn't create an issue with #1019922106370232360 because the norm is all cross posts will have a place to talk implicitly
Someone, someday, will go and create a post-thread like that.
I'm sure they will, but, that's an edge case ๐
I did not actually account for that so maybe i'll make the cross post message clearer that there's a place to chat already
Same goes for your insistence of always having a thread for every single showcase post.
It's not always needed.
that's not going to happen
I meant that showcase post have to have a thread attached to it, either forum one or manually created.
it doesn't require that
But your reason for not allowing [showcase] outside of #1019922106370232360 is that:
A) Can't properly auto-create post-thread (it shouldn't auto-create anything)
B) Can't be sure where the discussion is (it's in the place where original post was created, because original poster won't get notification of post-thread created on a cross-post message)
right, it doesn't actually add anything to the people consuming the content. It just makes the poster's life a tiny bit easier
If you can give me a fair reason why it makes the consumers life easier, then I can maybe understand why there's value to it
cause from what I gather, it just makes things more confusing (for the consumer/user)
But HOW it makes it confusing ffs. With simple-ass format like:
Showcase in #heaps (Message: <link>)
<copy of showcase post>
That's it. User can click the message link, see if it has any discussion, go back. Compared to:
Showcase in #1019926282802298880 (Message: <link>)
<copy of showcase post>
you didn't answer my question though, you don't think it's confusing to do that - i got that. But can you tell me how this setup actually benefits anyone other than the poster? And even then the active solution doesn't change any current behaviours that they're already used to. I can give reasons for that with the current solution.
I can't see how allowing it cross channel benefits others
i dont see how it doesnt benefit to do that
It adds benefit to the poster and does not create any negatives for consumer. That's it. In fact, it would make it better, because, let's say I posted something in #heaps. Then I just copy-pasted it to #showcase. Then people talk about it in #heaps and then someone else creates a post-thread in #showcase. Now there's 2 separate places where conversation is happening.
And users in place A would miss conversations part from place B and vice versa.
it's less cohesive, to put it simply. Lets sum up all the reasons why I think this isn't a good idea
- It's less cohesive
- You create the potential for double threads. (Bad for both the user and the poster)
- It objectively is more work, it's "simple", "I don't count this as work" work, but it is actually extra steps. And doing that across all channel categories, often. Is just gonna lead to people not clicking the link
- It's awkward when there's projects and channels,#haxeui exists but Ian also has a project, now there's 2 places. To cross post from. A user may forget they cross posted in one channel and do it again in the other
- Rather than a guaranteed #1019922106370232360 link that has a place to discuss things. It is now ambiguous. Lets say you have 6 cross posts in a row in #1019922106370232360 and all of them don't have a #showcase thread. You want to see what people are saying about each of the projects. You have to open link, check if thread exists, if it does, click again - read. If it doesn't you have to then browse through some help requests as replies to the showcase link is interspersed through out. And repeat that 6 times.
- It encourages bot cross posting which isn't particularly great in itself
this is objectively worse for the community
You should just do what you are thinking @civic sky and deal with feedback of the thing once it's out there.
Yeah, that's what I was thinking ๐
Cause I think there's been so much discussion about it now that it has become a bit unclear of what i'm actually gonna do or how it's going to work
- You create the potential for double threads. (Bad for both the user and the poster)
Except that's exactly what's going to happen with or without. Because if it doesn't allow me to auto cross-post, I would do exactly as I described:
- Post in #heaps
- Copy-paste it to #showcase
Because not everyone have #heaps unmuted and nont everyone have #showcase unmuted, and cross-posting nets me higher visibility.
More people look at #showcase than they do heaps
#showcase is the most read channel of the server
But at the same time #heaps have people who are more insterested in Heaps and more likely to discuss particulars.
which is why there's the option for threads in #showcase
The exact same freedom of discussion, will be encouraged in those threads. At least that's what I want out of this
Exceeept people would rather talk about it it right in the channel related to Heaps than go to some thread nobody even created.
I dunno, people talked about particulars in the old#showcase threads. And before the threads people would always talk about particulars before I started encouraging the channel to be on topic. So I don't think this change will actually negatively effect that
You do you 
why dont we https://tryitands.ee
I think this is an arbitrary limitation with not much benefit.
I still say cross posts shouldn't have a thread in #showcase and standalone posts should have a thread title field in the prompt
bruh, this limitation is not a limitation. It's the default user experience of discord ๐
I also assume 90% of people will make a forum post and then crosspost it
so the 'default user experience' has no limitations?
Default UX of Discord? I.e. "pretty bad". Gotcha. 
Okay, so this is what I want to encourage. Auto threads won't be happening, that's a bit OTT as per Ian's suggestion yesterday. Threads will be on a user creating basis
OTT?
over the top
if someone want to create a thread on a showcase post, they can. Otherwise the default is no thread
because discord comes with a /thread command by default so i'm not sure what benefit it would be to make a /thread command for #showcase unless it added to the experience
I can't control that really
It's a true/false permission on the channel
what thread command
so either anyone can make a thread on any post, or no one including bots can?
do it in a non forum channel
Detect if someone creates a thread on bot-created cross-post and make bot post a warning message that it's better to go into related threads for discussion?
yeah, but, I'm gonna rework the cross post message to say Discuss more at the showcase thread - #1021555085051957358 so it's clear
yeah that makes sense
we can always make it clear there is already a discussion in a crosspost, and if people make another we can just let them know. i doubt it will happen often, tho
well, the default experience i have in mind essentially means that issue doesn't exist
it's by default no/minimal risk
what default experience
project crossposts
i don't see how the problem doesn't exist
because there's implicitly somewhere clear and active to talk about the project
that doesn't exist with external channel crossposts
it requires investigation to figure out whether it exists or not
sometimes they click - no discussion at all
sometimes they click - a thread
sometimes they click - some discussion scattered between the general chat of the channel
current solution:
No thread - no discussion ๐
forum - click -> place exists immediately to chat about the thing ๐
things are immediately inferable from simply just scrolling the channel
or at least, moreso
Okay, everything is live now
feel free to type /showcase to get posting permission in #showcase
type [showcase] at the start of your post in a forum thread to auto cross post to #showcase
hmm take that back. didn't test something x)
Urgh, I may need to figure out some way to allow users to edit their crossposted message ๐
Nah
just to chip in. really enjoying the new formats. appreciate how it all seems to work - i think the tradeoff of loss-of-super-easy-scrolling is more than made up for by stronger discussions potential
probably best, cause, I have no idea how I would do that without tracking messages ๐
lol
i pinned my explanation post, just for the time being and the bot deleted the "this message has been pinned" post ๐
... so after all my whingeing, complaining and the "the sky is falling"... @civic sky 's new showcase is basically exactly as the old one, with a bunch of useful enhancements and tweaks... ... ill consider myself wrong, and will attempt to STFU in the future! ๐คฃ
Which of the two formats do you prefer? Do you have an idea for another?
personally i find it a bit awkward how the name of the user is all the way at the bottom
Could you use Webhooks instead?
This would allow the name and profile picture to match the submitter
can look into that
That is what the matrix bridge does
I'll see how to do that after i've eaten!
i always thought webhook's required an external server
didn't think it could be used across the same server
Add an extra link to specifically that message.
Because opening thread would just put you to last read position, while users also may want to jump to that message specifically.
hehe, this works. Looks waaay better ๐
lit
yea, just not live yet
๐
which is better? the bottom seems better to me but it's not as intuitive as having the discuss message on the bottom
but I can't have this at the absolute bottom due to the way discord handles embeds
I think it should be on the bottom
to me the top seems preferrable - it tells you, albeit in summary, what it is that you might discuss elsewhere which seems to help context
yeah, that's my issue. I think if it should be anywhere, it should be at the bottom but I can't have that due to technical limitation, so top seems next best place
cause otherwise the discuss message is kind of "in the middle" of the content
Maybe make the discuss more as an embed?
embed's in this format looks a bit ugly imo
ah k
Hmm, it isn't that bad
not that bad, but is worse. At least to me
The wording is kinda strange
Got another suggestion?
that's better than what I have at least, will update
yeah looks ok to me
@civic sky Didn't have anything to showcase yet, but have to say current result looks great ๐
hehe, i really like how things have turned out as well
I didn't think we'd still have a use for a "casual" project general in #1019922106370232360 once #showcase was out but I guess we totally do ๐
a lot of people just don't know about cross posting
lol, i forgot to put that in the /help thing as well
I think I can do something about that
If one of us has the time to commit to it it'd be cool to do like a monthly meetup where we just go over haxe roundups and stuff, would be a good place to remind people about that kind of thing
i would def be down for something like that fuk yea
VC or IRL? Iโm down for the Haxe woods retreat in dead of winter where we learn which one of us is man and which one of us is animal when faced with depleting resources in total isolation
But VC would be fun too
Less axes that way
yeah prob vc bc renting out the space for a murder mystery is always a big pain
i'm happy to support anyone who wants to organise these things
but the most i can probs do is setup an event and maybe participate if it falls on a day i'm not working ๐
If you want I could figure it out I suppose
Google forms or doodle poll or whatever
The Roundup Roundup
My only request is someone put a lil cowboy hat on the Haxe logo
And we make it an emoji
hahaha I really love The Roundup Roundup
No way else to proceed if this does not happen
Does anyone know the Haxe font
@civic sky @copper spindle these are the direct consequences of your actions
||yeehaw||
Now you have to theme it like that bounty hunter show from cowboy bebop
that's what I had in mind lol
that and woody's roundup
yeehawx
wasn't this a thing for a while?
i remember doing this and spending the whole time talking about the definition of "bi-weekly"
Which of course means doing something twice a week right?
Hahhaha
on a note completely unrelated to the concept of bi-weekly, lets meet every other week
How about daily every other week
on days that end with y

Every friday at 20:00 cest
or someone can record it and start a podcast
also I rarely have time on the weekends, but thats me
I would probably be willing to edit them and what not
Okay that's a good plan, one of us can record and send it to you @primal parcel and you can put it up after editing.
If we use the Discord stage feature I think it will record it?
I'd be interested if someone can't do this time, but could do weekend.
Discord stage might be really fitting for this
Okay wonderful
I would be unable to make it at that time unfortunately though
Thursday, 2:00PM EST for me
Works for you?
ill never be able to join...
oh that's not good ๐ฆ what time would work for you?
probably any evening which isnt on friday
Saturday at same time?
what timezone
Gmt + 3
Should be able to make it
Okay let's do that then
for what
Which leads me into my follow up idea
Turning #haxe into a #1019922106370232360 style channel
but with fixed threads
i dont think it needs to be a forum channel
there are still general haxe questions that wouldnt really fit into any more specific channel than just "haxe"
Yeah, it's an idea for the future I guess, just wanted to get the ideas out there
the projects channel would have a "general" thread within it
but actually writing it out, I don't think it's a good idea, at least for now
and having lua/hl/hxcpp be threads of #haxe makes more sense to me at least because those are still general haxe (as in not a specific framework) but still more focused
although less people would see them if they were threads anyways
also i feel like it would be more likely for someone to ask something in a "more incorrect" place if #haxe was a forum channel instead of a normal text channel
because i have seen plenty of people ask flixel questions in the #haxe channel, but they might move to like #tools instead because thats the first normal channel they see
people will ask questions in the wrong place, no matter how obvious the correct place is
ah this isn't about people asking questions in the wrong place
it's more about giving people a place and organising information
i don't really think the first issue is solvable
outside of occasional reminders
@civic sky regarding the FNF rule...
what about
- Whilst we absolutely love to see new programmers getting started, we DO NOT provide support for individual games. If your problem requires specific knowledge of games like FNF (or others) you'll have better luck in their server.
something along those lines, this might even be too welcoming
The fear is that the old rule makes people hide the fact that thier general haxe or flixel question is in violation of this rule
current* rule:
- Whilst we absolutely love to see new programmers getting started, we DO NOT provide support for individual games. If you are looking for support for games like FNF (or others) you should go to their server.
It's not really hiding it's common to make questions non specific to your exact game.
or maybe just, Don't ask questions that assume we know a specific game's codebase already
younger, newer programmers/modders often do not know what is specific to their game
they don't always know whether it's a game util, flixel util, or haxe util
and tend to assume haxe
classic example is Paths.image("path/to/image")
Sure, then it's useful to show them how they can figure out what comes from Flixel vs Funkin, i.e How do you set an FlxSprite's alpha vs BoyFriendSprite etc.
this conversation started because FNF people are often overly cryptic about what they're trying to do, helping them is like pulling teeth because they think if they say "it's for a FNF mod" we'll perma ban them
so maybe we should just append "This doesn't mean FNF questions are off-limits, it just means if your question requires extended knowledge of the FNF codebase you should ask elsewhere"
*puts down banhammer* Wait, we wont? 
lol
maybe something like you said "make your questions non-specific to your game"
@faint flicker is NotBilly here?
I think that's a good system
I assume he'll read when he gets here
but yeah, so long as they're not afraid to say the word FNF, but we have the right to say "thats too FNF specific, ask in an FNF server"
Phrasing is a bit dodgy. Since you ask a question, it's inherently specific to the game you're working on.
"If you're not sure if you're question is specific to your game, framework or haxe, ask and we'll let you know"
I say because we started the Haxe round up round up
oh
usually Billy announces in #announcements , but he's not here
he posted in #flixel a minute ago
- When requesting help, you should phrase your question as if we don't know anything about the project you're working on (it may shock you, but most of us here don't know anything about FNF). We can't offer specific project help, but, we can help with programming problems. Condense your problem down as much as you can.
