π˜‹π˜ͺ𝘳𝘬

Somewhere between Linux woes, gaming, open source, 3D printing, recreational coding, and occasional ranting.

πŸ”— Me, but elsewhere

πŸ‡¬πŸ‡§ / πŸ‡©πŸ‡ͺ

  • 1 Post
  • 26 Comments
Joined 2Y ago
cake
Cake day: Jun 09, 2023

help-circle
rss

Definitely seeing some people complain about the design changes

The great thing about Mastodon is, that you can freely chose what client you use. If you dislike the original client or web interface, just use Elk, Semaphore, Tusky, etc. whatever you prefer.


Threads has about 200 million monthly users, 33 million daily users. The fediverse has just under 1 million monthly users. Do you really think that 0.5% has any relevance to Meta?

Do you really think they would care about those users when they extend and extinguish the Fediverse?


Everyone can break into my house regardless of having a key or not. I still don’t have my key delivered to them.


A is defederated from Threads, but federates with B. And B federates with Threads. Now Meta can cash out on your data via B.


Daily reminder to defederate from and block threads.net (and optionally all instances that do not do the same).



They slowly start it. When Google killed XMPP they also didn’t do it within a week.



The thing is, Meta does not care about community safety, or moderation, or protecting user data. (Fun fact: they don’t have a data protection agreement, but a data usage agreement.) All they care about is how they can get the most money out of something. Killing off things left and right of their path.

The question is not IF Meta kills the Fediverse but only WHEN they do it.



I cannot see anything bad here. Blocking an actively malicious actor should be the norm.



I know about muenster.im which is a Mastodon instance specific to the city of MΓΌnster. There is also mastodon.hamburg for example.

Those are not local-by-default social media services, though. But I guess it’s easier to find an instance with a local focus instead of β€œJodel but federated”.





To be honest? At β€œInfanty”. In the Fediverse it has relevance, but the impact on the whole Internet is basically zero.


They aren’t. They use the same protocol as a base, and you can have limited interaction, but that’s it.


Why would they undo those changes. They did r/place, that should be enough. And yes, the protests have ended.


lemmy.ml was also down recently for half a day or so. But lemmy.ml was never knwon for being reliable, even it it works fine since some time now.


TIL: you can define different users in your global Git config depending on remote URL
I was in need of using different signing keys (but same mail address) and had a little adventure in the advanced Git documentation I'd like to share. ______________ In your `~/.config/git/config`` remove the [user] section and add this instead: ``` [includeIf "hasconfig:remote.*.url:https://your-remote-url/**"] path = ~/.config/git/user_a ``` And in `~/.config/git/user_a` use this: ``` [user] email = username@example.com name = User Name signingkey = the_16_digit_GPG_key_ID ``` Repeat as often as you need. Just add another `includeIf` section for each of your remote hosts. You can also keep a β€œstub” user section in your `~/.config/git/config` if you always use the same user name and mail address but want to use different keys. ``` [user] email = dirk@0x7be.de name = Dirk ``` In your `includeIf`’d files simply set the signingkey: ``` [user] signingkey = the_16_digit_GPG_key_ID ``` Git automatically combines the two as needed. A minimal working example: File `~/.config/.git/config`: ``` [user] email = username@example.com name = User Name [commit] gpgsign = true [tag] gpgsign = true [includeIf "hasconfig:remote.*.url:https://hostname_A/**"] path = ~/.config/git/config-A [includeIf "hasconfig:remote.*.url:https://hostname_B/**"] path = ~/.config/git/config-B ``` File `~/.config/git/config-A`: ``` [user] signingkey = 16_digit_key_id_used_for_a ``` File `~/.config/git/config-B`: ``` [user] signingkey = 16_digit_key_id_used_for_b ``` Now when you push commits or tags to `hostname_A` or `hostname_B` the correct key is used to sign those (in the example, using same name and mail address) without having to manually edit this for all your local repositories.
fedilink