we removed the instance-wide configuration that blocks emails with HTML parts, putting list owners in full control
This seems like a good omen. I like lots of things about SourceHut but it is definitely pretty opinionated in ways that I don’t always agree with. Some opinions are necessary to make a cohesive product without infinite complexity but I would love to see some more flexibility in the future.
I believe a large part of that is blocking specific ranges and ISPs; I couldn’t access SourceHut from anywhere within my home district, though I could access properly at school. Fortunately this doesn’t seem to affect SSH operations.
Glad to see improvements to the dev workflow, I tried setting up a local sourcehut instance a couple years ago and the tangle of repositories and dependencies was frustrating.
I wish all of the services were just in a single repository that was capable of building each service binary separately.
Why? Now this story will be hidden for everyone who filters on the ai tag… but the story isn’t primarily about AI (it just mentions bots at one point).
I enjoyed reading this but I would have missed it if it was tagged ai when it was submitted.
This seems like a good omen. I like lots of things about SourceHut but it is definitely pretty opinionated in ways that I don’t always agree with. Some opinions are necessary to make a cohesive product without infinite complexity but I would love to see some more flexibility in the future.
It’d be amazing to know how they combated the ai scrapers.
Unfortunately, measures like that are usually kept secret if only for the little respite they bring via obscurity.
I believe a large part of that is blocking specific ranges and ISPs; I couldn’t access SourceHut from anywhere within my home district, though I could access properly at school. Fortunately this doesn’t seem to affect SSH operations.
I did spot some trapdoor / tarpit links on a code base the other day.
Marked as something like “Do not Click”. I suspect the text of such links may have to change in future…
They will be marked with “Free training data inside!” or similar.
This was a surprisingly enjoyable and interesting read :)
Pleroma who once had an update mentioning a feature with
and I use that all the time 😉
Glad to see improvements to the dev workflow, I tried setting up a local sourcehut instance a couple years ago and the tangle of repositories and dependencies was frustrating.
I wish all of the services were just in a single repository that was capable of building each service binary separately.
Please, add “ai” tag :)
Why? Now this story will be hidden for everyone who filters on the
aitag… but the story isn’t primarily about AI (it just mentions bots at one point).I enjoyed reading this but I would have missed it if it was tagged
aiwhen it was submitted.