6 ms·
I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex, and include that number on any web page that they
by tzs 6y ago
I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex, and include that number on any web page that they would like people searching for their project to find.
That way once I know that say PEP the PDF editor exists and find its 128-bit number (let's say that is 379dd864b16eaca3ce94c15a6bdfcc73), at least I can subsequently toss a +379dd864b16eaca3ce94c15a6bdfcc73 on my searches to effectively let the search engine know I want PEP the PDF editor results rather than PEP the python enhancement results or PEP the entertainment portal results or PEP that refreshing beverage company stock symbol.
"xxd -l 16 -p /dev/urandom" is a handy way to get a 128-bit random hex number. A UUID generator works, too, although they usually include some punctuation you will need to delete and you might have to lower case their output.
- MaxBarraclough 6y ago> I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex We already have something similar: URLs.
- wtetzner 6y agoExcept a URL only points to one resource. The idea here is that this identifier would exist on any resource related to PEP (maybe even in URLs).
- deleted 6y ago[deleted]
- fiddlerwoaroof 6y agoThat’s not a problem, you just add a meta or a link tag that points to “the” url for your project (maybe og:app-id Or a link with rel=“app”)
- notatoad 6y ago>Except a URL only points to one resource isn't that exactly what this is asking for though? A URL can by definition only point to one resource. So if you include that URL with every other reference to the project (in the app descriptions, blog posts about it, etc) then you always know you're talking about the same thing. It makes a lot more sense that any resource related to this PDF editor should include a link to "https://macpep.org https://macpep.org" instead of including some random 128 character string. Any resource related to python peps should include a link to "https://www.python.org/dev/peps/ https://www.python.org/dev/peps/" (which all PEPs do, by virtue of having a url that's a subdirectory of the PEP index URL)
- oh_sigh 6y agoMore in line with using "golang" since it is far easier to search for than just "go"
- nickthemagicman 6y agoYeah but urls and names might need to change due to marketing. A hash would uniquely id the project and let the marketing aspect be dynamic. Although if the actual project name, authors, and codebase changes is it even still the same project?
- drivingmenuts 6y agoThen maybe what really needs to happen is we burn all marketers in a pyre? So they quit fucking up things that ain’t fucked up?
- nickthemagicman 6y agoThere's a number of professions I'd like to add to that pyre please. ;)
- gumby 6y agotzs is proposing URNs rather than textual program names. A URL is unnecessarily specific (though I suppose you could anycast URL resolution)
- westurner 6y ago> RFC 4122 defines a Uniform Resource Name (URN) namespace for UUIDs. A UUID presented as a URN appears as follows:[1] > > urn:uuid:123e4567-e89b-12d3-a456-426655440000 https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_4_(random) https://en.wikipedia.org/wiki/Universally_unique_identifier#... Version 4 UUIDs have 122 random bits (out of 128 bits total). In Python: >>> import uuid >>> _id = uuid.uuid4() >>> _id.urn 'urn:uuid:4c466878-a81b-4f22-a112-c704655fa4ee' Whether search engines will consider a URL or a URN or a random str without dashes to be one searchable-for token is pretty ironic in terms of extracting relations between resources in a Linked Data hypergraph. >>> _id.hex '4c466878a81b4f22a112c704655fa4ee' The relation between a resource and a Thing with a URI/URN/URL can be expressed with https://schema.org/about https://schema.org/about . In JSON-LD ("JSONLD"): {"@context": "https://schema.org", "@type": "WebPage", "about": { "@type": "SoftwareApplication", "identifier": "urn:uuid:4c466878-a81b-4f22-a112-c704655fa4ee", "url": ["", ""], "name": [ "a schema.org/SoftwareApplication < CreativeWork < Thing", {"@value": "a rose by any other name", "@language": "en"}]}} Or with RDFa: <body vocab="https://schema.org/" typeof="WebPage"> <div property="about" typeof="SoftwareApplication"> <meta property="identifier" content="urn:uuid:4c466878-a81b-4f22-a112-c704655fa4ee"/> <a property="url" href=""></a> <a property="url" href=""></a> <span property="name">a schema.org/SoftwareApplication < CreativeWork < Thing</span> <span property="name" lang="en">a rose by any other name</span> </div> </body> Or with Microdata: <div itemtype="https://schema.org/WebPage" itemscope> <link itemprop="http://www.w3.org/ns/rdfa#usesVocabulary" href="https://schema.org/" /> <div itemprop="about" itemtype="https://schema.org/SoftwareApplication" itemscope> <a itemprop="url" href=""></a> <a itemprop="url" href=""></a> <meta itemprop="identifier" content="urn:uuid:4c466878-a81b-4f22-a112-c704655fa4ee" /> <meta itemprop="name" content="a schema.org/SoftwareApplication < CreativeWork < Thing"/> <meta itemprop="name" content="a rose by any other name" lang="en"/> </div> </div>
- suprfsat 6y agoInstead of trolling HN you could contribute to Wikidata.
- nickthemagicman 6y ago8 bit ascii could work. 8^256 is a huge number.
- thechao 6y agoI can’t even this math.
- nickthemagicman 6y agoI worded wrong.
- colejohnson66 6y agoA 256 bit number is 2^256 possible combinations. 8^256 is the same as (2^3)^256 (or 2^768)
- nickthemagicman 6y agoEr yeah. Derp. 8 character ascii not 8 bit. It's early. That's 8 bits ^ 8. Or 256 ^ 8. and easily able to be represented searching online with 8 characters.
- SiVal 6y agoDon't get discouraged, but you might still have a bug or two to work out with your new and never-before-tried "256^8 and easily able to be represented searching online with 8 characters" design. For your beta test, here are some of the unique 8-char identifiers you might want to try searching for: `unique `, ` unique `, ` unique`, `Unique `, `u^Hunique`, `un^Hnique`, `uniq^H^H^H^H`, ` . . . .`, `. . . . `, `uniqueESCESC`, `BELBELBELBELBELBELBELBEL`, ...
- nickthemagicman 6y agoLol, thanks for your totally non sarcastic assistance. It needs some fleshing out.
- Fnoord 6y agoIf you want something like that with binaries, Nix(OS) might be for you.
- romanoderoma 6y agoThat's more or less what Ted Nelson envisioned in Xanadu and that's why he usually says that modern cut and paste has nothing to do with the real cut and paste and he consider it “a crime against humanity.” Even though he's friend with Larry Tesler, the man responsible for our modern use of cut and paste Links should bring back to the original source not point to some random text, with no context, that needs to be indexed
- vorpalhex 6y agoThat's actually a pretty solid idea. A meta tag for topics. Only issue would be handling inevitable "SEO-ified" abusers of it.
- kps 6y agoSimple solution: 379dd864b16eaca3ce94c15a6bdfcc73™
- mulmen 6y agoNot sure I follow. Are you saying that by trademarking the fingerprint you can prevent SEO abuse? The problem with any SEO mitigation is that the 128 bit string is intended for SEO. If you make a cool new thing then I blog about it I want to use your 128 bit string and you want me to use it too! So how do you prevent someone else from putting it on a linkfarm? I don't think trademark helps there.
- justaguy88 6y agoIf your page has 100 of these 128 bit strings in them then it's even clearer that its a link farm page that can be downranked
- deleted 6y ago[deleted]
- tgbugs 6y agoThis solves the namespacing problem and allows creators and consumers to use different names if they want. Searching based on the creator's original name for a project becomes a mess because there will be a very large number of HelloWorld applications out there. Interestingly enough the google web store sort of already does this. The issue that comes up fairly quickly though is how to deal with the relationships between different packaged and published versions of what is nomalinally the same code base, or even forks/branches of the same code base. Maintaining a verifiable and discoverable chain for published artifacts without completely confusing users or exposing them to various malicious attacks (change a single byte in the middle of that random string and you have a nice off-by-one attack). Lots of infrastructure would be required to pull this off, but it would be great if it could be built.
- kalium-xyz 6y agoI too dream of content addressable web.
- justaguy88 6y agohttps://docs.ipfs.io/how-to/websites-on-ipfs/single-page-website/ https://docs.ipfs.io/how-to/websites-on-ipfs/single-page-web...
- devenblake 6y agoJust added one to a project of mine[0] (just a YouTube browser using the RSS thing YouTube does). Hope it catches on! [0] - https://github.com/devenblake/ytfeed.py https://github.com/devenblake/ytfeed.py
- sbr464 6y agoThat's actually a pretty good idea. Kind of like an official @mention/#hashtag for an exact topic, if somehow wasn't abused by people, would definitely improve related search results. Navigating user intent algorithms is getting more difficult. Does schema.org etc support ids beyond keywords/categories? I guess the id could just be a keyword. Maybe a public registry where you claim an id for a topic, similar to claiming a yelp page or an ISBN number. Then anyone posting related content includes that id. Popular topics could be grouped. You could generate memorable ids for most known topics/products/etc, and people just utilize them organically, robots could apply them automatically over time also. It's especially bad for words with many definitions, like "bridge repair", could mean a dental bridge, guitar bridge, or a bridge over a lake.
- gjvnq 6y agoI kind of do this in blog. Each page is assigned an UUID.