Neat! I'm not a skin creator but I hope this new system will address a lot of the things I've seen creators express frustration about.

TOPIC | Dev Update: Pinglists & More
Neat! I'm not a skin creator but I hope this new system will address a lot of the things I've seen creators express frustration about.
Okay several thoughts:
Re: Pinglists-
There are several site communities that rely on pinglists to exist, such as GASP, G1 Collectors, ODCA, Dom Watch.... but most importantly, DOM teams. I really worry about the removal of mass pings without the ability to create public or at the VERY least, collaborative pinglists that can be owned by multiple users.
Dom pinglists cannot be held by a single user. Much how dom teams need to retire threads when folks step down from a role, we don't want to have to put the onus on users to re-subscribe to new pinglists whenever a dom lead steps down or steps up.
I'm also worried about pinglists like Swipp's Trades or Site Updates, both of which are collaborative and only work because anyone in our community can pitch in to ping folks when they see that a certain trade is up.
We're a widely responsible and respectful community, and while I do enjoy what site-supported pinglists offer, there is a serious need for collaborative, co-owned, and public pinglist features as well.
Re: Custom Skin Updates
Thank you so much for adding reprints, a site-supported % coverage tracker, and for all your continual hard work with the artist community. Skin queue is so much work!
I do think that the system that checks for line breaks will need to show the user submitting the png where the linebreak occurs. There is in particular a few spots on the Veil F base that always get people, and if you get the "2% Overflow" message but can't find the 2%, that's going to get frustrating really quickly.
Re: Coli PVP
So exciting! Can't wait for more opportunities to mess with stats and numbers in coli. c:
Re: Pinglists-
There are several site communities that rely on pinglists to exist, such as GASP, G1 Collectors, ODCA, Dom Watch.... but most importantly, DOM teams. I really worry about the removal of mass pings without the ability to create public or at the VERY least, collaborative pinglists that can be owned by multiple users.
Dom pinglists cannot be held by a single user. Much how dom teams need to retire threads when folks step down from a role, we don't want to have to put the onus on users to re-subscribe to new pinglists whenever a dom lead steps down or steps up.
I'm also worried about pinglists like Swipp's Trades or Site Updates, both of which are collaborative and only work because anyone in our community can pitch in to ping folks when they see that a certain trade is up.
We're a widely responsible and respectful community, and while I do enjoy what site-supported pinglists offer, there is a serious need for collaborative, co-owned, and public pinglist features as well.
Re: Custom Skin Updates
Thank you so much for adding reprints, a site-supported % coverage tracker, and for all your continual hard work with the artist community. Skin queue is so much work!
I do think that the system that checks for line breaks will need to show the user submitting the png where the linebreak occurs. There is in particular a few spots on the Veil F base that always get people, and if you get the "2% Overflow" message but can't find the 2%, that's going to get frustrating really quickly.
Re: Coli PVP
So exciting! Can't wait for more opportunities to mess with stats and numbers in coli. c:
Okay several thoughts:
Re: Pinglists-
There are several site communities that rely on pinglists to exist, such as GASP, G1 Collectors, ODCA, Dom Watch.... but most importantly, DOM teams. I really worry about the removal of mass pings without the ability to create public or at the VERY least, collaborative pinglists that can be owned by multiple users.
Dom pinglists cannot be held by a single user. Much how dom teams need to retire threads when folks step down from a role, we don't want to have to put the onus on users to re-subscribe to new pinglists whenever a dom lead steps down or steps up.
I'm also worried about pinglists like Swipp's Trades or Site Updates, both of which are collaborative and only work because anyone in our community can pitch in to ping folks when they see that a certain trade is up.
We're a widely responsible and respectful community, and while I do enjoy what site-supported pinglists offer, there is a serious need for collaborative, co-owned, and public pinglist features as well.
Re: Custom Skin Updates
Thank you so much for adding reprints, a site-supported % coverage tracker, and for all your continual hard work with the artist community. Skin queue is so much work!
I do think that the system that checks for line breaks will need to show the user submitting the png where the linebreak occurs. There is in particular a few spots on the Veil F base that always get people, and if you get the "2% Overflow" message but can't find the 2%, that's going to get frustrating really quickly.
Re: Coli PVP
So exciting! Can't wait for more opportunities to mess with stats and numbers in coli. c:
Re: Pinglists-
There are several site communities that rely on pinglists to exist, such as GASP, G1 Collectors, ODCA, Dom Watch.... but most importantly, DOM teams. I really worry about the removal of mass pings without the ability to create public or at the VERY least, collaborative pinglists that can be owned by multiple users.
Dom pinglists cannot be held by a single user. Much how dom teams need to retire threads when folks step down from a role, we don't want to have to put the onus on users to re-subscribe to new pinglists whenever a dom lead steps down or steps up.
I'm also worried about pinglists like Swipp's Trades or Site Updates, both of which are collaborative and only work because anyone in our community can pitch in to ping folks when they see that a certain trade is up.
We're a widely responsible and respectful community, and while I do enjoy what site-supported pinglists offer, there is a serious need for collaborative, co-owned, and public pinglist features as well.
Re: Custom Skin Updates
Thank you so much for adding reprints, a site-supported % coverage tracker, and for all your continual hard work with the artist community. Skin queue is so much work!
I do think that the system that checks for line breaks will need to show the user submitting the png where the linebreak occurs. There is in particular a few spots on the Veil F base that always get people, and if you get the "2% Overflow" message but can't find the 2%, that's going to get frustrating really quickly.
Re: Coli PVP
So exciting! Can't wait for more opportunities to mess with stats and numbers in coli. c:
YES
edit: yes, i'm also concerned about things like the swipp list, which are mass pings for specific circumstances (you don't want to ping everyone) or which become unwieldy for users to manage (you don't want the one person running the swipp list to be solely responsible).
i think voluntary sign-up for public pinglists is absolutely a necessary part of this transition and site QoL! obviously most pinglists (for a hatchery, art shop, etc) can and should be private, users should also have the option to sign up for publicly pingable lists like GASP, AEG1S, ODCA, swipp - with the full knowledge that those lists can be pinged by anyone.
edit: yes, i'm also concerned about things like the swipp list, which are mass pings for specific circumstances (you don't want to ping everyone) or which become unwieldy for users to manage (you don't want the one person running the swipp list to be solely responsible).
i think voluntary sign-up for public pinglists is absolutely a necessary part of this transition and site QoL! obviously most pinglists (for a hatchery, art shop, etc) can and should be private, users should also have the option to sign up for publicly pingable lists like GASP, AEG1S, ODCA, swipp - with the full knowledge that those lists can be pinged by anyone.
YES
edit: yes, i'm also concerned about things like the swipp list, which are mass pings for specific circumstances (you don't want to ping everyone) or which become unwieldy for users to manage (you don't want the one person running the swipp list to be solely responsible).
i think voluntary sign-up for public pinglists is absolutely a necessary part of this transition and site QoL! obviously most pinglists (for a hatchery, art shop, etc) can and should be private, users should also have the option to sign up for publicly pingable lists like GASP, AEG1S, ODCA, swipp - with the full knowledge that those lists can be pinged by anyone.
edit: yes, i'm also concerned about things like the swipp list, which are mass pings for specific circumstances (you don't want to ping everyone) or which become unwieldy for users to manage (you don't want the one person running the swipp list to be solely responsible).
i think voluntary sign-up for public pinglists is absolutely a necessary part of this transition and site QoL! obviously most pinglists (for a hatchery, art shop, etc) can and should be private, users should also have the option to sign up for publicly pingable lists like GASP, AEG1S, ODCA, swipp - with the full knowledge that those lists can be pinged by anyone.
This has one issue I can think of - are staff aware of GASP, the General Accent and Skin Pinglist? It's the single biggest way skin sellers get signups, and limiting users to 12 pings in a post will destroy it entirely.
EDIT: Also ODCA for low-digit ID sales pings etc
EDIT: Also ODCA for low-digit ID sales pings etc
The pinglist addition is super cool and useful!! Thank You!
The pinglist addition is super cool and useful!! Thank You!
//Wishlist//Oddjobs(Store)//Dragons for sale// I take random hiatuses during the summer. I am on more often than not though. So feel free to still be in contact and interact with me. |
![]() |
![]() |
![]() |