## pagination – What is the right method to show the user progress of a dynamic questionnaire with a variable number of questions?

What are the best practices for showing the length and the stage of a questionnaire, where the length of the questionnaire changes and branches dynamically depending on the responses? I will create a quiz in which the user will see one question at a time. I want users to know how much time they have and how much they have their place in the process, but without misleading them. I do not want them to think that a single questionnaire could have 50 questions to answer. But to give a tangible figure, they might have to answer 7 questions or 15 questions could be asked based on their answers.

## HawkHost questions

I ordered hawkhost and paid instantly on DATE NOVEMBER-09-2019 and until now, my accommodation is still waiting, I do not know what kind … | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1787047&goto=newpost

## [ Politics ] Open question: Why are the Conservatives still asking silly questions?

[Politics] Open question: Why are the Conservatives still asking silly questions?

## Questions about Jrpg NPC events (Unity C #)

So, I try to understand something. I've set up my basic quest system for my RPG style game.

Right now, I'm looking at NPC events and triggers that, in my opinion, have two distinct styles

1. The classic floor panel trigger that rpg maker uses or

2. have a listener for the quest / active event

My questions are therefore the best way to activate the event and what is the best way to define it? For example, defining movement patterns, etc. Or should I use scriptable objects?

## malware – Some questions about Red Hat Linux and a case study

As part of a course I'm doing, he presents a case study. I am a bit stuck and I do not know where to find other information. If anyone could point me in the direction, I would appreciate it.

In this case study, a network using Red Hat Linux mail and file servers, a proprietary SIEM server, and multiple Windows 2012 servers were attacked.
It is noted that:

• VMProtectss & NetCat have been installed
• There was streaming traffic to a URL with the end port 9091
• Ports 9091 and 9092 have been opened and only one packet has been sent to a URL ending with 9092.
• Linux servers have not been updated recently and have not been injected.
• No data changes took place

From what I can understand up to now, VMProtectss is a Windows-based cryptominer and NetCat could be a C2 element that establishes a TCP / UDP connection.
I think the only package at 9092 was a confirmation that NetCat was installed and opened the connection for an extended intrusion.
I do not know what streaming traffic to 9091 could be.

The questions they ask are:

• What could happen on Linux servers
• What was the impact on the network and was there a data breach?
• what methods would be taken to remove the malicious code

I do not expect anyone to answer these questions for me, but rather to know where I can go to find more information.

## Questions on the website Dedicated servers for file sharing

I have 2 questions about data centers:

1 – There is also M … | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1786889&goto=newpost

## Basic shellcode questions – Information Security Stack Exchange

Is the hexadecimal code at the top of this source file the same as the assembly at the bottom because they do the same thing?

How can I convert the assembly to hex as in this source code file? I often see that it is used in payloads. I understand that this is done to preserve space, bypassing IDS, among other reasons.

Sample Shell Storm website file

## Online test with 80 best practice questions

When using a long form, you must use different methods to provide a good user experience. For very long forms with many questions, here are some things you can try:

1. Group your questions into sections

Sort your questions into manageable pieces. When you have a long form, you probably ask about many different topics. Your goal is to identify what these themes are and to classify your questions into easy-to-understand sections.
Once you have sections, it means that you can more clearly identify where a person is filling out the form. Completing the sections also allows small rewards in a long form filling process and probably not fun.

2. Make the place visible

An essential difference between short forms and long forms is that they require a different user experience. Short forms are completed in minutes, long forms can take hours – and people are expected to take breaks between sessions. For long forms, you must include a "You are here" function, which allows you to orient the person while allowing you to estimate the remaining time.

To make the place visible, you want to show where the person filling out the form is. You can use a percentage to complete icons, page numbers, breadcrumbs, loading bars, a stepper, and so on. There is no standard standard design, you will need to find a system that works with your form. In your case, I think this 2-level tree is correct.

3. Set expectations before the start

To prepare the person to start the form, give them as much context as possible. This will increase the completion rates for people who start the process.
The questions that an introduction might answer are:

• Why does the person complete this form?
• How long does it take to complete the form?
• What is the schedule for next steps?
• Do they need to prepare anything in advance (for example, having a driver's license at hand or preparing documents)?
• What happens to the information they provide?
• Who does it access, how will it be used, how does it meet the standards of confidentiality?
• Does filling out the form cost money?
• Do not surprise people in the end with the cost.

4. Save each question automatically

When the user completes a long form, some problems may occur. Login problems, session expiration, etc. Make sure every step of the user is saved and that he / she does not need to fill them again.

5. Do not make irrelevant questions

Hide only fuzzy questions around the focused question for very short forms. This design is good for a simple form, such as a survey, but not for long online forms with many questions.
When I fill out a form like this, I feel my heart beat harder because I'm trying to determine if I'm led to believe that the form is shorter than it actually is.

This style of opacity reduction for fuzzy questions is not accessible. People will inevitably feel compelled to read the blurry text before it is developed. However, since the colors of the text on the screen do not meet the standards of accessibility in terms of contrast, the readability is reduced, which poses a problem for the person who tries to read the fuzzy question if it can even see it first.

## visas – simple questions about travel history

You seem confused about the intention of the "Travel History" question.

This question is a factual statement of where you traveled. There is no minimum requirement for the number of countries in which you have traveled, nor any specific requirements for these countries. If you have not visited any country other than your home country, this is the correct answer to the question. If you have visited 10 other countries, you must list these 10 countries.

In general, the number or even the specific countries will not affect your request. However, there may be exceptions if the consulate staff think that your travel would prevent you from applying for a visa.

## limits – questions about the expected value of the rewards renewal process

N (t) is a renewal process with an inter-arrival period $$X_i (i geq1)$$. $$X_i$$ follows the uniform distribution (0,1). $$(R_i, X_i)$$ is a renewal reward process where $$R_i = e ^ {X_i}$$. You can get a reward $$R_i$$ at the time of renewal $$S_i$$. I'm trying to find $$E (R_ {N (t) +1})$$ when t goes to infinity.

What I think is $$E (R_ {N (t) +1}) = E (e ^ {X_ {N (t) + 1}}) = int_ {0} ^ {1} mathrm {e} ^ {x } , dx = e-1$$since X ~ U (0,1). But this is not correct. I wonder where I was wrong. Thank you!!