eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

223
active users

#domainname

0 posts0 participants0 posts today

🚀 FastMpay.com – The Future of Fintech Domains! 🚀

In the fast-paced world of fintech, your domain is your brand's first impression. FastMpay.com is short, memorable, and perfect for startups in mobile payments and digital wallets. Discover why it's a smart choice for your brand's SEO and identity. Visit panda-fog.com to order now!

Read more: towfiquls-newsletter.beehiiv.c

Why Use a Country-Level Domain Extension?

Using overseas hosting (outside the United States) is a smart move and something we encourage — it can provide greater privacy, legal protection, and sovereignty over your data.

However, hosting alone is not enough.

Even if you host your website (for example, on a .com) in a country like Germany, while your files and database may be safe, your domain name itself can still be subject to U.S. law. Many domain extensions — including .com, .net, .org, .info, .us, and .edu — are governed by U.S. jurisdiction.

Additionally, many word-based domain extensions — such as .social — are managed by private corporations based in the United States, which can still put your domain name at risk of legal or commercial interference. Corporations can also be easily bought or influenced, unlike sovereign nations. Historically, sovereign nations tend to seek to hold onto their sovereignty — even when they are financially broke or fundamentally broken.

Domain takedowns are rare, but the possibility exists — especially in today's unstable political climate. For example, even close allies like Canada have experienced tension with the U.S., and Donald Trump even tried to instruct Microsoft to discontinue services to Denmark, raising the question: What is "normal" anymore?

" What country level domain name extensions are available for everyone?! "
The following, should be available to anyone to register. However, some (see list) will require a "domain agent" if you do not live or own a business in these countries. Many domain registers are happy to be your "domain agent", but you should check first with the register.

.ai – Anguilla

.am – Armenia

.co – Colombia

.fm – Micronesia

.io – British Indian Ocean Territory

.me – Montenegro

.tv – Tuvalu

.cc – Cocos (Keeling) Islands

.ws – Samoa

.in – India

.to – Tonga

.bz – Belize

.uk – United Kingdom (will need a domain agent)

.de – Germany (will need a domain agent)

.nl – Netherlands

.eu – European Union (will need a domain agent)

.ca – Canada (will need a domain agent)

#Domain #DomainName #Fediverse #ActivityPub #UsJurisdiction

This is how you run a Fedi website outside Us Jurisdiction.

mk.absturztau.be = Domain (.be) name is Belgium, while hosted in Switzerland, and the hosting provider is governed under the laws of Switzerland.

mastodon.au = Domain (.au) name is Australia, while hosted in Australia, and the hosting provider is governed under the laws of Australia.

Remember, Dot Com, Net, Org, Info, Us, and Edu is governed by the United States of America. Most word-based domain names, for example, Dot Social, managed by Corporations within the USA.

#Fediverse #ActivityPub #Mastodon #Misskey #DomainName #Domain #WebHosting

Continued thread

If more people had some good sense, they would use country extension domain names.

But everyone wants that cool domain, for example, random dot social, as opposed to random dot ch.

Corporate America, governed under Us Law, is going to have a lot more oversight on the Internet, and many of you are not paying attention.

#Internet #WorldWideWeb #Oversight #DomainName #Domain #DomainRegistration #Register #Website

Replied in thread

@sophieschmieg @neilmadden

IMO we need to stop coming up with algorithms to securely store "derivatives" of typically weak passwords, as

IT WILL FAIL.

From akkadia.org/drepper/SHA-crypt.:

In addition, the produced output for [...] MD5 has a short length which makes it possible to construct rainbow tables.

Please correct me if I'm wrong, but even in 2025 suggesting that a rainbow table is feasible for (lets cut a few bits for MD5 weaknesses) random numbers of 120 bits in length is BS (in order to create FUD).

If I'm right about that, the least bad thing to do is:

1) Everyone should use a password manager (pwmgr) because people simply do not have the ability to come up with a sufficiently strong password that is *unique for each account*, let alone for multiple accounts (sometimes hundreds), to remember them absolutely error-free, and to recall which password was chosen for which account.

Note: IMO password *reuse* currently is the biggest threat. Entering a reused password on a fake (phishing) website may have devastating consequences, because (when a password is reused for multiple accounts) chances are that ALL those accounts are compromised. Note that the complexity and uniqueness of the password are IRELLEVANT. And, what KDF is used on the server, is IRRELEVANT as well.

2) Let the pwngr generate a (cryptographically) random password, as long and with as much entropy as allowed by the server.

3) Use a strong master password and NEVER forget it (typical beginner failure).

4) Make sure the database is backed up in more than one place, and make a backup after each modification.

5) Make sure that the device the password mamager is used on, *never* gets compromised.

6) Double check that https:// is used. Better, make sure to use a browser that blocks http:// connections and warns you (Safari on iOS/iPadOS now supports "Not Secure Connection Warning"). In all browsers such a setting is OFF by default: ENABLE IT!

7) On a mobile device: use "Autofill". The OS then transfers the domain name (shown in the browser's address bar) to the pwmgr. If a matching domain name is *not found* in the pw database, assume that you're on a (fake) phishing website! In that case: DO NOT ATTEMPT TO LOG IN by looking up credentials yourself. Reasons for 7, two examples:
----
fake: circle-ci·com
real: circleci.com
----
fake: lîdl.be
real: lidl.be
----

If people would follow this advice (which is not just mine), even MD5 for storing a one-way derivative of the password on the server would be fine.

HOWEVER: don't use MD5 - because "never use MD5 for whatever" is easier to remember than "don't use MD5 if preimage attacks are possible".

P.S. I'm not a cryptographer (although I'm quite interested in the matter).

Disinformation networks register domain names that are confusingly similar to legitimate media outlets. This allows them to post fake articles that look like they belong to that news outlet and spread this disinformation via social media.

❓How can media outlets defend themselves against domain name abuse❓

Read more in our step-by-step guide ⬇️
disinfo.eu/publications/doppel