I would assume this just relies on the Discord API being read by the bot - and not on having a local discord installed…
I would assume this just relies on the Discord API being read by the bot - and not on having a local discord installed…
You can use Tblock - Or you can check which router they have, and tell them to flash it with FreshTomato
Then their router can service as a raspi with a pihole: https://wiki.freshtomato.org/doku.php/advanced-adblock
Like feathering somebody after tar pitting. I dont know what that would’ve meant. Maybe servers ridiculing an attacker or something
Could be a feature where servers would add your IP to a list, and send it to the clients (like a list somewhere in case of a website)
Then clients would start sending random metasploit-esk requests to those IPS
I’m building a custom search AI as well, but it would be pretty big to host a scihub search LLM.
It says there are 88,343,822 articles. For an AI to work effectively, you’ll have to slice up the articles into paragraphs, so you will probably end up with between 10x to 100x slices. For those slices you’d have to get the embed vector and store it in a Vector database.
One 1536 vector is about 6.15 KB, meaning 54331450530 KB for everything, or 543 GB in vectors
[From the github comment]
The issue I see with the RFC is not wanting to allow users to add tags to ease the burden on moderators. This comes from a lack of users with privileges, so moderators are overworked and need to rely on bots.
If the tags are just kinda “plain old hashtags” - and not something cool like I mentioned in the previous post 😉 -
Possibly you could have a look at how Gazelle handles tags, where it’s just a voting system. For example, this is “Kanye West” https://i.imgur.com/adTe4t8.png - then tags are no longer a boolean yes/no system, but a user-voted system. And then it’s no longer a moderation concern to have to correct tags, and you don’t need “User privileges” to manage the tags either.
It’s just a pretty chaotic system though - you might still want moderators to remove bad tags and/or ban users from creating tags if they’re always adding nonsense.
Could be some point based system like Stackoverflow - users with n points can vote on existing tags, users with n+ points can add their own new tags
Personally I don’t have any problems with it (if that was directed at me) - I’ve added 418 as “unhandled exception code” response to a bunch of applications, so I can easily differentiate whether my application is throwing an error, or whether it’s some middleware gateway AWS io-thing
I was just curious what OP thought about it, since in the early days it wasn’t uncommon to add goofs or easter-eggs into software, but nowadays not done so much… and apparently the “HTTP Working Group” doesn’t like it either… So I was curious whether OP though in hindsight whether it should’ve been added or not
Do you regret adding it, or with the knowledge you have today, would you still add the 418?
Since a bunch of languages have not implemented it, or/and has long discussions about it:
https://github.com/dotnet/runtime/issues/15650
https://github.com/golang/go/issues/21326
https://github.com/nodejs/node/issues/14644
https://github.com/psf/requests/issues/4238
https://github.com/aspnet/HttpAbstractions/issues/915
Removed by mod