I'm a worldbuilding consultant and fanfiction writer for the Pokémon fandom, also work with computers 'n' stuff. Linux user (but not Arch, btw).
I have a Mastodon btw as @VeniaSilente .
@fedia.io
I'm a worldbuilding consultant and fanfiction writer for the Pokémon fandom, also work with computers 'n' stuff. Linux user (but not Arch, btw).
I have a Mastodon btw as @VeniaSilente .
Does it really, practically, impact things?
If people had to obey the law of "every country that has any internet presence", site operators worldwide would have to do such silly things as ban women from using the internet while not sitting right next to their husbands, or who knows what other silly things as per the Sharia. So I don't really see how any such thing is to be taken at anything but grandposturing from boomer political parties, at face value.
Now, if you want to ban Bri'ish IP addresses, your hosting can take care of that. For the most capable ones it's just a flip of a switch. But do consider that in some cases that makes your site worse for everyone else worldwide as such rules are sometimes implemented via privacy-invading systems (eg.: yet another control that makes your site depend on Cloudflare).
I use SQLite to power up lots of stuff I'm working on. It's lightweight, fast, simple and well-documented for small projects — like a Postgres but very local. Saves me from having to deal with containers "just to store data", let alone for moving stuff to other machine where I would also need the permissions to configure and run containers in the first place; whereas all you need to pass SQLite databases along is scp / rsync.
To be fair (and this is something I don't recall being established with or dealt with in the video) you need to at least trust that the backend is there. Currently if "lol CIA AWS" servers are not working, you don't have an option (Advanced Settings or whatever) in Signal to choose another provider, such as say a self-hosted community server.
On the one hand, the French discovered that snails are edible. That takes some guts.
On the other hand, there was their play during WW2, their notorious love for the resurgence of neofascism, and now this.
I wonder how many more screwups before some guillotines are in order.
Also, I continue to live on the edge with the development channel of the kbin repo
So far things have been mostly stable it seems, so: Really thanks for your efforts! Being around the Fediverse these days and being able to use things right after an update from the devel branch gives me something I hope akin to the "I use Arch btw" feel ;)
But, caveat emptor, we are on the development branch of early-in-its-lifecycle open source software.
Living dangerously, eh? You gotta do what you gotta do.
All I can comment ATM is that I'm no longer having the HTTP 500 erros I reported some days ago. Instead the issues I have now seem to do with federation: kbin magazines I'm suscribed to in other servers seem to not be updating (I get a message in Spanish that in English probably translates to something like "warning: this federated magazine is not complete. Explore the full content at [remote magazine link]."). Meaning I can't ATM interact with magazines not in fedia.io since eg.: the posts or comments I want to reply to are not here.
Which leads me to a question I've always had about kbin model of federation but didn't know how to put in words until now: my current understanding is that "federation" is actually the local instance working on an archived copy of the remote instance content and then sending the new content to be synchronized, yes? If so, is there an alternative model or configuration for federation that actually fetches the remote content when it's going to be used rather than local users working over potentially incomplete copies?
I'm getting very "git rebase memes" from the current model, so I thought to ask.
thanks for using Leebra!
go to feed...