Создание Brute/Checker на HTTP запросах с помощью OpenBullet | ОБХОД CSRF-TOKEN | ЧАСТЬ 1 | РАЗВЕДКА
Ссылка:
Ссылка:
https://xss.pro/threads/125338/
[ИНИЦИАТИВА]: Покупаем статьи. Ищем авторов. Зарабатывай вместе c XSS
- Автор темы admin
- Дата начала
- Автор темы
- Добавить закладку
- #782
Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
https://xss.pro/threads/125329/
А мне кажется, что кроличья нора куда и куда и куда глубже, впрочем так и в желтых домах многим кажется
- Автор темы
- Добавить закладку
- #785
Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
SQL-DB как способ попробовать свои силы и понять принцип работы сокрытия данных.
https://xss.pro/threads/125474/
- Автор темы
- Добавить закладку
- #787
Тривиально, но полезно. Старайтесь разбавлять материал живой практикой, так интереснее. Как, например, сделал Xezis. Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
Создание Brute/Checker на HTTP запросах с помощью OpenBullet | ОБХОД CSRF-TOKEN | ЧАСТЬ 2 | СОЗДАНИЕ КОНФИГА
https://xss.pro/threads/125492/
- Автор темы
- Добавить закладку
- #789
Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
GPS tracker on Android + Code
https://xss.pro/threads/125555/
https://xss.pro/threads/125556/
JS: Пишем хакерское расширение для браузера. Часть 1https://xss.pro/threads/125566
https://xss.pro/threads/125581/
- Автор темы
- Добавить закладку
- #794
Не забывайте указывать копирайты (отредактировал вашу статью в качестве примера). Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
У вас потерялись (или продублировались) аттачи, поправьте их плз. Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
Самописная платежная система на TON и ее API- https://xss.pro/threads/125596/
- Автор темы
- Добавить закладку
- #796
Спасибо, принято. Оплачиваем. Прошу прислать кошелек в ЛС.
Why use three lines when you can reinvent the wheel in 300?
1. Turbolinks has been deprecated since Rails 6.
2. 3 paragraphs regurgitating what anyone with minimal experience in web dev already knows, explaining MPA vs. SPA.
3. Progressive enhancement for the two people in the world who disable JS on their browsers from the 90s?
4. Copy/paste Inertia.js setup from the docs and stretch it into 5 paragraphs? I’ve seen more original content in the npm registry.
5. In reality, any decent dev can handle state management without needing 300 lines of boilerplate.
6. Pinia just to cache user data is over engineering without a debate. 10 lines with vanilla JS.
Okay, the article has some substance, I won't disagree on that but regarding the payment:
How is this related to DamageLab?
The bulk of his article is about client-side JavaScript: hydrating components, improving rendering times etc.
Client-Side JavaScript is NOT Hacking.
Bro, I see you picking on this guy repeatedly, why are you so fixated on him? If you don't like his content, just ignore it. It's not like it's paid for with your money =)
"It's not like it's paid for with your money" == "I'm not roasting you. why do you care then?"
Do you want me to nail the other guys? Are you down to help me? There's plenty of substance for the both of us.)
Finished reading another article. xxxadam care to join?
2. Setting up a wallet API with basic .py scripts. I’m sure the forum members were on the edge of their seats waiting to learn how to check their crypto balance.
3. Step-by-step guide on how to use requests.get() and bcrypt, API key, hash the password.
4. His little postscript note—where he’s clearly trying to justify that the code won't be paid for—screams insecurity. He knows he’s padding the word count and wants to deflect criticism by saying the articles are “detailed” for those who can’t read code.
5. Next, write something about setting up a Shopfy payment processor.
6. How to build a registration page with Flask.
admin
Some of the writers here have an obsession with word count and the reason escapes me. Among many other weird obsessions like loading unrelated topics on to the forum for a quick $120 payment every weekend.
1. Mention crypto, get paid on a hacking forum.
2. Setting up a wallet API with basic .py scripts. I’m sure the forum members were on the edge of their seats waiting to learn how to check their crypto balance.
3. Step-by-step guide on how to use requests.get() and bcrypt, API key, hash the password.
4. His little postscript note—where he’s clearly trying to justify that the code won't be paid for—screams insecurity. He knows he’s padding the word count and wants to deflect criticism by saying the articles are “detailed” for those who can’t read code.
5. Next, write something about setting up a Shopfy payment processor.
6. How to build a registration page with Flask.
admin
Some of the writers here have an obsession with word count and the reason escapes me. Among many other weird obsessions like loading unrelated topics on to the forum for a quick $120 payment every weekend.