NFPS / Private New Stalker Middleware v 4.9.27

IPTV Private Server (NFPS)
#7
i think avov could run this see Choose between your Middleware from TVonline+ settings (Nova Middleware or Stalker Middleware)
 
Last edited:
#8
my MAG254 stalker runs after I put iptvprivateserver info....there is no actual stalker application loaded on MAG254. It get loaded after I typed in portal settings means it's coming from server....May be I am wrong.
 
#9
The boxes have firmware that includes the client that interacts with the middleware on the server side. The middleware allow the server people to properly setup their service to be accessed by their endusers. So, unless your firmware gets updated, it will not change if or when the middleware is changed. I guess sometimes client software may be changed in advance of the server/middleware, and hidden features suddenly appear when the server/middleware is updated, but that normally isn't the case.
 
#10
Looking at the picture, I would guess that it is software intended for boxes that have to use KODI to run stalker. My guess would be a side load and independent of KODI on all devices such as windows, linux, android or mac.
 
#11
You are all missing the point. "Middleware" is not installed on your client machines. It is not intended for end users. It looks nice for the server operators, but you end users will not notice it.
 
#12
I think you will find that the 'skins' for the service are in affect pulled down from the backend servers, I.e. the middleware, then these are used by the MAG 250/254 to display on the screen.

So you can change your 'skin' to the others available, cappuccino, digital, emerald, ocean_blue

NFPS is currently running version 4.9.22 of the middleware, latest is 4.9.27

a few images pulled from middleware below etc

View attachment 1151View attachment 1152View attachment 1153View attachment 1154View attachment 1155View attachment 1156View attachment 1157
 
Last edited:
#13
Change log 4.9.27

[*] Fixed the bug localization in the new admin (issue # 6008);

[*] For the correction filters in the new admin user (issue # 6013);

[*] Fixed a list of modules in the user API v2 (issue # 6021);

[*] Fixed sort users in the personal account of the new admin (issue # 6025);

[*] Fixed sort users by creation date (issue # 6027);

[*] Fixed bug authorization applications in and out of the launcher audiokluba (issue # 6037);

[*] Fixed a stats watching TV (issue # 6046);

[*] Fixes in the new admin dashboards for reseller (issue # 6051);

[*] Fixed a token for Flussonic (issue # 6052);

[*] Fixed a problem with the appearance of the window re-authorization (issue # 6076);

[*] New launcher application list now matches the user rate (issue # 6032);

[*] Minor improvements in the new admin (issue # 6034, issue # 6053);

[*] Added ability to clean the complaints in the new admin (issue # 6035);

[*] Added ability to assign the new skin as the default theme and change the theme for a particular user (issue # 6059);

[*] Added mechanism for controlling external applications (installation, delete, update) (issue # 6060);

[*] Added Slovak locale (issue # 6061);

[*] Updated application ex.ua (issue # 6063);

[*] Added the limit for applications megogo - now the application is available only under 1280x720 (issue # 6073);
 
#14
dara said:
You are all missing the point. "Middleware" is not installed on your client machines. It is not intended for end users. It looks nice for the server operators, but you end users will not notice it.
Click to expand...
It all comes down to support if they send out memos the current middlware software will no longer be supported then yes they need to upgrade to the lastest software.
 
Last edited:
#17
dara said:
That's not the case. Client software is not driven by the middleware.
Click to expand...

actually on the mag devices (and STB emulator). once you see the yellow loading bar on blue background, that and everything after you see IS the middleware.. so if and when they upgrade all users will experience the new GUI... the GUI of the middleware is really just a website in done in HTML, you can see that by going to the site in a regular browser, you wont be able to auth, so you will jsut get the STB blocked message. but I have made it past with that thing i showed you that time before the hole was patched.
 
Last edited:
#18
psycon said:
actually on the mag devices (and STB emulator). once you see the yellow loading bar on blue background, that and everything after you see IS the middleware.. so if and when they upgrade all users will experience the new GUI... the GUI of the middleware is really just a website in done in HTML, you can see that by going to the site in a regular browser, you wont be able to auth, so you will jsut get the STB blocked message. but I have made it past with that thing i showed you that time before the hole was patched.
Click to expand...

Exactly! 😎
 
#19
psycon said:
actually on the mag devices (and STB emulator). once you see the yellow loading bar on blue background, that and everything after you see IS the middleware.. so if and when they upgrade all users will experience the new GUI... the GUI of the middleware is really just a website in done in HTML, you can see that by going to the site in a regular browser, you wont be able to auth, so you will jsut get the STB blocked message. but I have made it past with that thing i showed you that time before the hole was patched.
Click to expand...

Isn't that what I said 😀
 
#20
Ok, I'll accept that the middleware may be sending out the GUI, but it better not affect all the other apps that may be hitting it. The GUI is important, but its even more important to actually get the channels from it, but also to work with other apps other than the emus and the MAG.
 
You must log in or register to reply here.
Top Bottom
Back
Menu