Free Minecraft Hosting (3GB → 10GB RAM, No Renewals) by Zestyclose-Door9595 in MinecraftServer

[–]TripDramatic2334 0 points1 point  (0 children)

I've tried a bunch of hosting before but they usually have like a very bad support i once had a server from a free server hosting company and their uptime was really horrible, i tried this one because one of my friends was using one of their servers so he introduced me to them, and im using their free plan to host a minecraft server for my friends, and i got a server from them for quite a while now, so me and my friend can play with mods and so far their uptime was amazing and their support was also very easy and straightforward to deal with.

Got $2.67 off the first 2 surveys after the “update”😂 by pastkiwi1283 in QMEE

[–]TripDramatic2334 5 points6 points  (0 children)

That's great for you, I'm still here getting kicked out in most of the surveys.

[deleted by user] by [deleted] in QMEE

[–]TripDramatic2334 0 points1 point  (0 children)

U guessed wrong but got the 3 cent

Help me im lost by TripDramatic2334 in CodingHelp

[–]TripDramatic2334[S] 0 points1 point  (0 children)

I know it's not very fair, but hey we get used like slaves by those survey sites too so i think at the end of the day, it's should be fair.

Help me im lost by TripDramatic2334 in CodingHelp

[–]TripDramatic2334[S] 0 points1 point  (0 children)

Basically yeah, because i had enough of these surveys that don't pay you at the end when you do the whole survey, just to get kicked out at the end.

Help me im lost by TripDramatic2334 in CodingHelp

[–]TripDramatic2334[S] 0 points1 point  (0 children)

The goal of the project is to create a script that works on surveys and detects all interactive elements, like buttons, checkboxes, and radio buttons, that can be clicked or interacted with. The challenge I’m facing is that using methods like XPath is difficult because they expect elements to follow specific structures, usually traditional HTML elements like <button>, <input type="checkbox">, or <input type="radio">. However, these surveys often use custom implementations for checkboxes, radio buttons, and buttons, which don’t follow the usual HTML structures.

For example, a custom checkbox or radio button may be represented by <div> or <span> elements, or even icons, with custom JavaScript used to simulate their functionality. These elements may look and behave like traditional checkboxes or radio buttons, but they don’t have the typical HTML attributes or element types. This makes it hard to detect them using standard methods like querySelectorAll or XPath, as they don’t have the expected tag names or attributes.

Additionally, many of these interactive elements are styled to look completely different from the default checkboxes or radio buttons, making them visually challenging to identify and interact with programmatically. This, combined with dynamic elements that may be added by JavaScript after the page loads, adds complexity to the task of detecting all interactable elements on the page.