DEV Community: jswalker.in

BlackJack - Beta version

jswalker.in — Mon, 29 Jan 2024 05:11:41 +0000

🚀 Free Beta Release of My Blackjack Game (Windows Version)! 🎲

itch store : (Executable) [https://bit.ly/blackjack-itch-io]

Gitlab : (Executable) [https://bit.ly/black-zip]

Hola! Dev.to family,

I hope this post finds you all well! I'm thrilled to share a significant milestone in my journey as a developer. After the successful development of my multiplayer game "You-Better-Run," I've been passionately working on a new project during my spare time - a classic and exciting Blackjack game!

🃏 About the Game:
This Blackjack game is the result of dedication, late-night coding sessions, and a genuine love for creating engaging experiences. It's a project close to my heart, and I'm excited to bring this to the community for a free beta release.
The game features a combo of four card games to beat boredom after long workdays or to boost entertainment levels when feeling exhausted.

Game includes:
    1.Blackjack
    2.Three-Card Brag
    3.Tough Luck
    4.EO : Guess the card is even or odd

You can collect coins even after losing many games and running out of them. Use the free-wheel spin to keep playing the game for free indefinitely.

🎉 Free Beta Version Now Available:
Today, I'm delighted to announce that the beta version of my Blackjack game is now available for free! 🆓 I would love for you to be a part of this journey and experience the game firsthand. Your feedback and suggestions will be invaluable in shaping the future-version.

🔗 How to Access the Beta:
To try out the game, simply from itch.io(Executable) [https://bit.ly/blackjack-itch-io] && Gitlab(Executable)[https://bit.ly/black-zip]. I appreciate your support and can't wait to hear your thoughts!

🙌 Let's Connect:
I'm always open to connecting with fellow developers, gamers, and anyone passionate about the tech and gaming industry. Feel free to connect, share your thoughts!

👉 Stay Updated:
If you're interested in staying updated on the game's development or future projects,lets connect on various Platform.

Linkedin : www.linkedin.com/in/jayesh-sapkale-jswalker
Twitter : https://twitter.com/jswalker_in
Portfolio : https://jswalker.in/its/jayesh

PreFy : Personal Recommendation Engine For YouTube

jswalker.in — Fri, 29 Jan 2021 05:31:55 +0000

Latest hobby project of jswalker called Prefy. A simple choice of own youtube video collection open for the people who might enjoy an unseen fun and elegant video list.

Project-Link : PreFY

Video collection on fly

To make the system more lightweight, I chose Netlify CDN over firebase CLoudstore because of firebase's relatively smaller amount of Read-query and Every query counts the individual Record consumption instead of query hitting counter which is not suitable for me and in other hand Netlfy offers 100GB monthly bandwidth.In the Case of Prefy production nature Netlify suitable for such kind of project where: fewer KBs are used and cached and make room for more new users.

Role of IndexedDB

To handle more user with less consumption of bandwidth(Netlify Bandwidth) the frequent and latest video collection also store in indexedDB which result in no redundant request on refresh.

[Bug Submit]
DM on twitter

Incoming : Web Walkie-Talkie

jswalker.in — Mon, 13 Jul 2020 10:49:26 +0000

The new creation of jswalker called Incoming. An army style communication approach around the world acts like a Radio Transmission over the internet.

Product-Link : Incoming

[Rule]

 1.Remember your codename : Your-Code-Name show in header
 2.Keep your language wise.Anyway its your choice to be gentle.
 3.Radio frequency allotted 5 seconds maximum hold
 4.Call each other by codename
 5.Give time to each user to speak comfortably

[Speaking code style]

 1.To start or check communication use : "Your-Code-Name" Inbound.  E.G. 'Bravo-2' Inbound 
 2.To end of each communication use : 'over'
 3.To ask/send to specific code-name use : Coming 'Opponent-Code-Name'. E.G. 'Coming Charlie'  
 4.To end talk use : "Your-Code-name" 'over and out' E.G. 'Bravo-2 Over and out'

[Bug Submit]
DM on twitter || Dev.to

Crypto Challenge

jswalker.in — Wed, 01 Jul 2020 11:49:20 +0000

This is a simple Crypto-challenge designed for the government to Introduce and crack classified project to fight cyber-war.

First challenge && Tiny-Enigma

You can try and might break code by trial and error basis.

Offbeat

jswalker.in — Mon, 29 Jun 2020 13:47:54 +0000

This is one of my products for the Indian crowd and a little bit for outside of India.But there are good quality videos chosen from Youtube(Embedded).

Project-Link

Status : Rarely update | Nearly dead | Project is old so, Some video(s) might be removed or unavailable

Share your thought !!!

One domain - multiple service-worker up

jswalker.in — Fri, 26 Jun 2020 05:48:09 +0000

What dilemma i faced?

I usually keep working on multiple projects but with full attention on one project at a specific time(Week, Month). But for a minimal update, I usually follow the same procedure that keeps an offline app with a service worker.
If you are a soloprenuer and have a cash crunch at an early stage, you have to deal with multiple apps under one domain.

like I am doing multiple apps(Total 10) with jswalker.in under /its/ tag and 7 with a subdomain.

If you follow approach from this URL.You will get few gotchas in work-cycle.

Service worker activate event


var staticCacheName="appname_version_1";
self.addEventListener('activate', function(event) {
  var cacheWhitelist = [staticCacheName];

  event.waitUntil(
    caches.keys().then(function(keyList) {
      return Promise.all(keyList.map(function(key) {
        if (cacheWhitelist.indexOf(key) === -1) {
           console.log("Cache delete : "+key);
           return caches.delete(key);
        }

      }));

    })
  );

Root Cause of problem

If we use previous approach We will face no problem and no other cache version will be affected of sub domain's service worker.

But if you use the same domain with dynamic URLs like: /its/amazing and its/sweeper as different Progressive web app.Previous service-worker strategy makes your Eco-System a little bit vulnerable at the offline stage.

It will clear every cache-list except current app-version.In that case if one of your app got update it will remove all caches(10 APP cache) it means /first-app,/second-app cache will also got removed.But service worker still not Unregister from browser so now network request of PWA not found in caches.keys() and make request over Network not from Service-Worker.

How to resolve?

var staticCacheName='appname_version_2';
self.addEventListener('activate', function(event) {

  var static_cache_prefix = staticCacheName.substring(0,staticCacheName.indexOf("_"));

  event.waitUntil(
    caches.keys().then(function(keyList) {
      return Promise.all(keyList.map(function(key) {

        if (key.indexOf(static_cache_prefix) > -1 && key!=staticCacheName) { 
           console.log("Cache delete : "+key);
           return caches.delete(key);
        }

      }));

    })
  );
});

What you will achieve?

The above strategy will check appname in cache list AKA caches.keys().Now it will only remove cache of specific app(separated by URL) with old version and all other related app cache will intact along with new version of updated PWA.

Ladies && Gentlemen please welcome PeerCynk

jswalker.in — Wed, 24 Jun 2020 23:05:09 +0000

I am here to present my latest Platform built on peer-to-peer technology for a Web-Community to exchange a resource in a pure peer-to-peer fashion.
Beta version has limited Access-token for Early-access users.

Checkout Platform: Platform | it is a PWA,so accessible both in mobile-web/Desktop-web

Please do read White-paper : White-Paper

Keep patience with Early Access, It will grow and will become interesting once user-base grow and start contribute on the platform.

So join and exchange information/resources if you have good intentions.

Any query/Bug Report DM on dev.to https://dev.to/jswalker_in || DM on twitter : https://twitter.com/jswalker_in

If you love WebRTC or Fan of Peer-To-Peer ideology this platform is for you.

Note:I have Teeny-Tiny server so please forgive me if server meltdown few time.In the meantime please do read White-Paper

I have seen three Hype-Cycle.

jswalker.in — Sat, 20 Jun 2020 01:48:32 +0000

I have seen/feel/sense three Hype-Cycle in my tech-life(2010-Present).
These are the obvious ones and needn't require the name and also people get angry these days if you speak straight truth on their face so I haven't mentioned the names but you can do a bullseye in a comment.

2013 B

2015-16-17 M

2019 B

In My limited vision, I believe in LID approach
{Logic + Infrastructure + Data-Flow}

Share your views?

Turn your server into a Centralize-Git-Repository.

jswalker.in — Thu, 18 Jun 2020 21:02:08 +0000

GitHub is Great for Open Source projects,
But i don't like GitHub and many other third-party code storage systems when it comes to building a Private-Product which is a highly closed-end system.

I believe in "Your-Code-Your-Responsibility".

Don't Transfer Your Responsibility to others or there will be greater consequences.

If your organization is not involved in open-source development.GitHub is not for you, Private organization must follow own approach to build a product.

Do it hard way to achieve best results,Setting own git server is piece of cake and secure too(If you want your product secure).

Generate key

 ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

Obtain key from user and push into server

Copy local id_rsa for windows (C:/USER/YOUR-USERNAME/.ssh/id_rsa.pub) 
For linux(/root/.ssh/id_ras.pub) 

INTO Remote server /root/.ssh/authorized_keys

Create Directory to store your centralize git server

mkdir git-server
cd git-server
git init --bare

Access this Repo at local client

git clone root@ip-address:/git-server

Additional Note:

If you like to make git more secure keep development and production copy where development copy is accessible to everyone in your organization and production copy allow only via special-mechanism such as Custom platform build in browser where user sync development code into production after checks-and-balance.

For my scenario (Single engineer)
I do not use git at the local/server.Simply use own platform where development code pushes into production mode after stable development channel.

Moral Of the story

IF I can do it as a single engineer, It's a teeny-tiny challenge for the Minimal Team of any organization.
In Case you care about your product.

EOF

How to Read IndexedDB data with order?

jswalker.in — Tue, 16 Jun 2020 21:32:13 +0000

Create Index on timestamp?

var version = 1;

// Access IndexedDB object everytime
function open_idb(obj,callback){
    var flag = 0;
    try {
        if (DBOpenRequest) {
            flag = 1;
        } else {
            flag = 0;
        }
    } catch (err) {
        flag = 0;
    }

    if (flag == 1) {

        //Use older DB object
        var db = DBOpenRequest.result;
        callback(db);
    } else {

        //Create New db object
        DBOpenRequest = indexedDB.open("test_db", version);
    }

    DBOpenRequest.onsuccess = function(event) {
        try {
            var db = DBOpenRequest.result;
            callback(db);
        } catch (err) {
            callback();
        }
    };

    //Set Index
    DBOpenRequest.onupgradeneeded = function(event) {

        var db = event.target.result;

        //This condition will always satisfy
        if(event.oldVersion<1){
          var object_store = db.createObjectStore('test',{keyPath: 'index'});
              object_store.createIndex("index", "index",{unique:false});
              object_store.createIndex("timestamp", "timestamp",{unique:false});
        }

        db.onerror = function(event) {
            console.log('Error loading database.');
        };
    };
};

Executive Function

function push_test_data(obj,callback){
    var index=obj.index;
    var arr=obj.arr;
    var len = arr.length;
    var db=obj.db;



    if(index<len){

        var transaction = db.transaction(['test'], 'readwrite');
        var object_store = transaction.objectStore('test');
        var entry = {index:arr[index].index,timestamp:arr[index].timestamp};

        var request = object_store.put(entry);
            request.onsuccess=function(){
              index=index+1;
              push_test_data({index:index,arr:arr,db:db},callback);
            };

            request.onerror=function(e){
             console.log("Error ");
             console.log(e);
            };      
    }else{
      callback();
    }
};


function order_by(o_){

        var type=o_.type;
        var key=o_.key;


        open_idb({},function(db){

            var transaction = db.transaction(['test'], 'readwrite');
            var object_store = transaction.objectStore('test');
            var request = object_store.index(key).openCursor(null,type);

            var result = [];
            request.onsuccess = function(event) {
                var cursor = event.target.result;
                //console.log(cursor);
                if(cursor){
                    result.push(cursor.value);
                    cursor.continue();
                }else{
                 console.log(":"+type+":");
                 console.log(result);
                }
            };

            request.onerror = function(e) {
              console.log(e);
            };

        });

}

Initial Push Test Data

open_idb({},function(db){
    var arr=[{index:1,timestamp:Date.now()+1},{index:2,timestamp:Date.now()+2}];
    push_test_data({arr:arr,index:0,db:db},function(){

    });

});

Ascending Order


open_idb({},function(db){
   order_by({key:"timestamp",type:"next"});  // For ascending order by timestamp
});

Descending Order


open_idb({},function(db){
   order_by({key:"timestamp",type:"prev"});  // For descending order by timestamp
});

Node.js on port 80 in AWS

jswalker.in — Sun, 14 Jun 2020 11:38:24 +0000

First step to AWS

You'll get the fresh machine after register with AWS.
But they provide a user that does not have the power of root. You can write root command with 'sudo su' but launching Node.js process on 80 port is difficult it always gives you The EACCESS Error. Because of Security reasons (For a Reason).

But as a single/Minimal team, you have a handful and trusted people. So you can make that bet on to get access with root with few adjustments at root level.

:Caution:
Take a backup of every file that you change mostly in /etc folder.

Install Node.js

After installing node.js you'll notice that 80 port already occupied either from Nginx/Apache WebServer.

Steps to configure Node.js on 80 port

Open ssh to ubuntu(AWS) with ssh key(Old one)
Write command "sudo su" to gain sudo power
Write command "nano etc/ssh/sshd_config"
look for PasswordAuthentication tag and change its value 'yes'
Login to root and password (If this is first time set new password with passwd)
Generate new public and private key in putty generator and keep Public-key ssh-header locally.
Paste (Public-Key:ssh-header) from PuttyGen to /root/.ssh/authorized_keys
Keep Private and Public key safe for login via public-key from "ssh-client" such as putty :
{Username:root,Method:Public-key} Add/Import your openSSH private key to your SSH-Client's Client-Key-Manager.
sudo service sshd restart
Login with ssh now
You may disable the password login and only allow ssh key again. By setting "PasswordAuthentication no" (Recommended) or you may still allow root access with password(Not recommended).

Stop preoccupied service on port 80

Before executing node.js process need to kill occupied 80 port process.

sudo fuser -k 80/tcp

Go Ahead

Go-Ahead run Node.js on port 80 it will work.

Tip:

Use Node.js for APIs.Static assets should serve via NginX.Keep use Multiple database layer for smooth operation.

I don't use whatsApp so i built messaging system with PWA for myself.

jswalker.in — Fri, 12 Jun 2020 09:13:03 +0000

 [Ingredients Require]

      * [Node.js + Redis]
      * [Service Worker setting]
      * [Firebase API]
      * [IndexedDB]

[Node.js]

It helps the API wrapper to fulfill the registration and syncing process of user meta info.
I use Redis database to kept every user entry as one key like :

set trunk_user_hash JSON.stringify(_user_info_)

[Service Worker]

The service worker keeps alive(Till lifecycle of the worker in the background) to facilitate with the purpose.

The first one is to keep the cache of an array of files and the second one is to deal with the Firebase web-push Event Listener.

//List all files path that you want to cache in service worker for offline usage.

var filesToCache = ['./js/js-files.js','./css/css-files.js'];

//identify direct URL call not cached URL of service worker

var _direct_url_=['https://fcm.googleapis.com/fcm/send','/api/call'];

var staticCacheName="version_1";

    self.addEventListener('install', event => {
       event.waitUntil(
        caches.open(staticCacheName).then(cache => 
        cache.addAll(filesToCache)).then(self.skipWaiting()
       ));
    });      

    self.addEventListener('activate', function(event) {
       var cacheWhitelist = [staticCacheName];
        event.waitUntil(
          caches.keys().then(function(keyList) {
           return Promise.all(keyList.map(function(key) {
             if (cacheWhitelist.indexOf(key) === -1) {
              return caches.delete(key);
             }
           }));
         }));
     });   

     self.addEventListener('fetch', function(event) {
        var i=0,len=_direct_url_.length;flag = 0;
        for(i=0;i<len;i++){
          if(event.request.url.indexOf(_direct_url_[i])>-1){
             flag=1;
             break;
          }
        }
        if(flag==1){
           return;
        }else{
           event.respondWith(                 
              caches.match(event.request).then(function(response){
               if (response) {
                 return response;
               }
               return fetch(event.request);
              }).catch(function(error) {
            }));
         }
      });

[Firebase Events]

    self.addEventListener('push', function(event) {
      var _json_ = JSON.parse(event.data.text());
      console.log(_json_.data.notification);
      console.log(_json_.data.notification.body);

     //Do your magic here
     //Additional code such as time delay,push into idb

      var body = _json_.data.notification;

      //Show Web-push on device
     event.waitUntil(self.registration.showNotification(
       "Title", 
        {icon: 'Icon-Image',
          badge: 'Small-badge-image',
          actions: [
            {action: 'action_1', title: 'show me'},
            {action: 'action_2', title: 'Dont'}
          ],
          vibrate: [3000], /*Three sercond of beep*/
          body: body.body,
          tag:"Unique or same tag for each notification",
          data: body
     }).then(() => 
       self.registration.getNotifications()).then(notifications=>{
          var msg_body={}; // Feed the payload

         self.clients.matchAll().then((clients) => {
           clients.map((client) => {
                   return client.postMessage(JSON.stringify(msg_body));
               })
         });

         // Push message in indexedDB for conversation history  
          push_msg(payload);
       });
   });

 self.addEventListener('notificationclick', function(event) {
   var eventURL = event.notification;
        event.notification.close();
        event.waitUntil(clients.matchAll({type: "window"     
          }).then(function(clientList) {
          for (var i = 0; i < clientList.length; i++) {
             var client = clientList[i];
               if (clients.openWindow){
         return clients.openWindow("Full-URL");         
           }
      }
    }));
  });

[Firebase]

Include web push standalone js files from firebase : (https://firebase.google.com/docs/web/setup)

On Document-Ready call following snippet to activate Firebase

var messaging = firebase.messaging();
firebase.initializeApp({'messagingSenderId': 'YOUR-SENDER-ID'});

 navigator.serviceWorker.register('./firebase-messaging-sw.js', {
        scope: './'
    }).then(function(registration) {
        console.log('ServiceWorker registerd');
        messaging.useServiceWorker(registration);
    }).then(() => {
        return messaging.requestPermission();
    }).then(() => {
        try{
           return messaging.getToken();
        }catch(err){
           console.log(err);
           return false;    
        }
    }).then((token) => {
        console.log(token); 
    // Store this token locally + into Redis along with user credential and meta data

}).catch((err) => {
        console.log('Messaging Service not working');
        console.log(err);
});

firebase.initializeApp({'messagingSenderId': 'YOUR-SENDER-ID'});

/*Ajax Call to send message to specific user*/

$.ajax({
                    type: 'POST',
                    url: "https://fcm.googleapis.com/fcm/send",
                    headers: {
                        "Authorization": "key=[FIREBASE-AUTH-KEY]",
                        "content-type": "application/json",
                    },
                    contentType: 'application/json',
                    dataType: 'json',                    
                    data: JSON.stringify({
                        body: "....",
                        to: [Receiver Token],
                        collapse_key: "new_messages",
                        data: {
                            "notification": {
                                msg_type: "msg",
                                sent_time:new Date(Date.now()+(new Date().getTimezoneOffset()*60000)).getTime()/1000|0,
                                timestamp:Date.now(),
                                ttl:30,
                                code:"Sender Code[Name or Codename]",
                                body: "MESSAGE BODY",
                                title: "Display Name of sender",
                                confirm: "URL FOR Confirm btn[Optional]",
                                decline: "URL FOR Decline btn[Optional]"
                            }
                        },
                        priority: "high"
                    }),
                    success: function(response) {
                      console.log(response);
                    },
                    fail:function(err){
                      console.log(err);
                    } 
             });

[IndexedDB]

Use IndexedDB APIs : If you want to store the messages for a while at client side.

Note:Use IndexedDB code into service worker file so you can manage it easily for transaction.

window.indexedDB = window.indexedDB || window.mozIndexedDB || window.webkitIndexedDB || window.msIndexedDB;
window.IDBTransaction = window.IDBTransaction || window.webkitIDBTransaction || window.msIDBTransaction;
window.IDBKeyRange = window.IDBKeyRange || window.webkitIDBKeyRange || window.msIDBKeyRange;

var FM_DBOpenRequest="";
var db="";



function open_indexeddb(obj,callback){
  FM_DBOpenRequest = indexedDB.open("app-name",1);
  FM_DBOpenRequest.onsuccess = function(event) {
    db = FM_DBOpenRequest.result;
    indexeddbflag=1;
    callback(db);
  };

  FM_DBOpenRequest.onupgradeneeded = function(event) { 
    var db = event.target.result;

        var objectStore = db.createObjectStore('conversation', { keyPath: 'id' });
            objectStore.createIndex("sent_time", "sent_time", {
                unique: false
            });

              if(event.oldVersion<1){
                 /*Create or update object store*/
              }
              if(event.oldVersion<2){
                /*Create or update object store*/
              } 

  };

}

function push_msg(payload){
    /*Store data into object store by put method*/  

      var transaction = db.transaction(['conversation'], 'readwrite');
      var objectStore = transaction.objectStore('conversation');

      var msg_obj={}; /*Add data to push into idb*/
      var request = objectStore.put(msg_obj);
          request.onsuccess = function() {
          };
};

[Additional Tasks]

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

Task
Keep Conversation at client side
Keep friend's token in-Sync locally.
Clear IDB an interval of 24hrs
Allow user to make web-call(WebRTC)

[Advantages]

===========
1.Small footprint and serve the purpose for friends and family.
2.No one will screening/selling your data.
3.Built to serve the purpose quickly with a low memory footprint.
4.My data My Rule.

[Limitations]

1.Firebase is free lunch for us, so sometimes the message got lost in the matrix.
2.Longer in-active users will not awake the device 's background service easily.
3.If the user is not frequent there will be a lot of delay messages.

This is a simple foundation work for any tiny messaging app. If you want to debug or to grasp more please inspect these files: {js/test.js,firebase-messaging-SW.js} from the console

Project Trunk : (https://trunk.jswalker.in)

Product of Jswalker.in
Thank You~~~[Create something that matters] EOF