Same rock here.

I guess that’s right. Although I’m (most likely) not a person of interest for any secret service. But the data could be interesting for marketing and insurance companies.

Thanks.

That is what the article is explaining.

The planned improvements are a good thing. I thought we talked about the status right/ until now.

Also: What does it mean then Meta (the company) isn’t eager to collect this data (anymore)? This doesn’t fit my world view of this company.

I don’t think so. Metadata is unencrypted (i.e. your contacts, who sends messages to whom and how often and when).
Messages itself are encrypted.

Am I wrong?

I’d like to have darkness during daytime. I’m not sure I would pay for it, but I’d like it very much.

but looks like they don’t include a split spacebar, so not for me unfortunately.

You could split it yourself. It’s ceramics after all.

This has to be the most idiotic thing I read this week.

Landgericht Hamburg enters the room to agree with the plaintiff.

Which Page?

lots of dom modifications

That’s good to know. These modifications are needed to replace the style sheet details, I guess?

passes around far too much data between processes.

What does this mean? Do you have a link where I could read up on the details? Thanks.

Maybe. Does it make a big performance difference which css (dark reader or delivered by wiki) is used?

Is it known how the default to dark mode setting is persisted if let’s say a plugin removed all the Wikipedia cookies on window close? A get or post parameter?

Either way it’s a good thing that wiki offers a dark mode.

Dark Reader Plugin already solved that issue.

One aspect is how interesting you are as a target. What would a possible attacker gain by getting access to your services or hosts?

The danger to get hacked is there but you are not Microsoft, amazon or PayPal. Expect login attempts and port scans from actors who map out the internets. But I doubt someone would spend much effort to break into your hosts if you do not make it easy (like scripted automatic exploits and known passwords login attempts easy) .

DDOS protection isn’t something a tiny self hosted instance would need (at least in my experience).

Firewall your hosts, maybe use a reverse proxy and only expose the necessary services. Use secure passwords (different for each service), add fail2ban or the like if you’re paranoid. Maybe look into MFA. Use a DMZ (yes, VLANs could be involved here). Keep your software updated so that exploits don’t work. Have backups if something breaks or gets broken.

In my experience the biggest danger to my services is my laziness. It takes steady low level effort to keep the instances updated and running. (Yes there are automated update mechanisms - unattended upgrades i.e. -, but also downwards compatibility breaking changes in the software which will require manual interactions by me.)

In my opinion it is its limited suitability for (my) common image editing needs. I.e. add a white text with black border to an image.

But these are my requirements. The developers don’t have to cater to them if they don’t want to. I in turn can decide to not use the program or add the features I would like to see myself (It’s the former for me).

That is the way it is.

Edit: The name gimp was never an issue for me. There are far worse.

Let the patch be part of the code for one or two minor releases. Then revert the changes of the patch.

I assume you want to access a self hosted service on your local server from the Internet.

To make the service accessible from the Internet multiple things are required:

• the router can be accessed from the outside. Find your public IP in the router or use a find-my-ip website. Better: do both. This is the address you can use to access your router (or whatever service you choose to expose through it). Side note: If the Ip-adresses of your router and the one of the find- my- ip- site are different it could mean that your provider uses CG-NAT (because ipv4- addresses are scarce, the provider doesn’t give you a real publicly accessible address). This means you can’t access your router from the Internet. Try IPv6 or contact your provider to get a publicly accessible ipv4- address.
• because the above mentioned IP- address of your router might change, dyndns is used. Configure it in your router and test it. Test if the DNS- name you have set up resolves to your ip- address (nslookup or ping it).
• to make your service available to the Internet you need to configure port forwarding in your router (or add your server as exposed host - means all ports are forwarded to the Internet). This means the router passes request to itself on to your internal server. Careful: everybody can access whatever services you expose. Advice: it’s a good idea to use a VPN. Setup a VPN-server in your Lan and only port-forward its port in the router. Connect to the VPN from the outside - Afterwards use the internal services through the vpn- connection.
• scripts and the internal ip: the dyndns name needs to be used instead of the IP. Find a way to make the scripts use that name to resolve it to your external IP.