Jump to content
Bicrypto v4.4.2 + All Plugins ×

Whatsapp Gateway | Multi Device v8.5.1


Magd Almuntaser

Recommended Posts

  • DW Members
55 minutes ago, Enno The Explorer said:

WH Read, WH Typing, WH Reject CAll dan delay untuk webhook tidak berfungsi tuanku @Magd Almuntaser

Fitur-fiturnya bekerja secara normal .. Penundaan dalam hitungan detik .. Jika Anda menulis 1, artinya 1 detik
Jangan menaruh angka yang besar lebih dari 10 detik... karena sistem WhiskeySockets/Baileys tidak menerima lebih dari angka ini... Selain itu, semakin banyak detik yang Anda masukkan, semakin Anda menghambat kerja nodejs untuk melakukan tugas selanjutnya

Apa manfaat yang akan Anda peroleh dari pengaturan 100 detik? Fitur ini hanya memerlukan waktu beberapa detik. Alih-alih sistem merespons Anda pada saat yang sama, sistem akan merespons Anda setelah beberapa detik, seakan-akan sistem sedang menulis. Beginilah cara kerja fitur ini. 👍

52 minutes ago, Dammah Sifla said:

litle bug in new thema.

On new themes in some menus, if you want to change the number it will not respond to changing the number.

image.thumb.png.08dc2be8975222b3ec121173df9496d8.png

And there is a small javascript error in init..

Yes, I focused on it late after the release of the version.. I fixed it and an update will be released for these fixes.

- Fixed the JavaScript language problem (shown in the image you posted).
- Fixed the phonebook.
- Fixed the create campaign.
- Added a new design.

  • Like 1
Link to comment
Share on other sites

  • DW Members

English:
I want to get everyone's opinion...
Now we have reached version 7.0.0.9, and there is no room for version 10. Since the script now contains many modifications, additions, and fixes, and the script's appearance has completely changed both in terms of programming and design, even the original programmer's code has become minimal due to the extensive changes that have occurred. There is no longer a way for the original programmer to bypass these additions, and even if a new version is released from him, I believe it will be outdated.

So, I thought of the following options, and you have the choice:

1- Should I use this version number for the next release (7.0.1.1) and start a new thread? Please note that the original programmer's latest release is 7.0.0, so I cannot use 7.0.1 for his version.

2- Should we ask the admin to change this entire thread to my version?

3- Or should I continue as I am with version numbers like 7.0.0.10?

For your information, if the original programmer releases, let's say, a version numbered 8.0.0, I will immediately change my version number to 8.0.0.1 because it's impossible for our version to remain lower than his release, especially since the script has become something entirely different.


Waiting for everyone's votes since the script concerns everyone.

===================================

Indonesian:
Saya ingin meminta pendapat semua orang...
Sekarang kita telah mencapai versi 7.0.0.9, dan tidak ada ruang untuk versi 10. Karena skrip ini sekarang berisi banyak modifikasi, penambahan, dan perbaikan, dan tampilan skrip telah benar-benar berubah baik dari segi pemrograman maupun desain, bahkan kode pemrogram asli telah menjadi sangat sedikit karena perubahan besar yang telah terjadi. Tidak ada lagi cara bagi pemrogram asli untuk melewati penambahan ini, dan bahkan jika versi baru dirilis, saya percaya itu akan sudah ketinggalan zaman.

Jadi, saya memikirkan beberapa opsi berikut, dan kalian memiliki pilihan:

1- Haruskah saya menggunakan nomor versi ini untuk rilis berikutnya (7.0.1.1) dan memulai thread baru? Perlu dicatat bahwa rilis terbaru dari pemrogram asli adalah 7.0.0, jadi saya tidak dapat menggunakan 7.0.1 untuk versinya.

2- Haruskah kita meminta manajemen untuk memindahkan seluruh thread ini ke versi saya?

3- Atau haruskah saya melanjutkan seperti sekarang dengan nomor versi 7.0.0.10?

Sebagai informasi, jika pemrogram asli merilis, misalnya, versi bernomor 8.0.0, saya akan segera mengubah nomor versi saya menjadi 8.0.0.1 karena tidak mungkin versi kami tetap lebih rendah daripada rilisnya, terutama karena skrip ini telah menjadi sesuatu yang benar-benar berbeda.


Menunggu suara dari semua orang karena skrip ini melibatkan semua orang.
 

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, Magd Almuntaser said:

English:
I want to get everyone's opinion...
Now we have reached version 7.0.0.9, and there is no room for version 10. Since the script now contains many modifications, additions, and fixes, and the script's appearance has completely changed both in terms of programming and design, even the original programmer's code has become minimal due to the extensive changes that have occurred. There is no longer a way for the original programmer to bypass these additions, and even if a new version is released from him, I believe it will be outdated.

So, I thought of the following options, and you have the choice:

1- Should I use this version number for the next release (7.0.1.1) and start a new thread? Please note that the original programmer's latest release is 7.0.0, so I cannot use 7.0.1 for his version.

2- Should we ask the admin to change this entire thread to my version?

3- Or should I continue as I am with version numbers like 7.0.0.10?

For your information, if the original programmer releases, let's say, a version numbered 8.0.0, I will immediately change my version number to 8.0.0.1 because it's impossible for our version to remain lower than his release, especially since the script has become something entirely different.


Waiting for everyone's votes since the script concerns everyone.

===================================

Indonesian:
Saya ingin meminta pendapat semua orang...
Sekarang kita telah mencapai versi 7.0.0.9, dan tidak ada ruang untuk versi 10. Karena skrip ini sekarang berisi banyak modifikasi, penambahan, dan perbaikan, dan tampilan skrip telah benar-benar berubah baik dari segi pemrograman maupun desain, bahkan kode pemrogram asli telah menjadi sangat sedikit karena perubahan besar yang telah terjadi. Tidak ada lagi cara bagi pemrogram asli untuk melewati penambahan ini, dan bahkan jika versi baru dirilis, saya percaya itu akan sudah ketinggalan zaman.

Jadi, saya memikirkan beberapa opsi berikut, dan kalian memiliki pilihan:

1- Haruskah saya menggunakan nomor versi ini untuk rilis berikutnya (7.0.1.1) dan memulai thread baru? Perlu dicatat bahwa rilis terbaru dari pemrogram asli adalah 7.0.0, jadi saya tidak dapat menggunakan 7.0.1 untuk versinya.

2- Haruskah kita meminta manajemen untuk memindahkan seluruh thread ini ke versi saya?

3- Atau haruskah saya melanjutkan seperti sekarang dengan nomor versi 7.0.0.10?

Sebagai informasi, jika pemrogram asli merilis, misalnya, versi bernomor 8.0.0, saya akan segera mengubah nomor versi saya menjadi 8.0.0.1 karena tidak mungkin versi kami tetap lebih rendah daripada rilisnya, terutama karena skrip ini telah menjadi sesuatu yang benar-benar berbeda.


Menunggu suara dari semua orang karena skrip ini melibatkan semua orang.
 

The thread should change to yours IMO

  • Like 1
Link to comment
Share on other sites

I run 7.0.0.9 on cpanel server i run it on node.js like the attached way and also i edited my env like

 APP_URL=http://wp.syslicense.net
WA_URL_SERVER=http://wp.syslicense.net
PORT_NODE=3000

 

and getting error like 

node:net:428
      throw new ErrnoException(err, 'open');
            ^

Error: open EEXIST
    at new Socket (node:net:428:13)
    at process.getStdin [as stdin] (node:internal/bootstrap/switches/is_main_thread:224:17)
    at get (<anonymous>)
    at getOwn (node:internal/bootstrap/realm:206:5)
    at BuiltinModule.syncExports (node:internal/bootstrap/realm:378:31)
    at ModuleWrap.<anonymous> (node:internal/bootstrap/realm:358:17)
    at BuiltinModule.getESMFacade (node:internal/bootstrap/realm:363:17)
    at ModuleLoader.builtinStrategy (node:internal/modules/esm/translators:468:17)
    at callTranslator (node:internal/modules/esm/loader:279:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:285:30) {
  errno: -17,
  code: 'EEXIST',
  syscall: 'open'
}
I am noob at nodejs can anyone please help me how to setup it.

Screenshot 2024-08-26 023257.png

Link to comment
Share on other sites

  • DW Members
17 minutes ago, Shahriar24 said:

I run 7.0.0.9 on cpanel server i run it on node.js like the attached way and also i edited my env like

 APP_URL=http://wp.syslicense.net
WA_URL_SERVER=http://wp.syslicense.net
PORT_NODE=3000

 

and getting error like 

node:net:428
      throw new ErrnoException(err, 'open');
            ^

Error: open EEXIST
    at new Socket (node:net:428:13)
    at process.getStdin [as stdin] (node:internal/bootstrap/switches/is_main_thread:224:17)
    at get (<anonymous>)
    at getOwn (node:internal/bootstrap/realm:206:5)
    at BuiltinModule.syncExports (node:internal/bootstrap/realm:378:31)
    at ModuleWrap.<anonymous> (node:internal/bootstrap/realm:358:17)
    at BuiltinModule.getESMFacade (node:internal/bootstrap/realm:363:17)
    at ModuleLoader.builtinStrategy (node:internal/modules/esm/translators:468:17)
    at callTranslator (node:internal/modules/esm/loader:279:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:285:30) {
  errno: -17,
  code: 'EEXIST',
  syscall: 'open'
}
I am noob at nodejs can anyone please help me how to setup it.

Screenshot 2024-08-26 023257.png

Look to your error:
 

node:net:428
      throw new ErrnoException(err, 'open');
            ^

Error: open EEXIST
    at new Socket (node:net:428:13)
    at process.getStdin [as stdin] (node:internal/bootstrap/switches/is_main_thread:224:17)
    at get (<anonymous>)
    at getOwn (node:internal/bootstrap/realm:206:5)
    at BuiltinModule.syncExports (node:internal/bootstrap/realm:378:31)
    at ModuleWrap.<anonymous> (node:internal/bootstrap/realm:358:17)
    at BuiltinModule.getESMFacade (node:internal/bootstrap/realm:363:17)
    at ModuleLoader.builtinStrategy (node:internal/modules/esm/translators:468:17)
    at callTranslator (node:internal/modules/esm/loader:279:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:285:30) {
  errno: -17,
  code: 'EEXIST',
  syscall: 'open'
}


Port 3000 is open for another operation. Choose another port, such as 3200

Link to comment
Share on other sites

3 minutes ago, Magd Almuntaser said:

Look to your error:
 

node:net:428
      throw new ErrnoException(err, 'open');
            ^

Error: open EEXIST
    at new Socket (node:net:428:13)
    at process.getStdin [as stdin] (node:internal/bootstrap/switches/is_main_thread:224:17)
    at get (<anonymous>)
    at getOwn (node:internal/bootstrap/realm:206:5)
    at BuiltinModule.syncExports (node:internal/bootstrap/realm:378:31)
    at ModuleWrap.<anonymous> (node:internal/bootstrap/realm:358:17)
    at BuiltinModule.getESMFacade (node:internal/bootstrap/realm:363:17)
    at ModuleLoader.builtinStrategy (node:internal/modules/esm/translators:468:17)
    at callTranslator (node:internal/modules/esm/loader:279:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:285:30) {
  errno: -17,
  code: 'EEXIST',
  syscall: 'open'
}


Port 3000 is open for another operation. Choose another port, such as 3200

node:internal/modules/cjs/loader:451
      throw err;
      ^

Error: Cannot find module '/home/syslicense/public_html/wp.syslicense.net/node_modules/@whiskeysockets/baileys/lib/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (node:internal/modules/cjs/loader:443:19)
    at Module._findPath (node:internal/modules/cjs/loader:711:18)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1126:27)
    at Module._load (node:internal/modules/cjs/loader:981:27)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:177:18)
    at Object.<anonymous> (/home/syslicense/public_html/wp.syslicense.net/server/whatsapp.js:16:5)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32) {
  code: 'MODULE_NOT_FOUND',
  path: '/home/syslicense/public_html/wp.syslicense.net/node_modules/@whiskeysockets/baileys/package.json',
  requestPath: '@whiskeysockets/baileys'
}
 

Link to comment
Share on other sites

2 hours ago, Magd Almuntaser said:

English:
I want to get everyone's opinion...
Now we have reached version 7.0.0.9, and there is no room for version 10. Since the script now contains many modifications, additions, and fixes, and the script's appearance has completely changed both in terms of programming and design, even the original programmer's code has become minimal due to the extensive changes that have occurred. There is no longer a way for the original programmer to bypass these additions, and even if a new version is released from him, I believe it will be outdated.

So, I thought of the following options, and you have the choice:

1- Should I use this version number for the next release (7.0.1.1) and start a new thread? Please note that the original programmer's latest release is 7.0.0, so I cannot use 7.0.1 for his version.

2- Should we ask the admin to change this entire thread to my version?

3- Or should I continue as I am with version numbers like 7.0.0.10?

For your information, if the original programmer releases, let's say, a version numbered 8.0.0, I will immediately change my version number to 8.0.0.1 because it's impossible for our version to remain lower than his release, especially since the script has become something entirely different.


Waiting for everyone's votes since the script concerns everyone.

===================================

Indonesian:
Saya ingin meminta pendapat semua orang...
Sekarang kita telah mencapai versi 7.0.0.9, dan tidak ada ruang untuk versi 10. Karena skrip ini sekarang berisi banyak modifikasi, penambahan, dan perbaikan, dan tampilan skrip telah benar-benar berubah baik dari segi pemrograman maupun desain, bahkan kode pemrogram asli telah menjadi sangat sedikit karena perubahan besar yang telah terjadi. Tidak ada lagi cara bagi pemrogram asli untuk melewati penambahan ini, dan bahkan jika versi baru dirilis, saya percaya itu akan sudah ketinggalan zaman.

Jadi, saya memikirkan beberapa opsi berikut, dan kalian memiliki pilihan:

1- Haruskah saya menggunakan nomor versi ini untuk rilis berikutnya (7.0.1.1) dan memulai thread baru? Perlu dicatat bahwa rilis terbaru dari pemrogram asli adalah 7.0.0, jadi saya tidak dapat menggunakan 7.0.1 untuk versinya.

2- Haruskah kita meminta manajemen untuk memindahkan seluruh thread ini ke versi saya?

3- Atau haruskah saya melanjutkan seperti sekarang dengan nomor versi 7.0.0.10?

Sebagai informasi, jika pemrogram asli merilis, misalnya, versi bernomor 8.0.0, saya akan segera mengubah nomor versi saya menjadi 8.0.0.1 karena tidak mungkin versi kami tetap lebih rendah daripada rilisnya, terutama karena skrip ini telah menjadi sesuatu yang benar-benar berbeda.


Menunggu suara dari semua orang karena skrip ini melibatkan semua orang.
 

I vote for version 8.0.0 because is so different. It is better create new thread sir.

sir this morning my nodejs sleeping again also disconnect after i disable my cron sending message every 5 minutes. I think your method not work?

cause i also not see any status on my whatsapp. Version 7.0.0.9

Edited by Unicode
Link to comment
Share on other sites

1 hour ago, Unicode said:

Saya memilih versi 8.0.0 karena sangat berbeda. Lebih baik buat thread baru, Pak.

Pak, pagi ini nodejs saya tidur lagi dan terputus setelah saya menonaktifkan cron yang mengirim pesan setiap 5 menit. Saya pikir metode Anda tidak berfungsi?

karena saya juga tidak melihat status apa pun di whatsapp saya. Versi 7.0.0.9

Apakah ini di vps atau di hosting, jika hosting apakah bisa tertidur juga ya? 

Link to comment
Share on other sites

I am using this wa api with a whmcs module after install its fully working fine but after some time like almost 1 hour now when i am trying it’s showing failed in report and when i click resend button its show user maybe not registered but if i click again its show success and only then its sending msg. What is the problem is it socket idle issue or node js or server side issue. Btw I am using a cpanel hosting.

Link to comment
Share on other sites

27 minutes ago, Ade Prastia said:

Apakah ini di vps atau di hosting, jika hosting apakah bisa tertidur juga ya? 

Di hosting pak.

ternyata belum work ini untuk solusinya, masih harus mengandalkan ping setiap 5 menit kirim pesan ke nomor lain, agar node js selalu bekerja dan tidak tertidur

Link to comment
Share on other sites

1 minute ago, Unicode said:

Di hosting pak.

ternyata belum work ini untuk solusinya, masih harus mengandalkan ping setiap 5 menit kirim pesan ke nomor lain, agar node js selalu bekerja dan tidak tertidur

Can you share the procedure what i need to do for cron and is it safe for my account?

Link to comment
Share on other sites

14 hours ago, Gusik Prasetyo said:

this tutorial to make MPWA autoreply using google sheet plus apps script.

1. make new sheet file using this format (1st row) Keyword, Type, Message, File

you can visit:

https://docs.google.com/spreadsheets/d/1svHPPF3hFyaPfkRxzN1wscR5A5bS21MzcjrH3NO51us/edit?usp=sharing

wsheet.jpg.b1a25516ac39374325eba53c0b89909e.jpg

 

2. then go to Extensions - Apps Script

appsscript.jpg.6ed7295ddac47fc78a363f1d113e9957.jpg

 

3. delete all data on there. copy and paste code bellow. and edit with your own data.

 

function doPost(e) {
    var data =  e.postData.contents;
    var json = JSON.parse(data);
    var number = json['from'];
    var senderMessage = json['message'];
    var file = json['bufferImage'];
    var pesan = senderMessage.toLowerCase();
    var newMessage = pesan.split(" ");
    var searchreply = autoreply(newMessage[0]);
    var type = searchreply[1];
    var messagetosend = searchreply[2];
    var file = searchreply[3];
    if(type == "file"){
        sendWaFile(number, messagetosend, file);
    } else if(type == "button") {
        sendWaButton(number, messagetosend, file);
    } else if(type == "list") {
        sendWaList(number, messagetosend, file);        
    } else {
        sendWaText(number, messagetosend);
    }
}
 
function autoreply(message){
  var sheetUrl = "https://docs.google.com/spreadsheets/d/1svHPPF3hFyaPfkRxzN1wscR5A5bS2jsdhjsdhuheheh/edit?usp=sharing"; //ganti dengan URL sheet kamu
  var sheetfile = SpreadsheetApp.openByUrl(sheetUrl);
  var sheet = sheetfile.getSheetByName("autoreply"); //sesuaikan dengan nama sheet yg d buat
  var data = sheet.getDataRange().getValues()
  var filterData = data.filter(function(keyword){
    if(keyword[0] == message){
      return keyword
      }        
    })
    if(filterData.length>0){
        return filterData[0]
    }
}
 
function sendWaText(number, messagetosend) {
  var APIKey = "Hcu8aDaGnxI6Utf9kWjQsjlpX5taFy" //ganti dengan API
  var sender = "628xxxxxxxxxx"  // ganti nomer HP
  var url = "https://websitekamu/send-message"; //ganti website
  var msgtext = {
    'api_key': APIKey,
    'sender': sender,
    "number": number,
    'message': messagetosend,
    };
  var response = UrlFetchApp.fetch(url, {
    "method": "POST",
    "contentType": "application/json",
    "payload" : JSON.stringify(msgtext),
      });
    Logger.log(response.getContentText());
}
 
//untuk kirim file
function sendWaFile(number, messagetosend, file){
  var APIKey = "Hcu8aDaGnxI6Utf9kWjQsjlpX5taFy" //ganti api
  var sender = "628000000000" // ganti nomer HP
  var url = "https://websitekamu/send-media"; //ganti website
  var msggmbr = {
    "api_key": APIKey,
    "sender": sender,
    "number": number,
    "media_type" : "image",
    "caption": messagetosend,
    "url": file
    }
  var response = UrlFetchApp.fetch(url, {
    "method": "POST",
    "contentType": "application/json",
    "payload" : JSON.stringify(msggmbr),
      });
    Logger.log(response.getContentText());
}
 
//fungsi button tidak bisa
//http://yourhost.com/send-button?sender=nomersender&api_key=yourapikey&number=nomertujuan&url=&footer=optional&message=Halo,ini pesan button&button=button 1,button 2,button 3
function sendWaButton(number, messagetosend, file){
  //var APIKey = "blablabla"
  //var sender = "blablabla"
  var url = "https://alamatwebsite/send-button";
  var msgbut = {
    "sender" : sender,
    "api_key" : APIKey,
    "number" : number,
    "url" : null,
    "footer" : "optional",
    "message" : messagetosend,
    "button" : file
    }
  var response = UrlFetchApp.fetch(url, {
    "method": "POST",
    "contentType": "application/json",
    "payload" : JSON.stringify(msgbut),
    });
    Logger.log(response.getContentText());
}

 

4. in left menus, choose Triggers

triggers.jpg.cf553ed27faf0ebcc6e40f9dffd666e5.jpg

 

5.  Click Add Trigger button in right bottom corner.

6.  make setting like picture bellow. click SAVE.

addtriger.jpg.053a6e898130aefe117adc67f4b4b4e7.jpg

 

7. Click DEPLOY in right top corner.

8. Select type: WEB APP. and make setting like picture. Click DEPLOY to finish it.

autowebhook.jpg.e2e67fa05cab4a05cba124d11bf07979.jpg

 

9. copy url and paste in your MPWA webhook. 

copyurl.jpg.581873383fcb7afc4a375c106be29699.jpg

 

 

@Enno The Explorer @JangE  thanks to @bloserda who teach me about this script.

THANK YOU OOOoommm, thank you semua 🙏🙏

Senantiasa selaras untuk kita semua, segala kebaikan untuk kalian 🙏🙏

Link to comment
Share on other sites

1 hour ago, Shahriar24 said:

Can you share the procedure what i need to do for cron and is it safe for my account?

Just simple. You just need create a cron for 5 minutes to execute api 

http://domain.com/send-message?api_key=1234567890&sender=62888xxxx&number=62888xxxx&message=Hello World

Please make sure your whatsapp account aged. So, whatsapp wont block your account.

 

Link to comment
Share on other sites

1 minute ago, Unicode said:

Just simple. You just need create a cron for 5 minutes to execute api 

http://domain.com/send-message?api_key=1234567890&sender=62888xxxx&number=62888xxxx&message=Hello World

Please make sure your whatsapp account aged. So, whatsapp wont block your account.

 

 

I am using this wa api with a whmcs module after install its fully working fine but after some time like almost 1 hour now when i am trying it’s showing failed in report and when i click resend button its show user maybe not registered but if i click again its show success and only then its sending msg. What is the problem is it socket idle issue or node js or server side issue. Btw I am using a cpanel hosting.

what do you think? What is the reason?
Link to comment
Share on other sites

Just now, Shahriar24 said:

 

 

I am using this wa api with a whmcs module after install its fully working fine but after some time like almost 1 hour now when i am trying it’s showing failed in report and when i click resend button its show user maybe not registered but if i click again its show success and only then its sending msg. What is the problem is it socket idle issue or node js or server side issue. Btw I am using a cpanel hosting.

what do you think? What is the reason?

I dont know the clearer problem about it.

have you try another version of node js?

for my problem i must restart node js everytime it was disconnected

Link to comment
Share on other sites

Just now, Unicode said:

I dont know the clearer problem about it.

have you try another version of node js?

for my problem i must restart node js everytime it was disconnected

I am using nodejs 16 and after how much time it get disconnected in you case?

Link to comment
Share on other sites

5 hours ago, Magd Almuntaser said:

English:
I want to get everyone's opinion...
Now we have reached version 7.0.0.9, and there is no room for version 10. Since the script now contains many modifications, additions, and fixes, and the script's appearance has completely changed both in terms of programming and design, even the original programmer's code has become minimal due to the extensive changes that have occurred. There is no longer a way for the original programmer to bypass these additions, and even if a new version is released from him, I believe it will be outdated.

So, I thought of the following options, and you have the choice:

1- Should I use this version number for the next release (7.0.1.1) and start a new thread? Please note that the original programmer's latest release is 7.0.0, so I cannot use 7.0.1 for his version.

2- Should we ask the admin to change this entire thread to my version?

3- Or should I continue as I am with version numbers like 7.0.0.10?

For your information, if the original programmer releases, let's say, a version numbered 8.0.0, I will immediately change my version number to 8.0.0.1 because it's impossible for our version to remain lower than his release, especially since the script has become something entirely different.


Waiting for everyone's votes since the script concerns everyone.

===================================

Indonesian:
Saya ingin meminta pendapat semua orang...
Sekarang kita telah mencapai versi 7.0.0.9, dan tidak ada ruang untuk versi 10. Karena skrip ini sekarang berisi banyak modifikasi, penambahan, dan perbaikan, dan tampilan skrip telah benar-benar berubah baik dari segi pemrograman maupun desain, bahkan kode pemrogram asli telah menjadi sangat sedikit karena perubahan besar yang telah terjadi. Tidak ada lagi cara bagi pemrogram asli untuk melewati penambahan ini, dan bahkan jika versi baru dirilis, saya percaya itu akan sudah ketinggalan zaman.

Jadi, saya memikirkan beberapa opsi berikut, dan kalian memiliki pilihan:

1- Haruskah saya menggunakan nomor versi ini untuk rilis berikutnya (7.0.1.1) dan memulai thread baru? Perlu dicatat bahwa rilis terbaru dari pemrogram asli adalah 7.0.0, jadi saya tidak dapat menggunakan 7.0.1 untuk versinya.

2- Haruskah kita meminta manajemen untuk memindahkan seluruh thread ini ke versi saya?

3- Atau haruskah saya melanjutkan seperti sekarang dengan nomor versi 7.0.0.10?

Sebagai informasi, jika pemrogram asli merilis, misalnya, versi bernomor 8.0.0, saya akan segera mengubah nomor versi saya menjadi 8.0.0.1 karena tidak mungkin versi kami tetap lebih rendah daripada rilisnya, terutama karena skrip ini telah menjadi sesuatu yang benar-benar berbeda.


Menunggu suara dari semua orang karena skrip ini melibatkan semua orang.
 

saya memilih no 3melanjutkan seperti sekarang dengan nomor versi 7.0.0.10 , sambil menunggu programmer asli merilis nomor v8.0.0

Link to comment
Share on other sites

3 minutes ago, Enno The Explorer said:

saya memilih no 3melanjutkan seperti sekarang dengan nomor versi 7.0.0.10 , sambil menunggu programmer asli merilis nomor v8.0.0

kenapa harus memilih terus dibawah bayang2 mpwa, sedangkan dev asli saja kedapatan logo, theme yang dia gunakan juga milik orang lain?

sedangkan script ini telah dikembangkan menjadi jauh berbeda bahkan memilik fitur yang melebihi versi aslinya dan telah disempurnakan.

Sudah saatnya script MPWA ini berdiri sendiri dengan tangan dingin dari master @Magd Almuntaser

Edited by Unicode
Link to comment
Share on other sites

3 hours ago, Unicode said:

I vote for version 8.0.0 because is so different. It is better create new thread sir.

sir this morning my nodejs sleeping again also disconnect after i disable my cron sending message every 5 minutes. I think your method not work?

cause i also not see any status on my whatsapp. Version 7.0.0.9

node.js harus tetap disadarkan minimal 1 jam sekali agar tetap online 24/7

saya jg tidak melihat perubahan status wa saya setiap 25 detik seperti yang diinfokan tuan @Magd Almuntaser, mungkin maslaahnya pada hal ini.

Link to comment
Share on other sites

Just now, Enno The Explorer said:

node.js harus tetap disadarkan minimal 1 jam sekali agar tetap online 24/7

saya jg tidak melihat perubahan status wa saya setiap 25 detik seperti yang diinfokan tuan @Magd Almuntaser, mungkin maslaahnya pada hal ini.

iya saya juga tidak melihat, alhasil setelah cron saya nonaktifkan node kembali pingsan

Link to comment
Share on other sites

3 minutes ago, Unicode said:

iya saya juga tidak melihat, alhasil setelah cron saya nonaktifkan node kembali pingsan

saya juga melihat sepertinya ada masalah sinkronisasi antara API AI dengan Webhook, klo kita menggunakannya bersamaan maka akan mengganggu kerja Node.js

sehingga node menjadi stuck (tidak bekerja) setelah beberapa menit, saya menyadari ini setelah pertama kali menggunakan Webhook untuk menghubungkan mpwa ke spreadsheet semalam.

tetapi setelah mematikan AI dan hanya menggunakan Webhook, semua berjalan lancar, hanya saja saya masih bingung kenapa WH Typing, WH read dan WH Delaynya tidak berjalan.

untuk Auto Replay, Fitur Delaynya berjalan dengan baik, apabila saya memasukkan 5 atau 10 maka pesan akan muncul 5 atau 10 detik kemudian.

@Magd Almuntaser

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...