💬 What’s taking so long?
So let’s start with what we’re doing right now, currently we are working on rebuilding a essential component that was used in SpamProtectionBot and other services called “PPM” but with a different approach, this new tool is called NCC and will serve more purpose than just a mere package manager, because of the open source aspect this is taking more time as we want users to understand the code, contribute to it and use it not only for our projects but their own as well. This component is coming together nicely and once we have a version of the software we can run with documentation; we will make it open source and post a link to the repository to allow users to inspect and use or improve..
So let’s start with what we’re doing right now, currently we are working on rebuilding a essential component that was used in SpamProtectionBot and other services called “PPM” but with a different approach, this new tool is called NCC and will serve more purpose than just a mere package manager, because of the open source aspect this is taking more time as we want users to understand the code, contribute to it and use it not only for our projects but their own as well. This component is coming together nicely and once we have a version of the software we can run with documentation; we will make it open source and post a link to the repository to allow users to inspect and use or improve..
Nosial
💬 What’s taking so long? So let’s start with what we’re doing right now, currently we are working on rebuilding a essential component that was used in SpamProtectionBot and other services called “PPM” but with a different approach, this new tool is called…
Spam protection bot is a different story, because we want to go for a more decentralized approach and here’s why.
Old user data may have been sold by the current shot callers of Intellivoid or used for other intentions without user permission or notice. And this is bad. So because of this, we don’t want to use any old Intellivoid component or data, instead we want to offer a different solution to prevent a problem like this from happening again rather giving up absolute control over to Nosial and one entity, and that is decentralized federations. Obviously we will host our own database of blacklisted users and so on but the idea would be that users can choose to use another database and host their own instance respectively. Allowing users to choose what federations they wanna use with our bot instance or their own instance. Among this, this is just the beginning of changes we are going to make as we would like to rebrand spam protection bot into a different service that not only covers malicious actors on telegram but on the web, discord, twitch and other services if possible. And once again these components are going to be open source, documented and separated to their respective components so that users can build upon it without for example requiring to have to run a telegram bot.
Like we said before, we don’t want to simply spin up a spam protection bot instance and call it a day, we already know that there’s clones out there that people can use but introduces no new features and doesn’t attempt to fix the current outstanding problems that spam protection bot had during it’s runtime, we want to offer something different, better and something that will not only prove useful in telegram but for the internet as a whole. We hope users understand why we choose to go down the difficult path but the end results should show itself as we want to standout from our current competitors that refuses to be innovative upon an existing project but rather just repeat the same mistakes and call it a day.
We’re not them, we’re different
Old user data may have been sold by the current shot callers of Intellivoid or used for other intentions without user permission or notice. And this is bad. So because of this, we don’t want to use any old Intellivoid component or data, instead we want to offer a different solution to prevent a problem like this from happening again rather giving up absolute control over to Nosial and one entity, and that is decentralized federations. Obviously we will host our own database of blacklisted users and so on but the idea would be that users can choose to use another database and host their own instance respectively. Allowing users to choose what federations they wanna use with our bot instance or their own instance. Among this, this is just the beginning of changes we are going to make as we would like to rebrand spam protection bot into a different service that not only covers malicious actors on telegram but on the web, discord, twitch and other services if possible. And once again these components are going to be open source, documented and separated to their respective components so that users can build upon it without for example requiring to have to run a telegram bot.
Like we said before, we don’t want to simply spin up a spam protection bot instance and call it a day, we already know that there’s clones out there that people can use but introduces no new features and doesn’t attempt to fix the current outstanding problems that spam protection bot had during it’s runtime, we want to offer something different, better and something that will not only prove useful in telegram but for the internet as a whole. We hope users understand why we choose to go down the difficult path but the end results should show itself as we want to standout from our current competitors that refuses to be innovative upon an existing project but rather just repeat the same mistakes and call it a day.
We’re not them, we’re different
👍1
🖌 Branding finale
Hello everyone! This is your resident designer taking up the task to write a huge wall of text.
Yes, as you may have noticed, we already have the branding complete, meaning that after NCC (and documentation, aha!) is done, every single one you will be able to bury the light of the spammer onslaught. But, since NCC is NOT done, here's the bedtime story of how we came up with this futuristic style.
When designing Nosial's branding, we came up with a problem - filling the shoes of a project with a lot of responsibility cannot be done if users don't trust the project with that responsibility. I, personally, trust in our team's capabilities, but you, the user, may not. In order to fix that, we had to go through multiple designs to make one which would make service enjoyable for you without losing out on any of the perks of open source.
Hello everyone! This is your resident designer taking up the task to write a huge wall of text.
Yes, as you may have noticed, we already have the branding complete, meaning that after NCC (and documentation, aha!) is done, every single one you will be able to bury the light of the spammer onslaught. But, since NCC is NOT done, here's the bedtime story of how we came up with this futuristic style.
When designing Nosial's branding, we came up with a problem - filling the shoes of a project with a lot of responsibility cannot be done if users don't trust the project with that responsibility. I, personally, trust in our team's capabilities, but you, the user, may not. In order to fix that, we had to go through multiple designs to make one which would make service enjoyable for you without losing out on any of the perks of open source.
It's true - some of you may have noticed before that open source solutions pale in contrast with Google, Apple, Microsoft and others' solutions. Our team here has set it our responsibility to make sure that we do not make that mistake too.
We've envisioned 9 drafts in total, whilst 2 of them cover specific targets: the end user and public relations; whitepapers and other official stuff. After NCC is complete, all such assets, fonts, etc. will be posted publicly for you to use when covering our products.
As you're reading this post, we're enforcing the new branding in groups and channels under Nosial. We ask you for feedback, because satisfying so many people with the viewpoint of few is very hard. Thanks for your attention :3
Also Amogus reference.
We've envisioned 9 drafts in total, whilst 2 of them cover specific targets: the end user and public relations; whitepapers and other official stuff. After NCC is complete, all such assets, fonts, etc. will be posted publicly for you to use when covering our products.
As you're reading this post, we're enforcing the new branding in groups and channels under Nosial. We ask you for feedback, because satisfying so many people with the viewpoint of few is very hard. Thanks for your attention :3
Also Amogus reference.
🎙 Interlude
Well well well, it has been a while, hasn't it now?
Yes, writing good software is time-consuming. But holy shit, the fact that we'd take so long that the geopolitical situation is *that* close to a nuclear war? That's new.
I'm sure that you want to hear an ETA. We don't have one. I'm sorry, but I don't make software, I make images look good together. NCC, the 'package manager' of our software, is almost complete. When it's fully complete, SPB will follow suit.
My other job is on getting infrastructure ready. Our main nodes are being upgraded to allow for high-availability. Right now the only thing preventing me from getting the second node 'upgraded' with enterprise-grade software is the operating system, but we're planning on getting it done this week.
We are NOT dead. Just alternatively alive.
Well well well, it has been a while, hasn't it now?
Yes, writing good software is time-consuming. But holy shit, the fact that we'd take so long that the geopolitical situation is *that* close to a nuclear war? That's new.
I'm sure that you want to hear an ETA. We don't have one. I'm sorry, but I don't make software, I make images look good together. NCC, the 'package manager' of our software, is almost complete. When it's fully complete, SPB will follow suit.
My other job is on getting infrastructure ready. Our main nodes are being upgraded to allow for high-availability. Right now the only thing preventing me from getting the second node 'upgraded' with enterprise-grade software is the operating system, but we're planning on getting it done this week.
We are NOT dead. Just alternatively alive.
👍3
A fresh new set of eyes joined our team, progress is increasing rapidly in development and we’re organizing things.
Please open Telegram to view this post
VIEW IN TELEGRAM
💅2👍1🎉1
Just a small update, I moved most of the completed repositories from git.n64.cc as a mirror to GitHub, feel free to check them out. The libraries that are missing is because they're not done or even stable.
https://github.com/orgs/nosial/repositories
https://github.com/orgs/nosial/repositories
👍1
🍾 While there's progress, there's progress
We're happy to announce that our submission of our Telegram Bot API implementation has made it's way to the samples listings found on Telegram's bot documentation.
More to come!
https://core.telegram.org/bots/samples
We're happy to announce that our submission of our Telegram Bot API implementation has made it's way to the samples listings found on Telegram's bot documentation.
More to come!
https://core.telegram.org/bots/samples
Announcement 📣
We are excited to share an important update with you. Over the upcoming days, we will commence the process of gathering data from public resources. This pivotal step marks the beginning of our journey to create a comprehensive database, ensuring that when the Spam Protection Bot (or more appropriately, the new federation database standard we’re developing) is launched, we will proudly offer the most effective solution available.
As we embark on this endeavor, we want you to know that your support and trust remain the bedrock of our operations. We understand the importance of transparency, and we assure you that our data collection efforts are carried out responsibly and with utmost respect for privacy.
Together, we strive to create a safer and more secure online environment. using our technologies, We appreciate your continued engagement and look forward to unveiling the Spam Protection Bot & the new federated database standard as the premier solution in the near future.
We’re looking forward to sharing more information with our community once we have something to show!
We are excited to share an important update with you. Over the upcoming days, we will commence the process of gathering data from public resources. This pivotal step marks the beginning of our journey to create a comprehensive database, ensuring that when the Spam Protection Bot (or more appropriately, the new federation database standard we’re developing) is launched, we will proudly offer the most effective solution available.
As we embark on this endeavor, we want you to know that your support and trust remain the bedrock of our operations. We understand the importance of transparency, and we assure you that our data collection efforts are carried out responsibly and with utmost respect for privacy.
Together, we strive to create a safer and more secure online environment. using our technologies, We appreciate your continued engagement and look forward to unveiling the Spam Protection Bot & the new federated database standard as the premier solution in the near future.
We’re looking forward to sharing more information with our community once we have something to show!
🔥5❤4💩3👍2
Hello,
We are currently migrating all our repositories to different Git repositories and implementing support for NCC to add multiple remote repositories for dependencies. This will allow NCC to fall back to another repository if one fails.
Changes will be reflected on all services during the migration period.
Estimated time of completion: unknown
We are currently migrating all our repositories to different Git repositories and implementing support for NCC to add multiple remote repositories for dependencies. This will allow NCC to fall back to another repository if one fails.
Changes will be reflected on all services during the migration period.
Estimated time of completion: unknown
🔔 Global git notifications
You can now stay up-to-date with all the latest changes to our projects in real-time. git notification updates & project notifications are now available @NosialUpdates
You can now stay up-to-date with all the latest changes to our projects in real-time. git notification updates & project notifications are now available @NosialUpdates
Got a working concept for a deep-learning text classification system, this project is still in early development but the idea is that while being open source, it could also benefit those who wishes to run & train their own models with or without cuda support.
This current test is based off a very small dataset as a way to test the the whole program overall, results are promising.
More to come soon
This current test is based off a very small dataset as a way to test the the whole program overall, results are promising.
More to come soon
🔥6