Seeing in the instructions about how to do a post search with tags, i.e. https://e621.net/help/cheatsheet

To do a conjunction of two or more tags, you enter them in the field...

Search:

cat dog bird

cat dog bird
Generated URL:

https://e621.net/posts?tags=cat+dog+bird

If we consider (not from an IT point of view, but mmmm... matehmatial), each tag could be thought as "set" of post, few or many.

The term

/post?tag=t1+t2+t3...

would be then, the intersection of those sets.

According to the instructions, you could generate also the "union" of those sets with the operator "~".

Search:

~cat ~dog ~bird

~cat ~dog ~bird
Generated URL:

https://e621.net/posts?tags=%7Ecat+%7Edog+%7Ebird

Evidently, "%7E" stands for the character "~".

You could also make searches, by the favorites of some user:

Search:

fav:MexicanFurry

fav:MexicanFurry
Generated URL:

https://e621.net/posts?tags=fav%3AMexicanFurry

Note that in the url, "fav:MexicanFurry" is treated as a tag...

So far, so good...

--------------------------------------

Not to make this thing excessively long, what I want is to generate a UNION of two favorites of users.

So I enter in the Search field:

Search:

~fav:MexicanFurry ~fav:Sirus2b

(This is analogous to the second example above.

URL Generated:

https://e621.net/posts?tags=%7Efav%3AMexicanFurry+%7Efav%3ASirus2b

But what is displayed here, is:

Nobody here but us chickens!

Go back

I don't know if...

(a.) I doing something wrong...

(b.) The system cannot process this kind of more complex request.

I don't know if someone here could help me.

PS.

Why I want to do this, you may ask?

The reason because this is important to me, is because I want to generate searches of post of users that have similar tastes to me.

That will be, so to say it, the kind of "tags" with which I could find the stuff more suitable to me in E6.

Then at the and, I could also add a metatag "order:score", just as "the cherry", so to speak.

metatags are not treated as normal tags. There is currently a limit of one of each metatag per search based on how the system builds the search internally. Some(most) metatags have a negated version that can be used distinctly from the inclusive version. The concept of a union against metatags doesn't exist.

kiranoot said:
metatags are not treated as normal tags. There is currently a limit of one of each metatag per search based on how the system builds the search internally. Some(most) metatags have a negated version that can be used distinctly from the inclusive version. The concept of a union against metatags doesn't exist.

Oh.. I see.

Thank you @KiraNoot.

As consolation, I see, artists at treated like "tag", it is valid to do searches of multiple artists, and order by score...

Search:

~truegrave9 ~hoot_(artist) order:score

Generated URL:

https://e621.net/posts/632729?q=~truegrave9+~hoot_%28artist%29+order%3Ascore

Result: ~truegrave9 ~hoot_(artist) order:score

... I will continue to explore that, and other ways.

Thanks again.

mexicanfurry said:
As consolation, I see, artists at treated like "tag", it is valid to do searches of multiple artists, and order by score...

They aren't "treated like" tags, they are tags. Anything that actually shows up on the lefthand list of tags is a fullblooded tag. Even the meta, lore, and invalid categories.

furrin_gok said:
They aren't "treated like" tags, they are tags. Anything that actually shows up on the lefthand list of tags is a fullblooded tag. Even the meta, lore, and invalid categories.

Hello, @furrin_gok. It is good to know it.

I continue with analizing ways to find users with similar tastes to I. So what I just do, is...

(a.) Select a number of posts that I really like (ideally, from different artists, now that I think about it).

(b.) Copy the users those these images are favorites to them, into a "small" database (in this test, it was in the order of 800+ records).

(c.) Run a "descriptives" procedure on a statistical package, to find the frequencies these users repeat...

So my first shot with this aproach, gave me these "significant" users...

Usuario					
		Frecuencia	Porcentaje	Porcentaje válido	Porcentaje acumulado
Válido	Aranak	4	.5	.5	.5
	DreitTheDragon	4	.5	.5	1.0
	GaitingGator	3	.4	.4	1.4
	PhotoDragonBird	3	.4	.4	1.7
	Qibble	3	.4	.4	2.1

Now, to see what we have... (crossing fingers)...

fav:Aranak
fav:DreitTheDragon
fav:GaitingGator
fav:PhotoDragonBird
fav:Qibble

And the result is....

-------------------------------------------------------

Mmmm.... not so bad as the first shot, BUT I see a problem... this users have MASSIVE number of favorites (like some more than hundred of pages as favorites)... but I could control that on other tests.

A simple but promising method, so far...

=).

mexicanfurry said:

Usuario					
		Frecuencia	Porcentaje	Porcentaje válido	Porcentaje acumulado
Válido	Aranak	4	.5	.5	.5
	DreitTheDragon	4	.5	.5	1.0
	GaitingGator	3	.4	.4	1.4
	PhotoDragonBird	3	.4	.4	1.7
	Qibble	3	.4	.4	2.1

Running a [table] code would probably work better, as it'll avoid column misplacement.

furrin_gok said:
Running a [table] code would probably work better, as it'll avoid column misplacement.

Wow... looks super-cool.

=).

mexicanfurry said:
Wow... looks super-cool.

=).

Pretty messy if you look at it under the reply option though.

I also like to continue to learn more about options for doing searches in this site... for example, with this simple instruction I could check the 4 comics that I am following right now in E6...

comic ~BitterStrawberries ~anti_dev ~sefeiren ~gabshiba

But it could be applied more extensively.

mexicanfurry said:
I also like to continue to learn more about options for doing searches in this site... for example, with this simple instruction I could check the 4 comics that I am following right now in E6...

comic ~BitterStrawberries ~anti_dev ~sefeiren ~gabshiba

But it could be applied more extensively.

Sadly, since metatags are one-or-none, you can't run fuzzies on pool:12478 type tags, which directly search for that comic.
Those metatags do at least work for throwing posts into pools, even if you enter them on the upload page! You can enter something like child:1234 to forcefully reassign post #1234's parent to your new upload, or pool:12478 to make it so it shows up in the pool at the same time it shows up on the post list.