#Seppo empowers you to publish short texts (and images yet to come) and to network in the Social Web. By renting commodity web space and dropping a single file. Without being subject to terms and conditions. Without having to fret about small print or tech lore. And without the need for an IT-consultant. But rather having a life.
You must log in or register to comment.
Seppo is old, slightly insulting Australian slang for an American
Whelp, researching a product name ahead of a release really helps to prevent those connotations :D
Seppo is also a common name among old men in Finland.
UK too, particularly common in the forces.(For those unaware it is rhyming slang - seppo = septic tank = yank). Somtimes just “septics” too.
Would that be about equivalent to calling British people Poms?
It comes from rhyming slang “septic tank = yank”.
Cheers :-)
Not quite. Yank would be a closer comparison to Pom.
Seppo is closer to “Pommy bastard” in terms of severity. It can be used in a good natured way, but it’s slightly derogatory.
Got you, thanks :-)
It’s a bit harsher than “Pom” and is rarely used in a positive way, unlike Pom which can be an insult or a term of endearment. I don’t think I’ve ever heard Seppo used in a positive way, now that I think of it.
Thanks :-)
Interesting
I think single account ActivityPub implementations are addressing a weakness of the Fediverse: one’s identity (handle, username) is tied to an instance they have no control over. If that instance shuts down users lose everything. With a single account instance, you take that control back. And since it doesn’t need to scale the architecture can be much simpler and can be deployed to much cheaper infrastructure.
The demo was not straightforward, though. And I didn’t quite get how a user can follow Mastodon users, for example.
So, not super sure what this is or how this works. Is the idea that you run the cgi, it sets up static files, and it responds to AP requests like follows, mentions, boosts and such? I realise lots of people don’t like long docs but I didn’t really understand the use case very well.
I think you’re right. In CGI, web server spawns a process for each incoming request to the CGI app, so the author provide static files for visitors to reduce the overhead.
Edit: here is the repository: https://codeberg.org/seppo/seppo and written in OCaml, so the single file CGI app is a compiled binary.
this is supposed to be simple? i spent a bit digging around this ‘platform’. very odd, seemed very ambiguous to… everything.
“rent” internet space?
They mean these typical shared php webspace you can get very cheaply for hosting Wordpress etc.
whats the benefit of this over wordpress?
Its much simpler and less likely to get hacked ;)
Looks interesting, I find it quite clear.
Just couldn’t find the creds for the demo instance, but could still see what it would look like. Thanks for sharing!
