Those are broader self-hosted platforms. They build apps with Dockerfiles or Buildpacks and run them in containers.
pack is intentionally smaller. It builds your app into a single-file executable, deploys it to your server, gives each deployment a persistent HTTPS URL, and handles ports, routing, and inactive deployments
A quick explanation: “Greytrapping as implemented in spamd puts offenders in a temporary blacklist, dubbed spamd-greytrap, for 24 hours. Twenty-four hours is short enough to not cause serious disruption of legitimate traffic, since real SMTP implementations will keep trying to deliver for a few days at least.”
How does it work?
(From another article linked in this post)..
“We already know that spam senders rarely use a fully compliant SMTP implementation to send their messages. That's why greylisting works. Also, as we noted earlier, not only do spammers send large numbers of messages, they rarely check that the addresses they feed to their hijacked machines are actually deliverable. Combine these facts, and you see that if a greylisted machine tries to send a message to an invalid address in your domain, there is a significant probability that the message is a spam, or for that matter, malware.”
The article includes a youtube video, where an NPC shares facts about the archeological site (i assume backed by knowledge from an LLM).
Pretty cool, I can see this as useful to a lot of different museums or organizations.
It would be interesting for the NPC to ask the player how they wanted information to be delivered- “I’m a hurried. Tourist, keep your responses short”.
“We uncover a systematic failure: LLMs cannot correct errors in their own outputs while successfully correcting identical errors from external sources - a limitation we term the Self-Correction Blind Spot.”
Yes! I’ve even considered finding some extension to just accept every cookie option for every site, so just I’m not hammered with consent dialogs on StackOverflow.
I use multiple browsers for testing, across multiple computers.
Perhaps this fact, along with their consent expiration policy causes the consent dialogs to always show.
“ Globe gores are strips of paper containing printed maps in the sizes and shapes needed for globe construction. The maps can be either terrestrial (showing the earth) or celestial (showing the heavens) and the gores are typically football shaped. The gores can be thought of as pre-assembled building blocks for a globe of a particular size which a globe-maker can quickly utilize to construct a globe without having to spend the time constructing the maps. ”
By “publishing”, it seems authors are limited to distribution inside the ElevenReader app.
They also offer an audio suite:
“Authors can use Studio, our premium audio suite, for fine-grained voice customization, pacing control, and multi-speaker selection.”
And authors can use FindAway Voices (one of the most popular options for sourcing generated voices for audiobooks).
Those are broader self-hosted platforms. They build apps with Dockerfiles or Buildpacks and run them in containers.
pack is intentionally smaller. It builds your app into a single-file executable, deploys it to your server, gives each deployment a persistent HTTPS URL, and handles ports, routing, and inactive deployments