├── LICENSE.txt ├── README.md ├── ShellBot.png ├── ShellBot.sh └── exemplos ├── BotDownloadFile1.sh ├── BotTerminal.sh ├── InlineKeyboard.sh ├── InlineYoutube.sh ├── MessageRules.sh ├── MessageRules2.sh ├── ReplyKeyboardMarkup.sh ├── ReplyKeyboardMarkup2.sh ├── WelcomeBot.sh ├── regHandleFunction.sh ├── sendMediaGroup.sh └── sendPoll.sh /LICENSE.txt: -------------------------------------------------------------------------------- 1 | ### AUTHOR/DETAILS 2 | 3 | ShellBot.sh Copyright(c) 2017 Juliano Santos [SHAMAN] 4 | 5 | ### GNU GENERAL PUBLIC LICENSE 6 | 7 | Version 3, 29 June 2007 8 | 9 | Copyright (C) 2007 Free Software Foundation, Inc. 10 | 11 | 12 | Everyone is permitted to copy and distribute verbatim copies of this 13 | license document, but changing it is not allowed. 14 | 15 | ### Preamble 16 | 17 | The GNU General Public License is a free, copyleft license for 18 | software and other kinds of works. 19 | 20 | The licenses for most software and other practical works are designed 21 | to take away your freedom to share and change the works. By contrast, 22 | the GNU General Public License is intended to guarantee your freedom 23 | to share and change all versions of a program--to make sure it remains 24 | free software for all its users. We, the Free Software Foundation, use 25 | the GNU General Public License for most of our software; it applies 26 | also to any other work released this way by its authors. You can apply 27 | it to your programs, too. 28 | 29 | When we speak of free software, we are referring to freedom, not 30 | price. Our General Public Licenses are designed to make sure that you 31 | have the freedom to distribute copies of free software (and charge for 32 | them if you wish), that you receive source code or can get it if you 33 | want it, that you can change the software or use pieces of it in new 34 | free programs, and that you know you can do these things. 35 | 36 | To protect your rights, we need to prevent others from denying you 37 | these rights or asking you to surrender the rights. Therefore, you 38 | have certain responsibilities if you distribute copies of the 39 | software, or if you modify it: responsibilities to respect the freedom 40 | of others. 41 | 42 | For example, if you distribute copies of such a program, whether 43 | gratis or for a fee, you must pass on to the recipients the same 44 | freedoms that you received. You must make sure that they, too, receive 45 | or can get the source code. And you must show them these terms so they 46 | know their rights. 47 | 48 | Developers that use the GNU GPL protect your rights with two steps: 49 | (1) assert copyright on the software, and (2) offer you this License 50 | giving you legal permission to copy, distribute and/or modify it. 51 | 52 | For the developers' and authors' protection, the GPL clearly explains 53 | that there is no warranty for this free software. For both users' and 54 | authors' sake, the GPL requires that modified versions be marked as 55 | changed, so that their problems will not be attributed erroneously to 56 | authors of previous versions. 57 | 58 | Some devices are designed to deny users access to install or run 59 | modified versions of the software inside them, although the 60 | manufacturer can do so. This is fundamentally incompatible with the 61 | aim of protecting users' freedom to change the software. The 62 | systematic pattern of such abuse occurs in the area of products for 63 | individuals to use, which is precisely where it is most unacceptable. 64 | Therefore, we have designed this version of the GPL to prohibit the 65 | practice for those products. If such problems arise substantially in 66 | other domains, we stand ready to extend this provision to those 67 | domains in future versions of the GPL, as needed to protect the 68 | freedom of users. 69 | 70 | Finally, every program is threatened constantly by software patents. 71 | States should not allow patents to restrict development and use of 72 | software on general-purpose computers, but in those that do, we wish 73 | to avoid the special danger that patents applied to a free program 74 | could make it effectively proprietary. To prevent this, the GPL 75 | assures that patents cannot be used to render the program non-free. 76 | 77 | The precise terms and conditions for copying, distribution and 78 | modification follow. 79 | 80 | ### TERMS AND CONDITIONS 81 | 82 | #### 0. Definitions. 83 | 84 | "This License" refers to version 3 of the GNU General Public License. 85 | 86 | "Copyright" also means copyright-like laws that apply to other kinds 87 | of works, such as semiconductor masks. 88 | 89 | "The Program" refers to any copyrightable work licensed under this 90 | License. Each licensee is addressed as "you". "Licensees" and 91 | "recipients" may be individuals or organizations. 92 | 93 | To "modify" a work means to copy from or adapt all or part of the work 94 | in a fashion requiring copyright permission, other than the making of 95 | an exact copy. The resulting work is called a "modified version" of 96 | the earlier work or a work "based on" the earlier work. 97 | 98 | A "covered work" means either the unmodified Program or a work based 99 | on the Program. 100 | 101 | To "propagate" a work means to do anything with it that, without 102 | permission, would make you directly or secondarily liable for 103 | infringement under applicable copyright law, except executing it on a 104 | computer or modifying a private copy. Propagation includes copying, 105 | distribution (with or without modification), making available to the 106 | public, and in some countries other activities as well. 107 | 108 | To "convey" a work means any kind of propagation that enables other 109 | parties to make or receive copies. Mere interaction with a user 110 | through a computer network, with no transfer of a copy, is not 111 | conveying. 112 | 113 | An interactive user interface displays "Appropriate Legal Notices" to 114 | the extent that it includes a convenient and prominently visible 115 | feature that (1) displays an appropriate copyright notice, and (2) 116 | tells the user that there is no warranty for the work (except to the 117 | extent that warranties are provided), that licensees may convey the 118 | work under this License, and how to view a copy of this License. If 119 | the interface presents a list of user commands or options, such as a 120 | menu, a prominent item in the list meets this criterion. 121 | 122 | #### 1. Source Code. 123 | 124 | The "source code" for a work means the preferred form of the work for 125 | making modifications to it. "Object code" means any non-source form of 126 | a work. 127 | 128 | A "Standard Interface" means an interface that either is an official 129 | standard defined by a recognized standards body, or, in the case of 130 | interfaces specified for a particular programming language, one that 131 | is widely used among developers working in that language. 132 | 133 | The "System Libraries" of an executable work include anything, other 134 | than the work as a whole, that (a) is included in the normal form of 135 | packaging a Major Component, but which is not part of that Major 136 | Component, and (b) serves only to enable use of the work with that 137 | Major Component, or to implement a Standard Interface for which an 138 | implementation is available to the public in source code form. A 139 | "Major Component", in this context, means a major essential component 140 | (kernel, window system, and so on) of the specific operating system 141 | (if any) on which the executable work runs, or a compiler used to 142 | produce the work, or an object code interpreter used to run it. 143 | 144 | The "Corresponding Source" for a work in object code form means all 145 | the source code needed to generate, install, and (for an executable 146 | work) run the object code and to modify the work, including scripts to 147 | control those activities. However, it does not include the work's 148 | System Libraries, or general-purpose tools or generally available free 149 | programs which are used unmodified in performing those activities but 150 | which are not part of the work. For example, Corresponding Source 151 | includes interface definition files associated with source files for 152 | the work, and the source code for shared libraries and dynamically 153 | linked subprograms that the work is specifically designed to require, 154 | such as by intimate data communication or control flow between those 155 | subprograms and other parts of the work. 156 | 157 | The Corresponding Source need not include anything that users can 158 | regenerate automatically from other parts of the Corresponding Source. 159 | 160 | The Corresponding Source for a work in source code form is that same 161 | work. 162 | 163 | #### 2. Basic Permissions. 164 | 165 | All rights granted under this License are granted for the term of 166 | copyright on the Program, and are irrevocable provided the stated 167 | conditions are met. This License explicitly affirms your unlimited 168 | permission to run the unmodified Program. The output from running a 169 | covered work is covered by this License only if the output, given its 170 | content, constitutes a covered work. This License acknowledges your 171 | rights of fair use or other equivalent, as provided by copyright law. 172 | 173 | You may make, run and propagate covered works that you do not convey, 174 | without conditions so long as your license otherwise remains in force. 175 | You may convey covered works to others for the sole purpose of having 176 | them make modifications exclusively for you, or provide you with 177 | facilities for running those works, provided that you comply with the 178 | terms of this License in conveying all material for which you do not 179 | control copyright. Those thus making or running the covered works for 180 | you must do so exclusively on your behalf, under your direction and 181 | control, on terms that prohibit them from making any copies of your 182 | copyrighted material outside their relationship with you. 183 | 184 | Conveying under any other circumstances is permitted solely under the 185 | conditions stated below. Sublicensing is not allowed; section 10 makes 186 | it unnecessary. 187 | 188 | #### 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 189 | 190 | No covered work shall be deemed part of an effective technological 191 | measure under any applicable law fulfilling obligations under article 192 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 193 | similar laws prohibiting or restricting circumvention of such 194 | measures. 195 | 196 | When you convey a covered work, you waive any legal power to forbid 197 | circumvention of technological measures to the extent such 198 | circumvention is effected by exercising rights under this License with 199 | respect to the covered work, and you disclaim any intention to limit 200 | operation or modification of the work as a means of enforcing, against 201 | the work's users, your or third parties' legal rights to forbid 202 | circumvention of technological measures. 203 | 204 | #### 4. Conveying Verbatim Copies. 205 | 206 | You may convey verbatim copies of the Program's source code as you 207 | receive it, in any medium, provided that you conspicuously and 208 | appropriately publish on each copy an appropriate copyright notice; 209 | keep intact all notices stating that this License and any 210 | non-permissive terms added in accord with section 7 apply to the code; 211 | keep intact all notices of the absence of any warranty; and give all 212 | recipients a copy of this License along with the Program. 213 | 214 | You may charge any price or no price for each copy that you convey, 215 | and you may offer support or warranty protection for a fee. 216 | 217 | #### 5. Conveying Modified Source Versions. 218 | 219 | You may convey a work based on the Program, or the modifications to 220 | produce it from the Program, in the form of source code under the 221 | terms of section 4, provided that you also meet all of these 222 | conditions: 223 | 224 | - a) The work must carry prominent notices stating that you modified 225 | it, and giving a relevant date. 226 | - b) The work must carry prominent notices stating that it is 227 | released under this License and any conditions added under 228 | section 7. This requirement modifies the requirement in section 4 229 | to "keep intact all notices". 230 | - c) You must license the entire work, as a whole, under this 231 | License to anyone who comes into possession of a copy. This 232 | License will therefore apply, along with any applicable section 7 233 | additional terms, to the whole of the work, and all its parts, 234 | regardless of how they are packaged. This License gives no 235 | permission to license the work in any other way, but it does not 236 | invalidate such permission if you have separately received it. 237 | - d) If the work has interactive user interfaces, each must display 238 | Appropriate Legal Notices; however, if the Program has interactive 239 | interfaces that do not display Appropriate Legal Notices, your 240 | work need not make them do so. 241 | 242 | A compilation of a covered work with other separate and independent 243 | works, which are not by their nature extensions of the covered work, 244 | and which are not combined with it such as to form a larger program, 245 | in or on a volume of a storage or distribution medium, is called an 246 | "aggregate" if the compilation and its resulting copyright are not 247 | used to limit the access or legal rights of the compilation's users 248 | beyond what the individual works permit. Inclusion of a covered work 249 | in an aggregate does not cause this License to apply to the other 250 | parts of the aggregate. 251 | 252 | #### 6. Conveying Non-Source Forms. 253 | 254 | You may convey a covered work in object code form under the terms of 255 | sections 4 and 5, provided that you also convey the machine-readable 256 | Corresponding Source under the terms of this License, in one of these 257 | ways: 258 | 259 | - a) Convey the object code in, or embodied in, a physical product 260 | (including a physical distribution medium), accompanied by the 261 | Corresponding Source fixed on a durable physical medium 262 | customarily used for software interchange. 263 | - b) Convey the object code in, or embodied in, a physical product 264 | (including a physical distribution medium), accompanied by a 265 | written offer, valid for at least three years and valid for as 266 | long as you offer spare parts or customer support for that product 267 | model, to give anyone who possesses the object code either (1) a 268 | copy of the Corresponding Source for all the software in the 269 | product that is covered by this License, on a durable physical 270 | medium customarily used for software interchange, for a price no 271 | more than your reasonable cost of physically performing this 272 | conveying of source, or (2) access to copy the Corresponding 273 | Source from a network server at no charge. 274 | - c) Convey individual copies of the object code with a copy of the 275 | written offer to provide the Corresponding Source. This 276 | alternative is allowed only occasionally and noncommercially, and 277 | only if you received the object code with such an offer, in accord 278 | with subsection 6b. 279 | - d) Convey the object code by offering access from a designated 280 | place (gratis or for a charge), and offer equivalent access to the 281 | Corresponding Source in the same way through the same place at no 282 | further charge. You need not require recipients to copy the 283 | Corresponding Source along with the object code. If the place to 284 | copy the object code is a network server, the Corresponding Source 285 | may be on a different server (operated by you or a third party) 286 | that supports equivalent copying facilities, provided you maintain 287 | clear directions next to the object code saying where to find the 288 | Corresponding Source. Regardless of what server hosts the 289 | Corresponding Source, you remain obligated to ensure that it is 290 | available for as long as needed to satisfy these requirements. 291 | - e) Convey the object code using peer-to-peer transmission, 292 | provided you inform other peers where the object code and 293 | Corresponding Source of the work are being offered to the general 294 | public at no charge under subsection 6d. 295 | 296 | A separable portion of the object code, whose source code is excluded 297 | from the Corresponding Source as a System Library, need not be 298 | included in conveying the object code work. 299 | 300 | A "User Product" is either (1) a "consumer product", which means any 301 | tangible personal property which is normally used for personal, 302 | family, or household purposes, or (2) anything designed or sold for 303 | incorporation into a dwelling. In determining whether a product is a 304 | consumer product, doubtful cases shall be resolved in favor of 305 | coverage. For a particular product received by a particular user, 306 | "normally used" refers to a typical or common use of that class of 307 | product, regardless of the status of the particular user or of the way 308 | in which the particular user actually uses, or expects or is expected 309 | to use, the product. A product is a consumer product regardless of 310 | whether the product has substantial commercial, industrial or 311 | non-consumer uses, unless such uses represent the only significant 312 | mode of use of the product. 313 | 314 | "Installation Information" for a User Product means any methods, 315 | procedures, authorization keys, or other information required to 316 | install and execute modified versions of a covered work in that User 317 | Product from a modified version of its Corresponding Source. The 318 | information must suffice to ensure that the continued functioning of 319 | the modified object code is in no case prevented or interfered with 320 | solely because modification has been made. 321 | 322 | If you convey an object code work under this section in, or with, or 323 | specifically for use in, a User Product, and the conveying occurs as 324 | part of a transaction in which the right of possession and use of the 325 | User Product is transferred to the recipient in perpetuity or for a 326 | fixed term (regardless of how the transaction is characterized), the 327 | Corresponding Source conveyed under this section must be accompanied 328 | by the Installation Information. But this requirement does not apply 329 | if neither you nor any third party retains the ability to install 330 | modified object code on the User Product (for example, the work has 331 | been installed in ROM). 332 | 333 | The requirement to provide Installation Information does not include a 334 | requirement to continue to provide support service, warranty, or 335 | updates for a work that has been modified or installed by the 336 | recipient, or for the User Product in which it has been modified or 337 | installed. Access to a network may be denied when the modification 338 | itself materially and adversely affects the operation of the network 339 | or violates the rules and protocols for communication across the 340 | network. 341 | 342 | Corresponding Source conveyed, and Installation Information provided, 343 | in accord with this section must be in a format that is publicly 344 | documented (and with an implementation available to the public in 345 | source code form), and must require no special password or key for 346 | unpacking, reading or copying. 347 | 348 | #### 7. Additional Terms. 349 | 350 | "Additional permissions" are terms that supplement the terms of this 351 | License by making exceptions from one or more of its conditions. 352 | Additional permissions that are applicable to the entire Program shall 353 | be treated as though they were included in this License, to the extent 354 | that they are valid under applicable law. If additional permissions 355 | apply only to part of the Program, that part may be used separately 356 | under those permissions, but the entire Program remains governed by 357 | this License without regard to the additional permissions. 358 | 359 | When you convey a copy of a covered work, you may at your option 360 | remove any additional permissions from that copy, or from any part of 361 | it. (Additional permissions may be written to require their own 362 | removal in certain cases when you modify the work.) You may place 363 | additional permissions on material, added by you to a covered work, 364 | for which you have or can give appropriate copyright permission. 365 | 366 | Notwithstanding any other provision of this License, for material you 367 | add to a covered work, you may (if authorized by the copyright holders 368 | of that material) supplement the terms of this License with terms: 369 | 370 | - a) Disclaiming warranty or limiting liability differently from the 371 | terms of sections 15 and 16 of this License; or 372 | - b) Requiring preservation of specified reasonable legal notices or 373 | author attributions in that material or in the Appropriate Legal 374 | Notices displayed by works containing it; or 375 | - c) Prohibiting misrepresentation of the origin of that material, 376 | or requiring that modified versions of such material be marked in 377 | reasonable ways as different from the original version; or 378 | - d) Limiting the use for publicity purposes of names of licensors 379 | or authors of the material; or 380 | - e) Declining to grant rights under trademark law for use of some 381 | trade names, trademarks, or service marks; or 382 | - f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions 384 | of it) with contractual assumptions of liability to the recipient, 385 | for any liability that these contractual assumptions directly 386 | impose on those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; the 405 | above requirements apply either way. 406 | 407 | #### 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your license 416 | from a particular copyright holder is reinstated (a) provisionally, 417 | unless and until the copyright holder explicitly and finally 418 | terminates your license, and (b) permanently, if the copyright holder 419 | fails to notify you of the violation by some reasonable means prior to 420 | 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | #### 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or run 438 | a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | #### 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | #### 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims owned 478 | or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within the 522 | scope of its coverage, prohibits the exercise of, or is conditioned on 523 | the non-exercise of one or more of the rights that are specifically 524 | granted under this License. You may not convey a covered work if you 525 | are a party to an arrangement with a third party that is in the 526 | business of distributing software, under which you make payment to the 527 | third party based on the extent of your activity of conveying the 528 | work, and under which the third party grants, to any of the parties 529 | who would receive the covered work from you, a discriminatory patent 530 | license (a) in connection with copies of the covered work conveyed by 531 | you (or copies made from those copies), or (b) primarily for and in 532 | connection with specific products or compilations that contain the 533 | covered work, unless you entered into that arrangement, or that patent 534 | license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | #### 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under 546 | this License and any other pertinent obligations, then as a 547 | consequence you may not convey it at all. For example, if you agree to 548 | terms that obligate you to collect a royalty for further conveying 549 | from those to whom you convey the Program, the only way you could 550 | satisfy both those terms and this License would be to refrain entirely 551 | from conveying the Program. 552 | 553 | #### 13. Use with the GNU Affero General Public License. 554 | 555 | Notwithstanding any other provision of this License, you have 556 | permission to link or combine any covered work with a work licensed 557 | under version 3 of the GNU Affero General Public License into a single 558 | combined work, and to convey the resulting work. The terms of this 559 | License will continue to apply to the part which is the covered work, 560 | but the special requirements of the GNU Affero General Public License, 561 | section 13, concerning interaction through a network will apply to the 562 | combination as such. 563 | 564 | #### 14. Revised Versions of this License. 565 | 566 | The Free Software Foundation may publish revised and/or new versions 567 | of the GNU General Public License from time to time. Such new versions 568 | will be similar in spirit to the present version, but may differ in 569 | detail to address new problems or concerns. 570 | 571 | Each version is given a distinguishing version number. If the Program 572 | specifies that a certain numbered version of the GNU General Public 573 | License "or any later version" applies to it, you have the option of 574 | following the terms and conditions either of that numbered version or 575 | of any later version published by the Free Software Foundation. If the 576 | Program does not specify a version number of the GNU General Public 577 | License, you may choose any version ever published by the Free 578 | Software Foundation. 579 | 580 | If the Program specifies that a proxy can decide which future versions 581 | of the GNU General Public License can be used, that proxy's public 582 | statement of acceptance of a version permanently authorizes you to 583 | choose that version for the Program. 584 | 585 | Later license versions may give you additional or different 586 | permissions. However, no additional obligations are imposed on any 587 | author or copyright holder as a result of your choosing to follow a 588 | later version. 589 | 590 | #### 15. Disclaimer of Warranty. 591 | 592 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 593 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 594 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT 595 | WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT 596 | LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 597 | A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND 598 | PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE 599 | DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR 600 | CORRECTION. 601 | 602 | #### 16. Limitation of Liability. 603 | 604 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 605 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR 606 | CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 607 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES 608 | ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT 609 | NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR 610 | LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM 611 | TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER 612 | PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 613 | 614 | #### 17. Interpretation of Sections 15 and 16. 615 | 616 | If the disclaimer of warranty and limitation of liability provided 617 | above cannot be given local legal effect according to their terms, 618 | reviewing courts shall apply local law that most closely approximates 619 | an absolute waiver of all civil liability in connection with the 620 | Program, unless a warranty or assumption of liability accompanies a 621 | copy of the Program in return for a fee. 622 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # ShellBot API v6.4.0 2 | ![ShellBot](https://github.com/shellscriptx/ShellBot/blob/master/ShellBot.png) 3 | 4 | ## Sobre 5 | 6 | 7 | O **ShellBot.sh** é uma API desenvolvida em **shell script** que permite a criação de bot's na plataforma. Para mais informações: [Telegram API](https://core.telegram.org/api). O projeto teve inicio após o desenvolvimento do bot [@shellscriptx_bot](t.me/shellscriptx_bot) que tinha como propósito apenas enviar mensagens de boas-vindas aos membros do grupo [@shellscript_x](t.me/shellscript_x). Sua evolução foi notável e novos recursos foram surgindo devido a sua integração nativa entre `sistema x bot` ficou cada vez mais aparente e a ideia de criar uma **API** surgiu. Sair da tradicional *gambiarra* e partir para funções estruturadas no intuito de agilizar e facilitar a criação de um bot em **Shell**. 8 | 9 | ## Créditos 10 | 11 | Desenvolvido por **Juliano Santos (SHAMAN)** 12 | 13 | Linguagem: **shell script** 14 | 15 | ## Contato 16 | 17 | Para informações, sugestões ou reporte de falhas, envie e-mail para 18 | 19 | Telegram (suporte): https://t.me/shellbot_api 20 | 21 | Blog: http://www.shellscriptx.blogspot.com.br 22 | 23 | Fanpage: https://www.facebook.com/shellscriptx 24 | 25 | Telegram (contato): https://t.me/x_SHAMAN_x 26 | 27 | Telegram (grupo): https://t.me/shellscript_x 28 | 29 | ## Agradecimentos 30 | 31 | A **Najane Lopes (Jane)** por escolher o nome da **API** e batizá-la de **ShellBot**. Um nome que indica de onde veio e o que faz. 32 | 33 | ## Requerimentos: 34 | 35 | |Pacote| Descrição| 36 | |---------|--------------| 37 | |bash (4.3 ou superior)|Interpretador de comandos Bourne-Again Shell| 38 | |jq (1.5 ou superior) ([baixar binário](https://stedolan.github.io/jq/download))|Processador de comandos JSON| 39 | |curl|Ferramenta para transferir dados de ou para um servidor.| 40 | 41 | > Certifique-se que todos os pacotes estão instalados. 42 | 43 | ## Download 44 | 45 | Realizando o download do projeto. 46 | 47 | ``` 48 | $ git clone https://github.com/shellscriptx/ShellBot.git && cd ShellBot 49 | ``` 50 | 51 | Copie o arquivo **ShellBot.sh** para a pasta do projeto do bot. 52 | 53 | Exemplo: 54 | 55 | ``` 56 | $ cp ShellBot.sh /projeto/meu_bot/ 57 | ``` 58 | 59 | ## Documentação 60 | 61 | Para mais informações consulte a documentação do projeto na página [wiki](https://github.com/shellscriptx/ShellBot/wiki). 62 | 63 | ## Ajude o projeto 64 | 65 | O projeto nasceu com o objetivo de ajudar a comunidade, permitindo o acesso gratuito aos recursos e atualizações. Todo trabalho é realizado com tecnicidade em um movimento totalmente voluntário por parte do desenvolvedor. 66 | 67 | O **ShellBot** é útil? 68 | 69 | Se _"Sim"_, nos ajude a mantê-lo "vivo" realizando uma doação simbólica. "Um programador não vive sem café!!" 70 | 71 | [![Apoia-se](https://1.bp.blogspot.com/-tTGuT8BaEPs/X3jQhIyqjKI/AAAAAAAAKDY/k6F8PaVGQMMZw5YAXo3TYlevXNXDptpDACK4BGAYYCw/s1600/logoRed.png)](https://apoia.se/shellscriptx) 72 | 73 | -------------------------------------------------------------------------------- /ShellBot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/shellscriptx/shellbot/a4d88a12572f51a09397df3f3df638a64552f48e/ShellBot.png -------------------------------------------------------------------------------- /exemplos/BotDownloadFile1.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # SCRIPT: BotDownloadFile1.sh 4 | # 5 | # DESCRIÇÃO: Efetua download dos arquivos enviados para o privado, grupo ou canal. 6 | # Em grupos/canais o bot precisa ser administrador para ter acesso a 7 | # todas mensagens enviadas. 8 | # 9 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 10 | # ser substituidos pelos parâmetros curtos respectivos. 11 | 12 | # Importando API 13 | source ShellBot.sh 14 | 15 | # Token do bot 16 | bot_token='' 17 | 18 | # Inicializando o bot 19 | ShellBot.init --token "$bot_token" --monitor --return map 20 | 21 | function download_file() 22 | { 23 | local file_id 24 | 25 | if [[ ${message_photo_file_id[$id]} ]]; then 26 | # Em alguns arquivos de imagem o telegram aplica uma escala de tamanho 27 | # gerando id's para diferentes resoluções da mesma iagem. São elas (baixa, média, alta). 28 | # Os id's são armazenados e separados pelo delimitador '|' (padrão). 29 | # 30 | # Exemplo: 31 | # baixa_id|media_id|alta_id 32 | 33 | # Extrai o id da imagem com melhor resolução. 34 | file_id=${message_photo_file_id[$id]##*|} 35 | else 36 | # Outros objetos. 37 | # Extrai o id do objeto da mensagem. 38 | # document, audio, sticker, voice 39 | file_id=$(cat << _eof 40 | ${message_document_file_id[$id]} 41 | ${message_audio_file_id[$id]} 42 | ${message_sticker_file_id[$id]} 43 | ${message_voice_file_id[$id]} 44 | _eof 45 | ) 46 | fi 47 | 48 | # Verifica se 'file_id' contém um id válido. 49 | if [[ $file_id ]]; then 50 | # Obtém informações do arquivo, incluindo sua localização nos servidores do Telegram. 51 | ShellBot.getFile --file_id $file_id 52 | 53 | # Baixa o arquivo do diretório remoto contido em '{return[file_path]}' após 54 | # a chamada do método 'ShellBot.getFile'. 55 | # Obs: Recurso disponível somente no modo de retorno 'map'. 56 | if ShellBot.downloadFile --file_path "${return[file_path]}" --dir "$HOME"; then 57 | ShellBot.sendMessage --chat_id "${message_chat_id[$id]}" \ 58 | --reply_to_message_id "${message_message_id[$id]}" \ 59 | --text "Arquivo baixado com sucesso!!\n\nSalvo em: ${return[file_path]}" 60 | fi 61 | fi 62 | 63 | return 0 64 | } 65 | 66 | while : 67 | do 68 | # Obtem as atualizações 69 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 70 | 71 | # Lista o índice das atualizações 72 | for id in $(ShellBot.ListUpdates) 73 | do 74 | # Inicio thread 75 | ( 76 | # Executa a função 'download_file' se a requisição não for um objeto de texto. 77 | [[ ${message_text[$id]} ]] || download_file 78 | 79 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 80 | done 81 | done 82 | #FIM 83 | -------------------------------------------------------------------------------- /exemplos/BotTerminal.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: BotTerminal.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot com log. 15 | ShellBot.init --token "$bot_token" --monitor --flush --log_file "/tmp/${0##*/}.log" 16 | ShellBot.username 17 | 18 | # A definição da regra a seguir utiliza uma construção curta na declaração 19 | # de múltiplos comandos. Aplicando o recurso de expansão de variáveis e 20 | # argumentos posicionais é possível criar comandos/argumentos para adequação 21 | # da sintaxe, podendo ser distribuida em regras e tratamentos distintos. 22 | # 23 | # Comandos: /who, /date, /df e /du (regex) 24 | ShellBot.setMessageRules --name 'terminal_comandos' \ 25 | --chat_type private \ 26 | --entitie_type bot_command \ 27 | --text '^/(who|date|df|du)[ ]+' \ 28 | --exec '${1#/} ${*:2}' # Remove a barra inicial do argumento posicional '$1' (bot comando) transformando-o 29 | # em um comando de shell válido e passa os argumentos posicionais subsequentes. 30 | # 31 | # Exemplo: 32 | # 33 | # Exibindo o contéudo do arquivo e enumerando as respectivas linhas. 34 | # 35 | # bot comando: /cat -n /etc/group /etc/passwd 36 | # exec: cat -n /etc/group /etc/passwd 37 | 38 | # A regra abaixo demonstra a construção de uma linha de comando personalizada 39 | # que recebe os elementos do texto como argumentos. 40 | ShellBot.setMessageRules --name 'filtrar_arquivo' \ 41 | --chat_type private \ 42 | --entitie_type bot_command \ 43 | --command '/filtrar' \ 44 | --num_args 3 \ 45 | --exec 'cat "$3" | egrep "$2"' # Utilizando os argumentos posicionais. 46 | # 47 | # Exemplo: 48 | # 49 | # bot comando: /filtrar root /etc/group 50 | # exec: cat "/etc/group" | egrep "root" 51 | 52 | # Definindo uma regra que contém um comando que lista recursivamente 53 | # o contéudo do diretório especificado. 54 | # Obs: Dependendo do diretório informado a saída poderá ser dividida 55 | # em várias mensagens de retorno e no pior dos cenários o possível 56 | # excesso de requisições. 57 | ShellBot.setMessageRules --name 'listar_diretorio' \ 58 | --chat_type private \ 59 | --entitie_type bot_command \ 60 | --command '/listar' \ 61 | --num_args 2 \ 62 | --exec 'ls -R $2' # Exemplo: 63 | # 64 | # bot comando: /listar /etc 65 | # exec: ls -R /etc 66 | 67 | # Aplica regra de erro caso nenhuma das regras anteriores forem satisfeitas. 68 | ShellBot.setMessageRules --name 'comando_invalido' \ 69 | --chat_type private \ 70 | --entitie_type bot_command \ 71 | --bot_reply_message 'erro: comando não encontrado.' 72 | while : 73 | do 74 | # Obtem as atualizações 75 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 76 | 77 | # Lista o índice das atualizações 78 | for id in $(ShellBot.ListUpdates) 79 | do 80 | # Inicio thread 81 | ( 82 | # Gerenciar regras 83 | ShellBot.manageRules --update_id $id 84 | 85 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 86 | done 87 | done 88 | #FIM 89 | -------------------------------------------------------------------------------- /exemplos/InlineKeyboard.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: InlineKeyboard.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" 16 | ShellBot.username 17 | 18 | # Limpa o array que irá receber a estrutura inline_button e suas configurações. 19 | botao1='' 20 | 21 | # INLINE_BUTTON - CONFIGURAÇÕES. 22 | # 23 | # Cria e define as configurações do objeto inline_button, 24 | # armazenando-as na variável 'botao1'. 25 | # O parâmetro '-l, --line' determinada a posição do objeto na exibição. 26 | # É possível especificar um ou mais botões na mesma linha. Neste caso 27 | # os serão redimencionados e dispostos em paralelo. 28 | # 29 | # Layout defino abaixo: 30 | # 31 | # [ Blog ] -> linha 1 32 | # [ Telegram (Grupo) ] [ Telegram (Canal) ] -> linha 2 33 | # [ Github ] -> linha 3 34 | # 35 | # 36 | # 37 | # Quando um botão é pressionado o usuário é redirecionado para o endereço configurando em '--url' 38 | ShellBot.InlineKeyboardButton --button 'botao1' --line 1 --text 'Blog' --callback_data '1' --url 'http://shellscriptx.blogspot.com.br' # linha 1 39 | ShellBot.InlineKeyboardButton --button 'botao1' --line 2 --text 'Telegram (Grupo)' --callback_data '3' --url 't.me/shellscript_x' # linha 2 40 | ShellBot.InlineKeyboardButton --button 'botao1' --line 2 --text 'Telegram (Canal)' --callback_data '4' --url 't.me/shellscriptx' # linha 2 41 | ShellBot.InlineKeyboardButton --button 'botao1' --line 3 --text 'Github' --callback_data '5' --url 'https://github.com/shellscriptx' # linha 3 42 | 43 | # Cria o objeto inline_keyboard contendo os elementos armazenados na variável 'botao1' 44 | # É retornada a nova estrutura e armazena em 'keyboard1'. 45 | keyboard1="$(ShellBot.InlineKeyboardMarkup -b 'botao1')" 46 | 47 | while : 48 | do 49 | # Obtem as atualizações 50 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 51 | 52 | # Lista o índice das atualizações 53 | for id in $(ShellBot.ListUpdates) 54 | do 55 | # Inicio thread 56 | ( 57 | # Verifica se a mensagem enviada pelo usuário é um comando válido. 58 | case ${message_text[$id]} in 59 | "/sigame") # bot comando 60 | # Envia a mensagem anexando o teclado "$keyboard1" 61 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} --text '*Siga-me*' \ 62 | --reply_markup "$keyboard1" \ 63 | --parse_mode markdown 64 | ;; 65 | esac 66 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 67 | done 68 | done 69 | #FIM 70 | -------------------------------------------------------------------------------- /exemplos/InlineYoutube.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # XXX SOBRE XXX 4 | # 5 | # script: InlineYoutube.sh 6 | # 7 | # O script implementa um Bot Inline semelhante ao '@vid' que realiza 8 | # consultas de vídeos no site do youtube. 9 | # 10 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 11 | # ser substituidos pelos parâmetros curtos respectivos. 12 | # 13 | # XXX ATENÇÃO XXX 14 | # 15 | # É necessário habilitar o modo inline. Para ativar essa opção, envie o 16 | # comando /setinline para @BotFather e forneça o texto de espaço reservado 17 | # que o usuário verá no campo de entrada depois de digitar o nome do seu bot. 18 | 19 | # Importando API 20 | source ShellBot.sh 21 | 22 | # Token do bot 23 | bot_token='' 24 | 25 | # Inicializando o bot 26 | ShellBot.init --token "$bot_token" --flush --monitor --return map 27 | 28 | yt_video() 29 | { 30 | local vid title views 31 | local resp yt_video query vids i 32 | local re_vid re_vt re_vv 33 | 34 | yt_video='https://www.youtube.com/watch?v=' # URI 35 | 36 | # Regex 37 | re_vid='href="/watch\?v=([a-zA-Z0-9_-]+)"' # ID 38 | re_vt='title="([^"]+)' # Título 39 | re_vv='
  • ([0-9.]+\s+(visualizações|views))
    • ' # Visualizações 40 | 41 | query='' 42 | 43 | while read -r resp; do 44 | # Extrai as informações do video. (se presente) 45 | if [[ $resp =~ $re_vid ]] && vid=${BASH_REMATCH[1]} && 46 | [[ $resp =~ $re_vt ]] && title=${BASH_REMATCH[1]} && 47 | [[ $resp =~ $re_vv ]] && views=${BASH_REMATCH[1]}; then 48 | 49 | # Salta para o próximo elemento caso já exista. 50 | [[ $vid == @($vids) ]] && continue 51 | 52 | # Cria/anexa o objeto video a query de resultado. 53 | ShellBot.InlineQueryResult --input query \ 54 | --type video \ 55 | --mime_type 'video/mp4' \ 56 | --id "$vid" \ 57 | --video_url "${yt_video}${vid}" \ 58 | --thumb_url "https://i.ytimg.com/vi/${vid}/hqdefault.jpg" \ 59 | --title "${title}" \ 60 | --description "${views}" \ 61 | --input_message_content "$(ShellBot.InputMessageContent --message_text "${yt_video}${vid}")" # Envia o link caso o usuário clique no video da lista. 62 | 63 | # 50 resultados por query. (limite máximo suportado pelo Telegram) 64 | [[ $((++i)) -eq 50 ]] && break 65 | 66 | # Atualiza a lista com o objeto criado. 67 | vids+=${vids:+|}$vid 68 | fi 69 | # Envia uma requisição a uri de pesquisa do youtube com o video especificado na query de consulta. 70 | done < <(wget -qO- "https://www.youtube.com/results?search_query=${inline_query_query[$id]// /+}") 71 | 72 | # Envia a query com os resultados da consulta. 73 | ShellBot.answerInlineQuery --inline_query_id ${inline_query_id[$id]} \ 74 | --results "$query" 75 | 76 | return $? 77 | } 78 | 79 | while : 80 | do 81 | # Obtem as atualizações 82 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 83 | 84 | # Lista o índice das atualizações 85 | for id in $(ShellBot.ListUpdates) 86 | do 87 | # Inicio thread 88 | ( 89 | # Executa a função caso uma consulta inline for iniciada. 90 | [[ $inline_query_id ]] && yt_video 91 | 92 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 93 | done 94 | done 95 | #FIM 96 | -------------------------------------------------------------------------------- /exemplos/MessageRules.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: MessageRules.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" --monitor --flush 16 | ShellBot.username 17 | 18 | # FUNÇÕES (AÇÃO) 19 | # 20 | # AS FUNÇÕES DEVEM SER DECLARADAS PREVIAMENTE ANTES DE SEREM 21 | # VINCULADAS AS REGRAS. 22 | # 23 | apagar_grupo_url(){ 24 | ShellBot.deleteMessage --chat_id ${message_chat_id[$id]} \ 25 | --message_id ${message_message_id[$id]} 26 | 27 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 28 | --text "Prezado [@${message_from_username[$id]}], não é permitido a divulgação de grupos/canais." \ 29 | --parse_mode markdown 30 | } 31 | 32 | ping_host(){ 33 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 34 | --text "$(ping -c4 ${message_text[$id]#* })" 35 | } 36 | 37 | msg_bem_vindo(){ 38 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 39 | --text "Seja bem vindo(a) [@${message_new_chat_member_username[$id]}] "'!!' \ 40 | --parse_mode markdown 41 | } 42 | 43 | msg_despedida(){ 44 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 45 | --text "Tchau [@${message_left_chat_member_username[$id]}], esperamos que volte em breve." \ 46 | --parse_mode markdown 47 | } 48 | 49 | apagar_msg(){ 50 | ShellBot.deleteMessage --chat_id ${message_chat_id[$id]} \ 51 | --message_id ${message_message_id[$id]} 52 | } 53 | 54 | usuario_info(){ 55 | # A função recebe como argumento posicional os elementos contidos na 56 | # mensagem, onde '$2' contém o nome do usuário a ser consultado. 57 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} --text "$(id $2)" 58 | } 59 | 60 | # REGRAS 61 | # 62 | # XXX ATENÇÃO XXX 63 | # 64 | # AS REGRAS SÃO TRATADAS SEQUÊNCIALMENTE NA ORDEM EM QUE FORAM DEFINIDAS, CASO 65 | # A MENSAGEM SATISFAÇA AO CONJUNTO DE CRITÉRIOS ESTABELECIDOS NA REGRA, A AÇÃO É 66 | # APLICADA (SE PRESENTE) E SALTA PARA A PRÓXIMA REQUISIÇÃO. 67 | # 68 | 69 | # Criando duas regras sem ação que envia uma mensagem informativa sobre o horário 70 | # de atendimento e ignora todas as requisições enviadas ao bot fora do dia/horário. 71 | 72 | # Texto informativo 73 | msg_info='Lamento, mas o horário para atendimento é das 8:00 às 18:00 de segunda à sexta.' 74 | 75 | # Finais de semana em qualquer horário. 76 | ShellBot.setMessageRules --name 'bot_horario_operacao1' \ 77 | --weekday 6 \ 78 | --weekday 7 \ 79 | --bot_reply_message "$msg_info" 80 | 81 | # Dias da semana fora do horário operacional. 82 | ShellBot.setMessageRules --name 'bot_horario_operacao2' \ 83 | --time '00:00-08:00,18:00-23:59' \ 84 | --weekday '1,2,3,4,5' \ 85 | --bot_reply_message "$msg_info" 86 | 87 | # Define o comando e a quantidade de argumentos aceitos na mensagem. 88 | # ex: /userinfo 89 | # | | 90 | # arg1 arg2 91 | ShellBot.setMessageRules --name 'ver_membro' \ 92 | --user_status administrator 93 | 94 | ShellBot.setMessageRules --name 'obter_informacoes_do_usuario' \ 95 | --action usuario_info \ 96 | --command '/userinfo' \ 97 | --num_args 2 98 | 99 | # Liberar o comando 'ping' para uma lista de usuários em horários especificos. 100 | ShellBot.setMessageRules --name 'pingar_host' \ 101 | --action ping_host \ 102 | --command '/ping' \ 103 | --username 'x_SHAMAN_x,admin1,admin2' \ 104 | --time '12:00-14:30' 105 | 106 | # Apagar as mensagens de divulgação em um grupo/super-grupo. 107 | ShellBot.setMessageRules --name 'apagar_postagem_de_grupos' \ 108 | --action apagar_grupo_url \ 109 | --entitie_type url \ 110 | --chat_type 'supergroup,group' \ 111 | --text 't.me/[a-zA-Z0-9_]+' 112 | 113 | # Envia mensagem de boas-vindas ao usuário no momento que ingressar ao grupo. 114 | ShellBot.setMessageRules --name 'mensagem_boas_vindas' \ 115 | --action msg_bem_vindo \ 116 | --chat_type 'supergroup,group' \ 117 | --chat_member new 118 | 119 | # Envia mensagem de despedida quando o usuário deixar o grupo. 120 | ShellBot.setMessageRules --name 'mensagem_despedida' \ 121 | --action msg_despedida \ 122 | --chat_type 'supergroup,group' \ 123 | --chat_member left 124 | 125 | # Apagar todos os arquivos executaveis enviados entre 01:00 e 06:00 da manhã no mês de dezembro. 126 | ShellBot.setMessageRules --name 'apagar_executaveis' \ 127 | --action apagar_msg \ 128 | --chat_type 'supergroup,group' \ 129 | --date '01/12/2018-31/12/2018' \ 130 | --time '01:00-06:00' \ 131 | --mime_type 'application/x-executable' 132 | 133 | # Apagar todas as fotos postadas no final de semana. 134 | ShellBot.setMessageRules --name 'apagar_fotos_final_de_semana' \ 135 | --action apagar_msg \ 136 | --chat_type 'supergroup,group' \ 137 | --file_type photo \ 138 | --weekday '6,7' 139 | 140 | # Notifica o usuário sempre que o mesmo postar uma foto no grupo ou super-grupo. 141 | ShellBot.setMessageRules --name 'postagem_fotos' \ 142 | --mime_type 'image/jpeg' \ 143 | --chat_type 'supergroup,group' \ 144 | --bot_reply_message 'Evite postar fotos no grupo, obrigado.' 145 | 146 | while : 147 | do 148 | # Obtem as atualizações 149 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 150 | 151 | # Lista o índice das atualizações 152 | for id in $(ShellBot.ListUpdates) 153 | do 154 | # Inicio thread 155 | ( 156 | # Gerenciar regras 157 | ShellBot.manageRules --update_id $id 158 | 159 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 160 | done 161 | done 162 | #FIM 163 | -------------------------------------------------------------------------------- /exemplos/MessageRules2.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: MessageRules2.sh 4 | # 5 | # XXX SOBRE XXX 6 | # 7 | # O código abaixo demonstra como implementar um mecanismo genérico 8 | # e dinámico de autenticação na validação de regras. 9 | # Os comandos administrativos permitem adicionar e remover permissões 10 | # de usuários sem reinicializar o bot para atualização das regras. 11 | # 12 | # XXX REQUERIMENTOS XXX 13 | # 14 | # O exemplo requer dois arquivos no diretório base onde 15 | # serão inseridos os usuários, são eles: 16 | # 17 | # users - Usuários que tem permissão para chamar ajuda do bot. 18 | # admins - Administradores que podem chamar todos os comandos do bot. 19 | # (Requer no mínimo um usuário para execução dos comandos.) 20 | # 21 | # Obs: os arquivos devem conter um usuário por linha. 22 | # (Comentários são suportados) 23 | # 24 | # Exemplo: 25 | # admin_id # isso é um comentário. 26 | # admin_name # outro comentário. 27 | # # admin // linha ignorada. 28 | 29 | # Importando API 30 | source ShellBot.sh 31 | 32 | # Token do bot 33 | bot_token='' 34 | 35 | # Inicializando o bot 36 | ShellBot.init --token "$bot_token" --return map --monitor 37 | 38 | # Funções 39 | function bot_help() 40 | { 41 | local text 42 | 43 | text=$(cat << _eof 44 | *\U2753 AJUDA \U2753* 45 | 46 | /useradd [] - Adiciona usuário. 47 | /userdel - Remove usuário. 48 | /userlist - lista os usuários cadatrados. 49 | /delall - excluir todas as contas. 50 | /help - Exibe ajuda. 51 | _eof 52 | ) 53 | 54 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 55 | --text "$text" \ 56 | --parse_mode markdown 57 | 58 | return 0 59 | } 60 | 61 | function user_add() 62 | { 63 | if grep -qw "^$2" "$PWD/users"; then 64 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 65 | --reply_to_message_id ${message_message_id[$id]} \ 66 | --text "*\U1F464 $2\n\U26A0 Usuário já existe.*" \ 67 | --parse_mode markdown 68 | else 69 | # Atualiza a base de usuários. 70 | echo "$2 # ${*:3}" >> "$PWD/users" 71 | 72 | # Notificação. 73 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 74 | --reply_to_message_id ${message_message_id[$id]} \ 75 | - --text "*\U1F464 $2\n\U2705 Usuário adicionado com sucesso!!*" \ 76 | --parse_mode markdown 77 | fi 78 | 79 | return 0 80 | } 81 | 82 | function user_del() 83 | { 84 | if grep -qw "^$2" "$PWD/users"; then 85 | # Remove usuário. 86 | sed -i "/^$2 /d" "$PWD/users" 87 | 88 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 89 | --reply_to_message_id ${message_message_id[$id]} \ 90 | - --text "*\U1F464 $2\n\U26D4 Usuário removido com sucesso!!*" \ 91 | --parse_mode markdown 92 | else 93 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 94 | --reply_to_message_id ${message_message_id[$id]} \ 95 | --text "*\U1F464 $2\n\U26A0 Usuário não encontrado.*" \ 96 | --parse_mode markdown 97 | fi 98 | 99 | return 0 100 | } 101 | 102 | function user_list() 103 | { 104 | local user comm header 105 | 106 | header='*\U1F465 USUÁRIOS \U1F465*' 107 | 108 | while read -r user comm; do 109 | # Ignora usuários desativados. 110 | [[ ${user###*} ]] || continue 111 | 112 | text+="\U1F464 [@$user]\n\U1F4CB ${comm##+([# ])}\n\n" 113 | done < "$PWD/users" 114 | 115 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 116 | --reply_to_message_id ${message_message_id[$id]} \ 117 | --text "${header}\n\n${text:-*\U26A0 Nâo há usuários cadastrados.*}" \ 118 | --parse_mode markdown 119 | 120 | return 0 121 | } 122 | 123 | # Regras 124 | # Nega todas requisições de usuários não cadastrados. 125 | ShellBot.setMessageRules --name 'USERS_DENIED' \ 126 | --auth_file "!($PWD/admins,$PWD/users)" 127 | 128 | # Envia ação padrão do bot (digitando...) e continua verificando as regras. 129 | ShellBot.setMessageRules --name 'BOT_ACTION' \ 130 | --bot_action 'typing' \ 131 | --continue 132 | 133 | # Administradores 134 | # 135 | # Obs: O uso da expressão em '--num_args' força o 136 | # comando 'useradd' a suportar 2 ou mais argumentos 137 | # que inclui uma expressão variática para os comentários. 138 | ShellBot.setMessageRules --name 'ADMIN_ADD_USER' \ 139 | --auth_file "$PWD/admins" \ 140 | --command '/useradd' \ 141 | --num_args '[2-9]|[1-9]+([0-9])' \ 142 | --action 'user_add' 143 | 144 | ShellBot.setMessageRules --name 'ADMIN_DEL_USER' \ 145 | --auth_file "$PWD/admins" \ 146 | --command '/userdel' \ 147 | --num_args 2 \ 148 | --action 'user_del' 149 | 150 | ShellBot.setMessageRules --name 'ADMIN_LIST_USERS' \ 151 | --auth_file "$PWD/admins" \ 152 | --command '/userlist' \ 153 | --action 'user_list' 154 | 155 | ShellBot.setMessageRules --name 'ADMIN_DEL_ALL' \ 156 | --auth_file "$PWD/admins" \ 157 | --command '/delall' \ 158 | --exec "> $PWD/users" \ 159 | --bot_reply_message '*\U274C Todos os usuários foram removidos!! \U274C*' \ 160 | --bot_parse_mode markdown 161 | # Usuários 162 | ShellBot.setMessageRules --name 'USER_HELP' \ 163 | --command '/help' \ 164 | --action 'bot_help' 165 | 166 | # Mensagem de erro. 167 | ShellBot.setMessageRules --name 'COMMAND_NOT_FOUND' \ 168 | --bot_reply_message '*\U26A0 Comando não encontrado ou requer argumentos.*' \ 169 | --bot_parse_mode markdown 170 | 171 | # Padrão 172 | while : 173 | do 174 | # Obtem as atualizações 175 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 176 | 177 | # Lista o índice das atualizações 178 | for id in $(ShellBot.ListUpdates) 179 | do 180 | # Inicio thread 181 | ( 182 | # Gerenciar regras 183 | ShellBot.manageRules --update_id $id 184 | 185 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 186 | done 187 | done 188 | #FIM 189 | -------------------------------------------------------------------------------- /exemplos/ReplyKeyboardMarkup.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: ReplyKeyboardMarkup.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" 16 | ShellBot.username 17 | 18 | # Limpa o array que irá receber a estrutura. 19 | unset botao 20 | 21 | # array 22 | # Nota: Cada elemento do array precisa estar entre aspas duplas enquanto 23 | # a atribuição da estrutura entre aspas simples. Caso o uso das aspas duplas 24 | # na atribuição seja necessário para expansão de variáveis, é preciso escapar 25 | # as aspas internas com '\' (contra barra). 26 | # 27 | # Exemplo: 28 | # 29 | # botao=" 30 | # [\"$num1\",\"$num2\",\"$num3\"], 31 | # [\"$num4\",\"$num5\",\"$num6\"], 32 | # [\"$num7\",\"$num8\",\"$num9\"], 33 | # [\"$num0\"] 34 | # " 35 | 36 | # teclado - array 37 | botao=' 38 | ["1","2","3"], 39 | ["4","5","6"], 40 | ["7","8","9"], 41 | ["0"] 42 | ' 43 | 44 | # Cria o teclado, define a configuração de auto ocultação após o uso e salva em 'keyboard1' 45 | keyboard1="$(ShellBot.ReplyKeyboardMarkup --button 'botao' --one_time_keyboard true)" 46 | 47 | while : 48 | do 49 | # Obtem as atualizações 50 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 51 | 52 | # Lista o índice das atualizações 53 | for id in $(ShellBot.ListUpdates) 54 | do 55 | # Inicio thread 56 | ( 57 | # Verifica se a mensagem enviada pelo usuário é um comando válido. 58 | case ${message_text[$id]} in 59 | "/key") # bot comando 60 | # Envia a mensagem anexando o teclado "$keyboard1" 61 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} --text '*Teclado numérico*' \ 62 | --reply_markup "$keyboard1" \ 63 | --parse_mode markdown 64 | ;; 65 | esac 66 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 67 | done 68 | done 69 | #FIM 70 | -------------------------------------------------------------------------------- /exemplos/ReplyKeyboardMarkup2.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: ReplyKeyboardMarkup2.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" --monitor --flush --return map 16 | 17 | while : 18 | do 19 | # Obtem as atualizações 20 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 21 | 22 | # Lista o índice das atualizações 23 | for id in $(ShellBot.ListUpdates) 24 | do 25 | # Inicio thread 26 | ( 27 | # Requisições somente no privado. 28 | [[ ${message_chat_type[$id]} != private ]] && continue 29 | 30 | # Gera o arquivo temporário com base no 'id' do usuário. 31 | CAD_ARQ=/tmp/cad.${message_from_id[$id]} 32 | 33 | # Verifica se a mensagem enviada pelo usuário é um comando válido. 34 | case ${message_text[$id]} in 35 | '/start') 36 | 37 | # Cria e define um botão simples. 38 | btn_ajuda='["❓Ajuda ❓"]' 39 | 40 | # Inicia a conversa com o bot. 41 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 42 | --text "Olá *${message_from_first_name[$id]}* !! em que posso ajudar?" \ 43 | --reply_markup "$(ShellBot.ReplyKeyboardMarkup --button 'btn_ajuda' -o true)" \ 44 | --parse_mode markdown 45 | ;; 46 | '/ajuda'|'❓Ajuda ❓') 47 | 48 | msg='❓*Ajuda* ❓\n\n' 49 | msg+='*Comandos:*\n\n' 50 | msg+='/start - inicia conversão com bot.\n' 51 | msg+='/cadastro - cadastra o usuário.\n' 52 | msg+='/contato - envia informações para contato.\n' 53 | msg+='/ajuda - exibe ajuda.' 54 | 55 | # Envia menu de ajuda. 56 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 57 | --text "$msg" \ 58 | --reply_markup "$(ShellBot.ReplyKeyboardRemove)" \ 59 | --parse_mode markdown 60 | ;; 61 | '/cadastro') 62 | 63 | # Cria o arquivo temporário. 64 | > $CAD_ARQ 65 | 66 | # Primeiro campo. 67 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 68 | --text "Nome:" \ 69 | --reply_markup "$(ShellBot.ForceReply)" 70 | ;; 71 | '/contato') 72 | 73 | btn_contato='' 74 | # Cria e define uma configuração personalizada para cada botão. 75 | ShellBot.KeyboardButton --button 'btn_contato' --line 1 --text '🏠 enviar local' --request_location true 76 | ShellBot.KeyboardButton --button 'btn_contato' --line 2 --text '📞 enviar telefone' --request_contact true 77 | 78 | # Envia o teclado personalizado. 79 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 80 | --text '*Me ajude a encontrá-lo enviando automaticamente sua localização.*' \ 81 | --reply_markup "$(ShellBot.ReplyKeyboardMarkup --button 'btn_contato')" \ 82 | --parse_mode markdown 83 | ;; 84 | /*) # Comando inválido 85 | 86 | # Envia uma mensagem de erro ao usuário e remove o teclado personalizado atual. 87 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 88 | --text '*comando inválido !!*' \ 89 | --reply_markup "$(ShellBot.ReplyKeyboardRemove)" \ 90 | --parse_mode markdown 91 | ;; 92 | esac 93 | 94 | # Verifica se há respostas. 95 | if [[ ${message_reply_to_message_message_id[$id]} ]]; then 96 | 97 | # Analisa a interface de resposta. 98 | case ${message_reply_to_message_text[$id]} in 99 | 'Nome:') 100 | # Salva os dados referentes e envia o próximo campo 101 | # repetindo o processo até a finalização do cadastro. 102 | echo "Nome: ${message_text[$id]}" >> $CAD_ARQ 103 | 104 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 105 | --text 'Endereço:' \ 106 | --reply_markup "$(ShellBot.ForceReply)" # Força a resposta. 107 | ;; 108 | 'Endereço:') 109 | echo "Endereço: ${message_text[$id]}" >> $CAD_ARQ 110 | 111 | # Próximo campo. 112 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 113 | --text 'Cidade:' \ 114 | --reply_markup "$(ShellBot.ForceReply)" 115 | ;; 116 | 'Cidade:') 117 | echo "Cidade: ${message_text[$id]}" >> $CAD_ARQ 118 | 119 | # Próximo campo. 120 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 121 | --text 'Telefone:' \ 122 | --reply_markup "$(ShellBot.ForceReply)" 123 | ;; 124 | 125 | 'Telefone:') 126 | echo "Telefone: ${message_text[$id]}" >> $CAD_ARQ 127 | 128 | # Finaliza o cadastro removendo o teclado personalizado atual. 129 | ShellBot.sendMessage --chat_id ${message_from_id[$id]} \ 130 | --text "✅ *Cadastro realizado com sucesso.* ✅\n\n$(< $CAD_ARQ)" \ 131 | --parse_mode markdown 132 | 133 | # Limpa o arquivo temporário. 134 | > $CAD_ARQ 135 | ;; 136 | esac 137 | fi 138 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 139 | done 140 | done 141 | #FIM 142 | -------------------------------------------------------------------------------- /exemplos/WelcomeBot.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # script: WelcomeBot.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" 16 | ShellBot.username 17 | 18 | # boas vindas 19 | msg_bem_vindo() 20 | { 21 | local msg 22 | 23 | # Texto da mensagem 24 | msg="🆔 [@${message_new_chat_member_username[$id]:-null}]\n" 25 | msg+="🗣 Olá *${message_new_chat_member_first_name[$id]}*"'!!\n\n' 26 | msg+="Seja bem-vindo(a) ao *${message_chat_title[$id]}*.\n\n" 27 | msg+='`Se precisar de ajuda ou informações sobre meus comandos, é só me chamar no privado.`'"[@$(ShellBot.username)]" 28 | 29 | # Envia a mensagem de boas vindas. 30 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 31 | --text "$(echo -e $msg)" \ 32 | --parse_mode markdown 33 | 34 | return 0 35 | } 36 | 37 | while : 38 | do 39 | # Obtem as atualizações 40 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 41 | 42 | # Lista o índice das atualizações 43 | for id in $(ShellBot.ListUpdates) 44 | do 45 | # Inicio thread 46 | ( 47 | # Chama a função 'msg_bem_vindo' se o valor de 'message_new_chat_member_id' não for nulo. 48 | [[ ${message_new_chat_member_id[$id]} ]] && msg_bem_vindo 49 | 50 | # Verifica se a mensagem enviada pelo usuário é um comando válido. 51 | case ${message_text[$id]} in 52 | *) 53 | : 54 | # ... 55 | ;; 56 | esac 57 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 58 | done 59 | done 60 | #FIM 61 | -------------------------------------------------------------------------------- /exemplos/regHandleFunction.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # script: regHandleFunction.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" 16 | ShellBot.username 17 | 18 | # Mensagem de ajuda 19 | exibir_ajuda() 20 | { 21 | msg="Olá *${callback_query_from_username[$id]}* , em que posso ajudar?\n" 22 | msg+="No momento minhas opções são limitadas, mas farei o possível." 23 | 24 | # Envia uma notificação em resposta ao botão pressionado. 25 | ShellBot.answerCallbackQuery --callback_query_id ${callback_query_id[$id]} \ 26 | --text "Ajuda" 27 | # Envia mensagem 28 | ShellBot.sendMessage --chat_id ${callback_query_message_chat_id[$id]} \ 29 | --text "$(echo -e $msg)" \ 30 | --parse_mode markdown 31 | 32 | 33 | # retorno 34 | return 0 35 | } 36 | 37 | # Envia mensagem contendo informações sobre o bot 38 | exibir_info() 39 | { 40 | msg="*Sobre mim*\n\n" 41 | msg+="id: [$(ShellBot.id)]\n" 42 | msg+="username: [@$(ShellBot.username)]\n" 43 | msg+="firstname: [$(ShellBot.first_name)]" 44 | 45 | # Envia uma notificação em resposta ao botão pressionado. 46 | ShellBot.answerCallbackQuery --callback_query_id ${callback_query_id[$id]} \ 47 | --text "Sobre mim" 48 | # Envia mensagem 49 | ShellBot.sendMessage --chat_id ${callback_query_message_chat_id[$id]} \ 50 | --text "$(echo -e $msg)" \ 51 | --parse_mode markdown 52 | 53 | # retorno 54 | return 0 55 | } 56 | 57 | # Botões 58 | # 59 | # [ Ajuda ] 60 | # [ Sobre mim ] 61 | # 62 | # limpa 63 | unset botao1 64 | # Define as configurações e atribui os valores de retorno (callback_data) para cada botão. 65 | # Sempre que um InlineButton é pressionado pelo usuário, o valor definido no parâmetro 'callback_data' 66 | # é retornado e armazenado na variável 'callback_query_data'. 67 | ShellBot.InlineKeyboardButton --button 'botao1' --line 1 --text 'Ajuda' --callback_data 'btn_help' # valor: btn_help 68 | ShellBot.InlineKeyboardButton --button 'botao1' --line 2 --text 'Sobre mim' --callback_data 'btn_about' # varor: btn_about 69 | 70 | # Registra o nome da função associando-a ao valor de 'callback_data'. 71 | # [ ajuda ] -> btn_help -> exibir_ajuda 72 | # [ Sobre mim ] -> btn_about -> exibir_info 73 | ShellBot.regHandleFunction --function exibir_ajuda --callback_data btn_help 74 | ShellBot.regHandleFunction --function exibir_info --callback_data btn_about 75 | 76 | # limpa 77 | unset keyboard1 78 | # Cria o objeto inline_keyboard contendo os elementos armazenados na variável 'botao1' 79 | # É retornada a nova estrutura e armazena em 'keyboard1'. 80 | keyboard1="$(ShellBot.InlineKeyboardMarkup -b 'botao1')" 81 | 82 | while : 83 | do 84 | # Obtem as atualizações 85 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 86 | 87 | # Lista o índice das atualizações 88 | for id in $(ShellBot.ListUpdates) 89 | do 90 | # Inicio thread 91 | ( 92 | # Monitora as funções registradas por 'regHandleFunction'. 93 | # Se o valor de 'callback_query_data' for igual a um valor 94 | # associado a uma função, a mesma é chamada. 95 | ShellBot.watchHandle --callback_data ${callback_query_data[$id]} 96 | 97 | # Verifica se a mensagem enviada pelo usuário é um comando válido. 98 | case ${message_text[$id]} in 99 | "/bot") # bot comando 100 | # Envia a mensagem anexando o teclado "$keyboard1" 101 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} --text '*Inicio*' \ 102 | --reply_markup "$keyboard1" \ 103 | --parse_mode markdown 104 | ;; 105 | esac 106 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 107 | done 108 | done 109 | #FIM 110 | -------------------------------------------------------------------------------- /exemplos/sendMediaGroup.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # script: sendMediaGroup.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" --monitor 16 | ShellBot.username 17 | 18 | # Inicializa a variável onde será anexado as fotos/videos. 19 | album="" 20 | 21 | # Anexando as mídias. 22 | # Fotos (url) 23 | ShellBot.inputMedia --input album --type photo --media 'http://2.bp.blogspot.com/-M53JjEuGjvE/WXM2uL0QpxI/AAAAAAAAI2k/HDEa368-yecsQG7_dgCevxYoIonS4MnmgCK4BGAYYCw/w800/14650669_269510070111655_4132757982135640193_n.png' --caption "SHELL x SCRIPT (blog wallpaper)" 24 | ShellBot.inputMedia --input album --type photo --media 'https://www.ibm.com/developerworks/mydeveloperworks/blogs/752a690f-8e93-4948-b7a3-c060117e8665/resource/BLOGS_UPLOADED_IMAGES/post-50_applinux.jpg' --caption "Família Linux (IBM)" 25 | 26 | # Fotos (ID) 27 | ShellBot.inputMedia --input album --type photo --media 'AgADAQADyqcxGx10kUbF0VrzCBAH-d4n9y8ABAMBhyFEYQ0EO00BAAEC' --caption "ShellBot e os Pinguins de Madagascar." 28 | ShellBot.inputMedia --input album --type photo --media 'AgADAQADy6cxGx10kUZzXYXre8OzfbZrDDAABJKQDsFvckP4RlQAAgI' --caption "Foto do grupo no Telegram: t.me/shellscript_x" 29 | 30 | # Vídeo (ID) 31 | ShellBot.inputMedia --input album --type video --media 'BAADAQADEgADHXSRRgkpayiIdrXjAg' --caption 'MATRIX (Proteção de Tela)' 32 | 33 | while : 34 | do 35 | # Obtem as atualizações 36 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 37 | 38 | # Lista o índice das atualizações 39 | for id in $(ShellBot.ListUpdates) 40 | do 41 | # Inicio thread 42 | ( 43 | # Verifica se a mensagem enviada pelo usuário é um comando válido. 44 | case ${message_text[$id]%%@*} in 45 | /album) # comando 46 | # ação 47 | ShellBot.sendChatAction --chat_id ${message_chat_id[$id]} --action upload_video 48 | 49 | # Envia o álbum contendo as mídias. 50 | ShellBot.sendMediaGroup --chat_id ${message_chat_id[$id]} --media "$album" 51 | ;; 52 | esac 53 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 54 | done 55 | done 56 | #FIM 57 | -------------------------------------------------------------------------------- /exemplos/sendPoll.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # script: sendPoll.sh 4 | # 5 | # Para melhor compreensão foram utilizados parâmetros longos nas funções; Podendo 6 | # ser substituidos pelos parâmetros curtos respectivos. 7 | 8 | # Importando API 9 | source ShellBot.sh 10 | 11 | # Token do bot 12 | bot_token='' 13 | 14 | # Inicializando o bot 15 | ShellBot.init --token "$bot_token" --monitor --return map 16 | 17 | function ajuda() 18 | { 19 | local msg 20 | 21 | msg=$(cat << _eof 22 | \U2753 *AJUDA* \U2753 23 | 24 | /enquete - Publica uma enquete de pesquisa. 25 | /teclado - Envia um botão para criação de enquete. 26 | /tabuada - Publica uma enquete de teste. 27 | /ajuda - Exibe ajuda e sai. 28 | _eof 29 | ) 30 | 31 | ShellBot.sendChatAction --chat_id ${message_chat_id[$id]} --action 'typing' 32 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 33 | --text "$msg" \ 34 | --parse_mode markdown 35 | 36 | return 0 37 | } 38 | 39 | function enquete() 40 | { 41 | # Opções disponíveis da enquete. (Min: 2, Max: 10) 42 | local arr='["Ubuntu", "Debian", "Manjaro", "CentOS", "Slackware"]' 43 | 44 | ShellBot.sendChatAction --chat_id ${message_chat_id[$id]} --action 'typing' 45 | 46 | # Envia uma enquete não anônima, ou seja, registra os usuários que participaram da votação. 47 | ShellBot.sendPoll --chat_id ${message_chat_id[$id]} \ 48 | --question 'Na sua opinião qual é a melhor distro Linux?' \ 49 | --options "$arr" \ 50 | --is_anonymous false \ 51 | --type regular 52 | 53 | return 0 54 | } 55 | 56 | function teclado() 57 | { 58 | local btn='' 59 | local msg=$(cat << _eof 60 | \U203C *Atualmente há um coleção de distribuições Linux para cada perfil de usuário e propósito. Crie uma enquete e saiba a preferência da comunidade entre as mais populares.* \U203C 61 | 62 | _Para começar acesse o teclado abaixo._ \U1F447 63 | _eof 64 | ) 65 | 66 | # Define o botão com a função de criação de enquete. 67 | ShellBot.KeyboardButton --button 'btn' \ 68 | --line 1 \ 69 | --text '\U1F4CB Criar enquete' \ 70 | --request_poll "$(ShellBot.KeyboardButtonPollType --type regular)" 71 | 72 | ShellBot.sendChatAction --chat_id ${message_chat_id[$id]} --action 'typing' 73 | ShellBot.sendMessage --chat_id ${message_chat_id[$id]} \ 74 | --text "$msg" \ 75 | --parse_mode markdown \ 76 | --reply_markup "$(ShellBot.ReplyKeyboardMarkup --button 'btn')" 77 | 78 | return 0 79 | } 80 | 81 | function tabuada() 82 | { 83 | local n ra op num1 num2 opts arr msg 84 | 85 | num1=$((RANDOM%9+1)) # Operando 1 86 | num2=$((RANDOM%9+1)) # Operando 2 87 | ra=$((RANDOM%3+1)) # Posição da resposta correta. 88 | op=('+' '-') # Operador de variação. 89 | 90 | # Gera os resultados. 91 | for n in {0..3}; do 92 | if [[ $n -eq $ra ]]; then 93 | # Correto. 94 | opts[$n]=$((num1*num2)) 95 | else 96 | # Incorreto. 97 | opts[$n]=$(((num1*num2)${op[RANDOM%2]}(RANDOM%9+n))) 98 | fi 99 | done 100 | 101 | # Converte os valores em um array de string. 102 | printf -v arr '"%s",' "${opts[@]}" 103 | printf -v arr '[%s]' "${arr%,}" 104 | 105 | msg=$(cat << _eof 106 | \U2716 TABUADA \U2716 107 | 108 | Vamos avaliar seu conhecimento em matemática. 109 | Quanto é $num1 x $num2? 110 | _eof 111 | ) 112 | # Ação. 113 | ShellBot.sendChatAction --chat_id ${message_chat_id[$id]} --action 'typing' 114 | 115 | # Envia enquete de teste (quiz) definindo a opção correta. 116 | ShellBot.sendPoll --chat_id ${message_chat_id[$id]} \ 117 | --question "$msg" \ 118 | --options "$arr" \ 119 | --is_anonymous false \ 120 | --type quiz \ 121 | --correct_option_id $ra 122 | 123 | return 0 124 | } 125 | 126 | while : 127 | do 128 | # Obtem as atualizações 129 | ShellBot.getUpdates --limit 100 --offset $(ShellBot.OffsetNext) --timeout 30 130 | 131 | # Lista o índice das atualizações 132 | for id in $(ShellBot.ListUpdates) 133 | do 134 | # Inicio thread 135 | ( 136 | case ${message_text[$id]} in 137 | '/enquete') enquete;; 138 | '/tabuada') tabuada;; 139 | '/teclado') teclado;; 140 | '/ajuda') ajuda;; 141 | esac 142 | ) & # Utilize a thread se deseja que o bot responda a várias requisições simultâneas. 143 | done 144 | done 145 | #FIM 146 | --------------------------------------------------------------------------------