mirror of
https://github.com/SpacehuhnTech/esp8266_deauther.git
synced 2026-04-26 00:05:55 +03:00
[GH-ISSUE #1160] CHANCE TO REVIEW YOUR FOOLISHNESS. #542
Labels
No labels
best of
bug
development
discussion
documentation
duplicate
feature request
help wanted
help wanted
improvement
pinned
pull-request
question
stale
translation
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/esp8266_deauther#542
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @leonierocks on GitHub (Oct 7, 2019).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/1160
CHANCE TO REVIEW YOUR FOOLISHNESS.
You are not getting it right .
Issues on github are for the discussion of problems by likeminded individuals over the same software to try to work out what is happening..
You don't just close an issue because you think it does not concern you ?
"I have looked at it and determined it must be something you did" ??
You don't just stick a label on it and forget it.
What a stupid approach to solving a problem. ...NOT solving it.
Who's got control of you clowns. Who is overseeing the project? NO-ONE IT SEEMS !
I have selected the only board in the deauther section that meets the description.
The ESP8266 device has ESP WROOM 32 marked on the front of it .
Which board should I be selecting at least ?
@spacehuhn commented on GitHub (Oct 7, 2019):
wow
@underwoodblog commented on GitHub (Oct 7, 2019):
Lol, 1bjames1 creating only a new account to post her again. What a madlad!
@tobozo commented on GitHub (Oct 7, 2019):
confusing the effects of a locked post with a banned account totally corroborates the fact that frustration can obfuscate neural paths.
@digmorepaka commented on GitHub (Oct 7, 2019):
I have looked at this issue, and determined it's a waste of time for both the developers, maintainers, and you. If you don't like how the issues section meant for Bug reports is handled, no one forces you to make a post or read the others.
@lbussy commented on GitHub (Oct 7, 2019):
Clearly, the gentleman deserves a refund? Twice what he paid for all of his troubles!
@tobozo commented on GitHub (Oct 7, 2019):
@digmorepaka I'll do you one better: "...it's a waste of time for throth the developers, maintainers, and you"
@0xjmux commented on GitHub (Oct 7, 2019):
I think I deserve a refund for my time for reading this stupid ass post
@f0wl commented on GitHub (Oct 9, 2019):
That's like buying an iPhone and complaining that it doesn't run Android
@jasonjpeters commented on GitHub (Oct 24, 2019):
I'll do ya'll one even more better -- why is Android.
@astonge commented on GitHub (Oct 24, 2019):
You win. I quit.
@jLynx commented on GitHub (Feb 24, 2020):
Closed as OP seems to be off his meds.