#echobot
Explore tagged Tumblr posts
Text
Why Don't You Fix CVE?
Historically when I pointed out problems in anything, I wasn’t the best at offering solutions. Sometimes I simply had none because the problem was complex and the solutions I came up with were problematic themselves. Other times I had ideas, but they were fairly high-level and abstract and I didn’t want to be like the vulnerability disclosers offering the vendor fix ideas ala “sanitize input“.…
0 notes
Text

bored and did one of those "draw yourself" ideas, so i drew echo. it's so different from my usual style but i did draw this by hand while looking at the template hah
any other ideas on what i should do?
2 notes
·
View notes
Photo

Meet Echobot. The boys decided our echo needed an addition. #momlife #unschooling #echo #echobot #awesome #boys https://www.instagram.com/p/CCML-HQpnH2/?igshid=a6rtbxcton0t
0 notes
Photo

"AI CHATBOTS" can improve, reduce costs💲 of customer engagement services. We just published Part 3 of #Tutorial 👨💻 Series, where you will learn 👉 How to Create Multiturn Prompt #ChatBot 🤖 with #Azure Framework SDK C# and #DotNET? - https://bit.ly/3aDuLow ✔️STAY Connected >>> We're going to publish total 5 parts of tutorials to create basic to advance level chatbots. 💬 #ChatbotDevelopment #BotFramework #EchoBots #AI #azuredevops (at Samarpan Infotech) https://www.instagram.com/p/CD_G6fcHzCL/?igshid=9prf5u8tek2z
0 notes
Text
New Echobot Botnet Variant Uses Over 50 Exploits to Propagate
New Echobot Botnet Variant Uses Over 50 Exploits to Propagate
A new variant of Echobot botnet has been spotted to include over 50 exploits leading to remote code execution (RCE) vulnerabilities in various Internet-of-Things devices.
Echobot was discovered in May and analyzed by security researchers at Palo Alto Networks, who found that it incorporated 18 exploits at the time.
A week later, Larry Cashdollar from Akamai published his analysis, where he revea…
View On WordPress
0 notes
Text
Remote Paid Social Specialist (m/f/d) Job at Leadfeeder -Jobsclub
A native/fully fluent German speaker and fluency in English is a must have for this Paid Social Specialist position. We are a remote-first, international SaaS company helping businesses maximise their revenue potential in Europe and the US with our Go-To-Market SaaS Platform. We are the successful merger of Leadfeeder and Echobot, bringing two industry leaders together. What makes us unique? With…
View On WordPress
0 notes
Text
Data Engineer
Leadfeeder is a fast growing international SaaS scale-up. We are on a mission to bring web intelligence into business. Simply put, Leadfeeder helps companies know more about their website visitors, which enables them to convert promising visitors into sales leads. We’re excited to share that Leadfeeder has merged with Echobot, a leading provider of European Sales Intelligence. As a result, we now…
View On WordPress
0 notes
Text
all done, bisexual flag!!
1 note
·
View note
Text
I....
really don’t like the “Reblog if you’re against X” kind of posts.
Because, yes, I’m against homophobia and rape in all its forms with all its victims, I’m against the stupid deportations and blatant racism going on, I’m against climate denial, all that. But at the same time...
“Reblog if you’re against! And if you don’t, you’re no true follower of mine.”
But I’m a quiet sort. I know, it’s a weakness to many... not going out and marching in protests. I could say I have social anxiety and that would be true. And I do vote, I register and vote, in hopes of changing something. And yet...
How many of you followed me for political commentary? I make stories, silly posts. Occasionally deep philosophical ones. I like to think that I, and this blog, are a comfortable retreat, not... not another ‘this is horrible’ in the growing crowd of ‘this is horrible.’ Because yes, life... and a lot of things, they’re awful. So many people are trying to bring down the bad. What’s wrong with wanting to raise up the good?
“Reblog if you’re against!”
But I have nothing to add to the conversation. By the time that post comes across my dash, everything worth saying has been said. There’s no reason for me to reblog. Can’t I just like it? Can’t I just acknowledge it? If I reblog without adding anything, I am nothing more then a mindless echobot. Maybe if I had a thousand followers it would help, but...
“And if you don’t, you’re no true follower of mine.”
I can understand taking a stand. But ‘with me or against me’ is a dangerous route. There’s the third option of ‘I don’t want to get dragged into this.’ Or the fourth of ‘I’ve fought this fight and I’m tired.’ Or the fifth of ‘I don’t even know what this argument is.’ Or, most likely, the sixth: ‘I agree with you, but how is reblogging going to help anything?’ And yet, there’s an implied threat. A social outcasting, if they say nothing on a loud public forum.
“Reblog if you’re against! And if you don’t, you’re no true follower of mine.”
What if they keep their words quiet, helping out from the shadows? What if they’re not comfortable with the eyes of so many anonymous internet viewers? You should fight for what’s right, yes, but in a way that you can fight, and let others fight in the way they can. You should say “This is Wrong!” You should argue your point. Speak up as you can. But to demand agreement... that is to demand service. Those who join must do so willingly.
So I guess... I’ll still do what I can to support the oppressed. I’ll offer fun stories, and friendship, and maybe advice or directions to people who can help. I’m too monetarily unstable to donate money regularly, and while there was a time where I signed petition after petition my e-mail is bloated and I have to par down for my own sanity. I’ll definitely reblog if I can add anything worthwhile to the conversation... Like if the conversation is already worthwhile. Still...
Reblog if you’re against forced reblogs.
And if you don’t... that’s perfectly fine.
23 notes
·
View notes
Photo

"AI CHAT BOTS" One of the trending topic. We just published Part 2 of Tutorial Series, where you will learn 👉 How to Create Welcome Message 💬 Prompt Bot 🤖 with #Azure Bot Framework SDK C# and #DotNET? - https://bit.ly/30xjmTw ✔️STAY Connected >>> We're going to publish total 5 parts of tutorials to create basic to advance level chatbots. #AzureChatbots #Chatbots #EchoBots #AI #AzureDevOps (at Samarpan Infotech) https://www.instagram.com/p/CDjT3_lFKDL/?igshid=lvc20lhlccsr
0 notes
Text
Echobot and Leadfeeder merge, raise $190M in Euro sales tech consolidation play – TechCrunch
Echobot and Leadfeeder merge, raise $190M in Euro sales tech consolidation play – TechCrunch
Sales and marketing has seen a huge boom in the last several years, fueled by developments in user experience and design, innovations around how companies can parse and leverage big data analytics to understand more about their target audiences and tech to connect with them effectively. That’s also led to a profusion of startups and scaling-up mega-businesses in the space — as well as the…

View On WordPress
0 notes
Photo

This is an intro to a social media project I’m working on, although I don’t think it’s of interest to most tumblr users because tumblr doesn’t really do comment threads; not exactly.
Introducing Project "Echommentary"
tl;dr - Echommentary is a multi-site writer/reader with a crosscommenting "echobot" to unify discussion threads between multiple social media sites. Since all comments are echoed to other sites, everyone participates in the same unified discussion.
= = =
ECHOMMENTARY CORE FUNCTIONALITY
With the impending end of Google+, I've looked at various social media alternatives and have decided none are a perfect fit for what I really want. So...I'm rolling my own multi-site writer/reader solution. The features of the core system will include:
1) Echobot python console app uses web scraping or API to load new posts/comments from each source, to local storage. Core functionality is to scrape from your own profile pages, but you can also scrape followed profile pages to local storage.
2) Echobot echos new posts/comments to all other sources, so all followers participate in the same comment threads (rather than separate discussions on each site).
3) Local storage means it's possible to autopost everything to a new social media site/account if desired.
4) Ability to block users via delblock or shadowblock. A delblock auto-deletes comments by a user. A shadowblock simply doesn't echo a user's comments to other sites.
Project Echommentary's primary mission is to solve the problem of interoperability between diaspora, Mastodon, Google+ (while it exists), and other social media sites. It's an open source project so others are invited to help - especially with Python code for various sources.
There are, of course, a lot of products to multipost to many different social media sites, but these are more designed for commercial publicity rather than to foster cohesive community discussion. In particular, each copy of a post on the different social media sites has its own independent comment thread. I find this frustrating, because a lot of the best ideas are developed in comment threads, and only users from the same site will see those comments. Often, I find that one discussion thread on one site will have some interesting comments, while another discussion thread on another site will have other interesting comments. I wish that they could see each others comments!
So, my core idea is a comment echobot. It will take a comment from Sam on G+, and echo it on other sites with something that looks like:
Sam @ GooglePlus: Yeah, I noticed Aunt Cass in the sassy housewives ad. Actually a kind of subtle running theme of the movie that things on the Internet are often not quite true.
This is an "echo" comment, which appears to be made by the echobot user's account, rather than the original account. Unfortunately, this has some issues. For one thing, it may be best for the echo system to be opt-in. By default, everyone is shadowblocked. Their comments are NOT forwarded to other sites. But you could use a pinned post or something to ask folks whether it's okay to add them into the "echommentary" by echoing their comments to other sites.
Another issue - blocking. Let's say Anna wants to block Hans, so she never sees any comments by Hans. The problem is that she follows Elsa, and Elsa's echobot may echo a comment made by Hans on another site. Anna follows Elsa on G+, but Hans follows Elsa on Mastodon. Anna would see a comment on G+ like:
Hans @ mastodon.social: (@ Elsa @ mastodon.social) Hey Anna, chill out, babe!
The problem? This comment is seen on G+ as made by Elsa, not Hans. So Anna can't block these comments without blocking Elsa entirely. Unfortunately, the best solution may be for Anna to ask Elsa to block Hans. Elsa could block Hans with delblocking or shadowblocking; this prevents Hans's comments from being visible to Anna via echoing.
= = =
BEYOND THE CORE
The echobot stores what it scrapes to a SQLite3 database, as well as a static HTML file tree. This file tree is considered a source just like diaspora or Mastodon, but it offers no built in way to write posts or comments. It's mostly just for troubleshooting. Nevertheless, it can be a somewhat useful tool, and you can optionally serve it up with a web server for others to browse.
Far more flexible and powerful is the SQLite3 database, which stores all posts and comments, as well as their echoes (both pending and completed). This database can be accessed and modified by other programs, such as a writer/commenter, and a "universal reader".
My own interest is in a simple blog writer. It would have very basic functionality...just bold, italic, and inline images. This way, I could compose blog entries that would be directly inserted into the SQLite3 database for transmission to all sources. In addition to the basic functionality, I'd have automatic tag addition to include my own personalized hashtags. For example, if I have #myart in the post, it would auto-add #ijkmyart. That way, diaspora users could click on #ijkmyart to see just my own "myart" posts - like a Collection.
With this simple writer, I could compose blog posts offline and then publish them when I'm ready or on a schedule. I'd still go to diaspora or somewhere to actually read and write comments. The big advantage of the writer is that it could be lean and mean - relatively simple to develop and modify.
A universal reader, however, could be a very powerful tool because it uses SQL queries. You could filter things in powerful ways, including blocking users in ways unavailable in the source systems (such as diaspora, which still lets you see comments made by a blocked user on someone else's post). You could filter followees by hashtag or content matches; you could filter out spoilers by hiding (temporarily) content matching a show you haven't caught up on yet. Stuff like that.
With a universal reader, you could define numerous "read only" sources - not your own profile pages, but followee profile pages. Maybe even blog pages also. Maybe even including RSS feeds, and such.
I feel like a universal reader/writer/commenter is a more complex project than a simple blog composer, but it's also something that a lot of people would really want. As such, it's important for me to think about the SQLite database design in a way that accommodates it from the start. In particular, it needs to understand that some sources are read/write, while other sources are read only. The user owned read/write sources are all that's needed for Echommentary's core functionality, but followed read-only sources are critical for universal reader/writer/commenter functionality.
= = =
AND BEYOND ... ?
Project Echommentary could be taken a step further to become its own independent peer-to-peer social media network, by exposing read-only SELECT functionality to a custom port. That way, echobots could directly pull posts/comments from each other's SQLite3 databases. Even with no outside sources, it could be possible to create an independent social media network somewhat similar to USENET - each node connects with a small number of trusted neighbor nodes.
One node connects to another node via an encrypted (ssh) connection, and then each node can send SELECT statements to the other side. Each node can pull new posts and comments. The reason I specify that it goes both ways, is because of the problem of NAT routers. Most users are behind NAT routers, and there's generally no way to connect to a "server" behind a NAT. But a user behind a NAT can connect to a server out there with a true permanent IP address (either standalone or behind a specifically configured router). So, only a small fraction of nodes need to be out there with permanent IP addresses.
Now, this is truly ambitious. But is it even necessary? I hope not. It's not like we desperately need yet another internet protocol "standard". But it's a potential thing to do which might be useful just in case.
= = =
TECH THOUGHTS
The core Echommentary echobot will be a simple Python console program, to make it very portable and easy to develop/run/maintain remotely. Remote troubleshooting can be assisted by running Python's built in http.server on the local storage file tree. But for most users, it will be easiest and best to simply run and maintain it locally. Using SQLite3 makes it possible for savvy users to do a lot of powerful things with the database directly. I do understand that not everyone knows SQL, though.
For the universal writer and reader, I think that a native Python program would be better than web based...but I'm not sure. I feel like it would streamline development to keep most everything Python + SQLite3. Avoiding web based client functionality means avoiding a lot of extra complexity, maybe - and also it could be more readily adapted to mobile iOS/Android versions.
= = =
So, anyone interested in contributing, or just suggesting thoughts? Concerns?
#echommentary #socialmedia #python #sqlite #diaspora
1 note
·
View note
Text
Remote VP of Finance Job at Leadfeeder -Jobsclub
We are a remote-first, international SaaS company helping businesses maximise their revenue potential in Europe and the US with our Go-To-Market SaaS Platform. We are the successful merger of Leadfeeder and Echobot, bringing two industry leaders together. What makes us unique? With origins in Finland and Germany, the country with the highest privacy standards in Europe, Dealfront was born with…
View On WordPress
0 notes
Link
via Twitter https://twitter.com/PatrickCMiller
0 notes
Text
Yeni Echobot 77 Uzak Kod Yürütme Açığı Bulunduruyor
Echobot botnet hala gündem çünkü yeni bir varyant olarak tespit edildi. Çoğu yama yapılmamış IoT cihazları hedef alan artan sayıda istismar görüldü. Bu yaz keşfedilen bir varyant uzaktan kod yürütülmesine izin veren 50'den fazla kullanım içeriyordu. Bir güvenlik araştırmacısı, 77'sinden daha fazla istismarla yeni bir versiyonun ortaya çıktığını fark etti. Sitemizin üniversite öğrencisi gönüllü editörlerine bir kahve ısmarlar mısınız? Echobot karşı koymak için yeni veya zor bir yönteme ihtiyaç yok ancak bütünleştirdiği yararlanmalar ve hedeflenen cihazların çeşitliliği için garip bir durum olarak öne çıkıyor. Mevcut sürümdeki 77 istismar, yönlendiriciler, IP kameralar, VoIP telefonlar, sunum sistemleri, akıllı ev merkezleri, yazılım, veri analitiği platformları, biyometrik tarayıcılar, ağa bağlı depolama sistemleri, termal kameralar gibi ürünler içindir.
Sitemizin üniversite öğrencisi gönüllü editörlerine bir kahve ısmarlar mısınız? Güvenlik araştırmacısı Carlos Brendel yeni Echobot varyantını buldu ve 12 aralıkta Twitter'da açık bir işareti olarak tehlikeye giren 10 farklı cihazda yayılma mekanizmasının nasıl çalıştığını söyledi. Bununla birlikte ikili dosya sistemleri(binary) geçmişte görüldüğünden farklı bir IP adresinde barındırılmaktadır.

Önceki sürümlerde olduğu gibi kötü amaçlı yazılım, Richard adlı bir dosyada açık bir sunucuda bulunmaktadır. Giriş sayısı dışında, yeni yükler listesi öncekinden çok farklı değil. Aşağıdaki resim, güvenlik araştırmacısı tarafından alınan istismarları göstermektedir.
Geçtiğimiz ağustos ayının başlarında Brendel, istismar listesinin savunmasız bir cihazda uzaktan kod çalıştırılmasını sağlayan neredeyse 60 istismarı tespit etmişti. Hedeflenen işlemci mimarilari bakımından kodun yazarı ayrımcılık yapmamış ve ARM / 4/5/6/7, x86, MIPS, PPC, SuperH gibi geniş bir alanı kapsamıştır.
Twitter,Facebook,Linkedln gibi Sosyal Medya Hesaplarımızdan Bizi Takip Etmeyi Unutmayın. Read the full article
0 notes