My instance is up! about araa-search HOT 36 CLOSED

you might need 2gb ram because with the system arra uses 1rb ram leaving 1gb free

#74 (comment)
#74 (comment)

from araa-search.

nice!

from araa-search.

btw i will be renaming tailsx soon #67 let me know what you think.

from araa-search.

thanks

from araa-search.

@Extravi Will do! Also, is there some sort of logo for the frontend so I can add it to my homepage?

from araa-search.

i will update the code with once done

from araa-search.

it adds a few things like this

from araa-search.

from araa-search.

I also replaced the background, let me know if you like it. Thanks.

from araa-search.

would you like me to add your instance to the instances list?

from araa-search.

would you like me to add your instance to the instances list?

Yes, thank you! I will change the subdomain to the new name after you decide on one. I personally use Darkreader so I usually don't see the wallpaper, but the blur gives it an elegant look.

from araa-search.

thanks

from araa-search.

i think i will rename to Araa from TailsX

from araa-search.

@Extravi Before you add my instance, the video section on it doesn't even load, it just hangs then times out, any idea why this happens?

from araa-search.

do it load at any point?

from araa-search.

or did it just take some time

from araa-search.

It times out and gives me 504

from araa-search.

did you change the Invidious instance in config?

from araa-search.

Yes, and I also white-listed it.

from araa-search.

i might not have api support on that instance or a working api

from araa-search.

https://yt.artemislena.eu/api/v1/search?q=cat

replace with the instance you want to use and test

from araa-search.

last update with the renaming has some bugs btw so i am working on fixing it in the next update with this (not complete)

trying my best to polish and clean up this project

from araa-search.

@Extravi, it's my Invidious API instance and it works just fine, so the API shouldn't be a problem?

from araa-search.

can I see what you have typed in the configuration file for the api

from araa-search.

also send me a copy of the error on the server

from araa-search.

you can email me privately if you want [email protected]

from araa-search.

alright bugs fixed from yesterdays update everything is all good now

from araa-search.

before updating your instance try it on any of my instances

from araa-search.

from araa-search.

@Extravi, bangs don't work unless you put them at the start of the query. Check this.

from araa-search.

I know about that I think that's how bangs should work idk

from araa-search.

I don't really use bangs so idk

from araa-search.

I don't really use bangs so idk

Realistically, most users will search with their privacy-respecting search engine and if they don't like the results they add a bang at the end of the query, so it makes sense to have it there.

from araa-search.

@Extravi, bangs don't work unless you put them at the start of the query. Check this.

@unstablemaple

I did that by design; I thought of shebangs you'd see in scripting, and how they always came first at the top of all scripts.

I could possibly try changing it to what you're suggesting, but I don't feel that there's enough of a need to do so right now.

I'm open to hear what anyone else may feel about this.

(Also, thanks for hosting Araa/TailsX/another name pending maybe!)

from araa-search.

@Extravi @TEMtheLEM I have modified the search() function to have it parse bangs as desired:

   if BANG in query:
            query += " " # Simple fix to avoid a possible error 500
                         # when parsing the query for the bangkey.
            bang_index = query.index(BANG)
            bangkey = query[bang_index+1:query.index(" ", bang_index)].lower()
            if SEARCH_BANGS.get(bangkey) is not None:
                query = query.lower().replace(BANG + bangkey, "").lstrip()
                return app.redirect(SEARCH_BANGS[bangkey].format(query))
            # Remove the space at the end of the query.
            # The space was added to fix a possible error 500 when
            # parsing the query for the bangkey.
            query = query[:len(query) - 1]  

That way, it will be able to detect the bangs wherever they are, in a query like search !g test !yt the function will redirect to google and will leave the YouTube bang as it is. My instance currently has the modified code for testing. If there are no bugs please inform me so I can make a pull request.

from araa-search.

does your instance use 1gb ram 2gb ram?

from araa-search.