#stylobot — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #stylobot, aggregated by home.social.
-
Well Stylo.Bot gets it's 8.7 release tomorrow and with it *the launch of more advanced, paid options*.
Early days but it gets a full live management and analytics dashboard with Postgres support, multi-node hosting support, domain specific management and reporting and DOZENS more features (I suck at marketing I rock at building stuff so...it has stuff!).
Competition all starts at £100/mo + usage charges and per seat etc...
Stylo.Bot is £25 / £50 / month depending if you need the scalability, FREE if you're single site.
30 Day Free Trials too..All self-hosted, ZERO PII is collected, no data leaves your system, adds almost no latency to requests and it runs for EVERY request (sub-millisecond for most requests).
Website is ZERO cookie for non-signed in users, zero tracking beyond the Stylo.Bot fingerprints (which again are zero PII). I take privacy *seriously*.
Lets you eliminate. malicious bots attacking your site, control AI bots by slowing them down (or block or ignore etc)...
Honestly now *for me* the hard bit starts. Not getting too excited when I talk about it!
FOR SALE TOMORROW - FREE TRIALS TOO!
Stylo.Bot
#stylobot #botdetection #self-hosted
-
Well Stylo.Bot gets it's 8.7 release tomorrow and with it *the launch of more advanced, paid options*.
Early days but it gets a full live management and analytics dashboard with Postgres support, multi-node hosting support, domain specific management and reporting and DOZENS more features (I suck at marketing I rock at building stuff so...it has stuff!).
Competition all starts at £100/mo + usage charges and per seat etc...
Stylo.Bot is £25 / £50 / month depending if you need the scalability, FREE if you're single site.
30 Day Free Trials too..All self-hosted, ZERO PII is collected, no data leaves your system, adds almost no latency to requests and it runs for EVERY request (sub-millisecond for most requests).
Website is ZERO cookie for non-signed in users, zero tracking beyond the Stylo.Bot fingerprints (which again are zero PII). I take privacy *seriously*.
Lets you eliminate. malicious bots attacking your site, control AI bots by slowing them down (or block or ignore etc)...
Honestly now *for me* the hard bit starts. Not getting too excited when I talk about it!
FOR SALE TOMORROW - FREE TRIALS TOO!
Stylo.Bot
#stylobot #botdetection #self-hosted
-
Right on time my presentation on Stylo.Bot has been published! https://youtu.be/ZbPLVKxNQIg?si=Z68wenIK0IwJaNr8
-
Right on time my presentation on Stylo.Bot has been published! https://youtu.be/ZbPLVKxNQIg?si=Z68wenIK0IwJaNr8
-
Working on my UX hard to make it simple but getting there.
Opinions of this? #stylobot -
Working on my UX hard to make it simple but getting there.
Opinions of this? #stylobot -
More DevOps for Stylo.Bot this weekend - and addressing some load speed issues; mainly as I don't add caching until way late so it doesn't hide actual perf issues.
Today is Harbor https://goharbor.io/ and Gitea https://git.openharbor.io/
To move my builds locally - GitHub is spendy for the 20+ AoT / Docker builds I need for every release for commercial - and control login with one account etc...
Almost there; my local cluster is the 'until Stylo.Bot pays for hosting' solution...not ideal but it *works*.
Apart from that, one last parasite store - LLMs LOVE slipping them in when you're not looking and only behaviour under load reveals the antipattern.
Stylo.Bot will have it's full trial & paid plans (the first one, multi-node for Enterprise to follow) release NEXT WEEK.
I also need to make some getting started videos (and pay my Tax) in the week ahead...GULP!
-
More DevOps for Stylo.Bot this weekend - and addressing some load speed issues; mainly as I don't add caching until way late so it doesn't hide actual perf issues.
Today is Harbor https://goharbor.io/ and Gitea https://git.openharbor.io/
To move my builds locally - GitHub is spendy for the 20+ AoT / Docker builds I need for every release for commercial - and control login with one account etc...
Almost there; my local cluster is the 'until Stylo.Bot pays for hosting' solution...not ideal but it *works*.
Apart from that, one last parasite store - LLMs LOVE slipping them in when you're not looking and only behaviour under load reveals the antipattern.
Stylo.Bot will have it's full trial & paid plans (the first one, multi-node for Enterprise to follow) release NEXT WEEK.
I also need to make some getting started videos (and pay my Tax) in the week ahead...GULP!
-
Just the slow slog of final tasks to get Stylo.Bot *FOR SALE*...Stylo.Bot 8.5 is out now
https://github.com/scottgal/stylobot/releases/
Too many changes to mention (https://github.com/scottgal/stylobot/blob/main/CHANGELOG.md)
This is the Free-Open-Shared-Source release (FOSS) it's the FULL Stylo.Bot detection engine. Based on mostlylucid.botdetection, 40k downloads and has Docker Images (15k downloads) etc...
Realtime, Adpative, Behavioural Bot Detection which runs on your hardware.
-
Just the slow slog of final tasks to get Stylo.Bot *FOR SALE*...Stylo.Bot 8.5 is out now
https://github.com/scottgal/stylobot/releases/
Too many changes to mention (https://github.com/scottgal/stylobot/blob/main/CHANGELOG.md)
This is the Free-Open-Shared-Source release (FOSS) it's the FULL Stylo.Bot detection engine. Based on mostlylucid.botdetection, 40k downloads and has Docker Images (15k downloads) etc...
Realtime, Adpative, Behavioural Bot Detection which runs on your hardware.
-
New article on an odd architecture I discovered to solve a problem in Stylo.Bot - how do you have a 'live' dashboard over the qwhole system while not bringing your system to a halt if you have many concurrent users.
Signal Shingle: a novel architecture for high-performance ASP.NET multi-widget sites
How do you deliver fast responses for complex dashboards without going crazy? You stop rendering them on the request path.
-
New article on an odd architecture I discovered to solve a problem in Stylo.Bot - how do you have a 'live' dashboard over the qwhole system while not bringing your system to a halt if you have many concurrent users.
Signal Shingle: a novel architecture for high-performance ASP.NET multi-widget sites
How do you deliver fast responses for complex dashboards without going crazy? You stop rendering them on the request path.
-
Just released the StyloExtract packages https://www.nuget.org/packages?q=styloextract&includeComputedFrameworks=true&prerel=true&sortby=relevance
Really for internal use but someone might find them useful.
It's an adaptive HTML to (AI Friendly, structural) Markdown converter designed for extensibility and AoT compatibility.It's the basis of a future StyloBot feature where it will auto generate any upstream page to markdown for AI scrapers automatically. This lets it be FAST!
-
Just released the StyloExtract packages https://www.nuget.org/packages?q=styloextract&includeComputedFrameworks=true&prerel=true&sortby=relevance
Really for internal use but someone might find them useful.
It's an adaptive HTML to (AI Friendly, structural) Markdown converter designed for extensibility and AoT compatibility.It's the basis of a future StyloBot feature where it will auto generate any upstream page to markdown for AI scrapers automatically. This lets it be FAST!
-
Continuing on StyloBot this weekend, staging site showed a regression after my new work on Browser Modes so working through that - code llm drifted away from a core pattern in a big refactor...as it always does.
Core lesson: make your test apps *fail loudly* LLMs are great at papering over spreading, structural cracks in your system.
Distillation phase; not planned work as it's responding to live detection issues. Where a single homan controlled browser sends different headers, request 'shape' for stuff like data / resources / api calls / content.
Each of those is a different 'mode' which NORMALLY bot detectors will just toss the strange differences and merge into a single 'identity based' fingerprint.*However* in StyloBot it can tell them apart because it doesn't throw away these extra discriminators. The bug appeared like multiple clients requesting from the same IP but different 'deceptive' browsers (as I expected all the headers etc). Same goes for AdBlock on/off...it changes what your browser *looks like* by stripping headers etc...
So instead I actually detect these 'modes' and use them to add to discriminaton signal; the proportion and timing cadence is SUPER hard to fake for automation; humans run browsers in 'noisy' computational environments, bots tend to be synthetically 'cleaner'.Anyway that's my weekend, the code llm decided (as it tends to) to layer another parallel system on top of the existing one and it SUCKS - 2s a response as it does a full *db* match against ALL our 'prototyes' each request.
It got the idea but forgot the pattern; I use a single consolidated behaviourally shaped LFU 'transparent' - you don't worry about DB just read and wwrite through the cache and it handles updates etc - LAZY CQRS with none of the guarantees for *super* high speed & in memory.
As usual this is an *odd* archutecture of this sub-feature so the Code LLM (Calude) SMEARS it towards the normative for this.
I told it new in memory stores are not allowed; as it will ALWAYS add these (IMemoryCache) in ASP.NET apps...try and stop it!
So it decided this was a direct to DB operation; it followed one constraint then SKIPPED all the others.
#stylobot #botdetection #botprotection -
Continuing on StyloBot this weekend, staging site showed a regression after my new work on Browser Modes so working through that - code llm drifted away from a core pattern in a big refactor...as it always does.
Core lesson: make your test apps *fail loudly* LLMs are great at papering over spreading, structural cracks in your system.
Distillation phase; not planned work as it's responding to live detection issues. Where a single homan controlled browser sends different headers, request 'shape' for stuff like data / resources / api calls / content.
Each of those is a different 'mode' which NORMALLY bot detectors will just toss the strange differences and merge into a single 'identity based' fingerprint.*However* in StyloBot it can tell them apart because it doesn't throw away these extra discriminators. The bug appeared like multiple clients requesting from the same IP but different 'deceptive' browsers (as I expected all the headers etc). Same goes for AdBlock on/off...it changes what your browser *looks like* by stripping headers etc...
So instead I actually detect these 'modes' and use them to add to discriminaton signal; the proportion and timing cadence is SUPER hard to fake for automation; humans run browsers in 'noisy' computational environments, bots tend to be synthetically 'cleaner'.Anyway that's my weekend, the code llm decided (as it tends to) to layer another parallel system on top of the existing one and it SUCKS - 2s a response as it does a full *db* match against ALL our 'prototyes' each request.
It got the idea but forgot the pattern; I use a single consolidated behaviourally shaped LFU 'transparent' - you don't worry about DB just read and wwrite through the cache and it handles updates etc - LAZY CQRS with none of the guarantees for *super* high speed & in memory.
As usual this is an *odd* archutecture of this sub-feature so the Code LLM (Calude) SMEARS it towards the normative for this.
I told it new in memory stores are not allowed; as it will ALWAYS add these (IMemoryCache) in ASP.NET apps...try and stop it!
So it decided this was a direct to DB operation; it followed one constraint then SKIPPED all the others.
#stylobot #botdetection #botprotection -
StyloBot today; more work on Endpoint UX - for ASP.NET core pack you get the ability to live update endpoint policies. So working out the best UX.
Almso more on the new 'browser mode' work; need to write a blog post on that SEEMS to be anew technique, using the proportion of browser mode changes combined with markov paths to detect subtle timing errors automation lacks.
Even stuff like how a users' browser runs on a desktop OS in terms of xhr, resource requests etc is influenced by other applications loaded, gpu presence etc.
NOT a 'fingerprint' per-se (though it could maliciously be used that way) but a parretn StyloBot can connect to human and bot signatures to find the divergence between the two.
Useful as it's also per-site and likely load dependent so it's a nicely patternable signature - NOT repeatable so not 'this is definietely Scott on his Chrome Mac', that's *identity* no, behaviour; so it *varies* in a human way.
And because StyloBot already watches centroid drift generally, browser modes become another way to detect subtle mismatches: not "is this request bad?" but "does this client’s behavioural movement make sense for the browser it claims to be?" -
StyloBot today; more work on Endpoint UX - for ASP.NET core pack you get the ability to live update endpoint policies. So working out the best UX.
Almso more on the new 'browser mode' work; need to write a blog post on that SEEMS to be anew technique, using the proportion of browser mode changes combined with markov paths to detect subtle timing errors automation lacks.
Even stuff like how a users' browser runs on a desktop OS in terms of xhr, resource requests etc is influenced by other applications loaded, gpu presence etc.
NOT a 'fingerprint' per-se (though it could maliciously be used that way) but a parretn StyloBot can connect to human and bot signatures to find the divergence between the two.
Useful as it's also per-site and likely load dependent so it's a nicely patternable signature - NOT repeatable so not 'this is definietely Scott on his Chrome Mac', that's *identity* no, behaviour; so it *varies* in a human way.
And because StyloBot already watches centroid drift generally, browser modes become another way to detect subtle mismatches: not "is this request bad?" but "does this client’s behavioural movement make sense for the browser it claims to be?" -
NOTE: In preparation for v7 (RTM) of StyloBot with 6.8 the default startup mode changes.
It becomes:
Block malicious Bots
Throttle non-malicious bots
Throttle ALL automation to preserve Human performance (auto rate limiting).You can opt in to the old behaviour with ObserveOnly:true in config
-
NOTE: In preparation for v7 (RTM) of StyloBot with 6.8 the default startup mode changes.
It becomes:
Block malicious Bots
Throttle non-malicious bots
Throttle ALL automation to preserve Human performance (auto rate limiting).You can opt in to the old behaviour with ObserveOnly:true in config
-
Lunchtome over. Endpoint details panel DONE. StyloBot core has some tweaks based on live data training be released as 6.7.0 this weekend.
#stylobot -
Lunchtome over. Endpoint details panel DONE. StyloBot core has some tweaks based on live data training be released as 6.7.0 this weekend.
#stylobot -
Ok work over for the day...ROUGH DAY.
Now to twiddle some StyloBot knobs (discovered more data sources for detection); optional, working on the high risk policies which need that 100%).
THEN more dashboard sytuff and site updates (adding packs)
#stylobot -
Ok work over for the day...ROUGH DAY.
Now to twiddle some StyloBot knobs (discovered more data sources for detection); optional, working on the high risk policies which need that 100%).
THEN more dashboard sytuff and site updates (adding packs)
#stylobot -
A wee bit boring but part of the StyloBot release docs; asnwering the question 'how do you test a probablistic system designed to block automation'
StyloBot Release Series: Testing the Thing That Won't Sit Still
https://www.mostlylucid.net/blog/stylobot-release-nondeterministic-testing#testing #stylobot #probablistic-testing
-
A wee bit boring but part of the StyloBot release docs; asnwering the question 'how do you test a probablistic system designed to block automation'
StyloBot Release Series: Testing the Thing That Won't Sit Still
https://www.mostlylucid.net/blog/stylobot-release-nondeterministic-testing#testing #stylobot #probablistic-testing
-
Two new draft StyloBot articles today:
1. On the upcoming TypeScript SDK for StyloBot (behavourally aware UX for Node / client side)
https://www.mostlylucid.net/blog/typescript-sdk
2. What makes that (and other) SDKs like Go /Caddy support possible..a SideCar mode for StyloBot - low latency low resource StyloBot running alongside any other service.
-
Two new draft StyloBot articles today:
1. On the upcoming TypeScript SDK for StyloBot (behavourally aware UX for Node / client side)
https://www.mostlylucid.net/blog/typescript-sdk
2. What makes that (and other) SDKs like Go /Caddy support possible..a SideCar mode for StyloBot - low latency low resource StyloBot running alongside any other service.
-
OK my StyloBot hours begin (after my two contracts).
Today is getting the new SideCar mode in shape for the draft article.
This is what lets Node, Caddy etc...work with it in high performance modes. So .NET service running over gRPC in 1-2ms for a bot decision.SO also building a small SDK with Typescript (client and server) & Go (Caddy) implementations. And it has a neat 'template' mode which accepts liquid templates and renders HTML controls allowing a hybrid rendering mode.
Makes it really useful beyond .net (so the behavioural UX idea from ASp.NET works everywhere https://www.mostlylucid.net/blog/behaviour-aware-ux.
-
OK my StyloBot hours begin (after my two contracts).
Today is getting the new SideCar mode in shape for the draft article.
This is what lets Node, Caddy etc...work with it in high performance modes. So .NET service running over gRPC in 1-2ms for a bot decision.SO also building a small SDK with Typescript (client and server) & Go (Caddy) implementations. And it has a neat 'template' mode which accepts liquid templates and renders HTML controls allowing a hybrid rendering mode.
Makes it really useful beyond .net (so the behavioural UX idea from ASp.NET works everywhere https://www.mostlylucid.net/blog/behaviour-aware-ux.
-
New article about StyloBot - my FREE realtime adaptive automation blocker and detector.
https://www.mostlylucid.net/blog/stylobot-fingerprint
Trying to put together a *human* level descriptor as I prepare to make it my full time gig (amongst other self-released projects).
-
New article about StyloBot - my FREE realtime adaptive automation blocker and detector.
https://www.mostlylucid.net/blog/stylobot-fingerprint
Trying to put together a *human* level descriptor as I prepare to make it my full time gig (amongst other self-released projects).