Re: introducing deken trends
IOhannes m zmoelnig via Pd-list <[email protected]>
| Newsgroups | gmane.comp.multimedia.puredata.general |
|---|---|
| Message-ID | <[email protected]> |
>> esp. what data is there that is useful for an external developer (as >> opposed to the maintainers of the deken search) > > > Why are you not interested in data that is useful for the maintainers > of the deken search? simple: because that is practically only me (kudos to you of course, but in reality there have not been many contributions by others in the last decade) and I do not need to *publish* statistics about the queries, because i can access them just so. obviously i haven't done that myself, so this entire thread is a good motivation :-) but if I were to invest time to publish such data, I would like to see benefits for other people that they can act on (short of nagging other people). On 8/28/25 10:18, Christof Ressi wrote: >> Clearly people are searching for 'freeverb' - why is it not returning >> the freeverb external? The intent of the user is obvious. How can the >> tool be updated to better serve the user? > > Yes. I think this is a good argument for using wildcard search by > default. We can add a checkbox for people who only want exact matches. indeed. i do want people to be able to do exact matches (with wildcards and what not). but allowing the user to check whether they want to do a fuzzy search or an exact search sounds like the best idea. should a fuzzy search also allow for soundex? (that's going to be more tricky. there's a tcl module in the tcllib, but we don't ship this with Pd; if we want to do the soundex matching on the server, we need to signal that in the query... it's easy, but right now the query is even trivial :-)) gfdmsr IOhannes --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/TUASRIZEUJ2PT6AJNIYMMZSBHRI7OV2C/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmiwJOgFAwAAAAAACgkQtlAZxH96NvjI hw/9Exz/1P0b+kQ4NdP1KW5pEwMVbCBX2Un2pQQ7Y/FMlbzWzxp2sxPTh/T3eV6fTk99ihJn5LcD q+YDi+md9PN1nkBQALLfhFdM3kx9U0Mdoq5bQRV0TrIznSRUOBgt0Doaf6Yqhau3TLpGH/WCPaDC XaH+Pk+SVXI4O3zq88akUtRBG78sJpwJbkYe20jKxLh5WBn6mnT0yD06XHwYlhkDLat/yA9+vWwp KXABVXZA/qGAge96JtAMF1fYb653XzROmFh3I0B+0V6QKxZQTvswR2MWaXQtyb1Vg7c/7U4Xl/Nu +t1cHqcShAhiQ3pkHCyNZDL3pYJfA7JxQTeClG09NpTmeG7vPhmLbo78CLt4ucr0kPyOV48YrytR qOnUTiyol3l0Cr0aTvW73VA1WjE5R+/DCKmQB76LZKPsBH3BXwIihTA2ajExQaZSJRq9mNw9dXGZ Li4E9o6cCJvCQA4iVn2ZYmc0O4NzRASJHLqctMZGPO6n+BfzioGr3ai55EvrQVl8oNdcRSoc7ok1 UDtqJbA/bZSbbtZeoettNEHCmfbl0SYC93dgbuYX75Cp9iv4Dfm1foamMdN/iGdVamoYiK3T+md4 32+gI/wu+AzQ7/blVafPUUGP93RQaJaZaAhQPl1jBdIrlHkYAdx9vc06N7Fl4heGPDK/G8FVue3Q 8UA= =pyn7 -----END PGP SIGNATURE-----