You all get it totally wrong, it’s not part of enshittification, they add the landingpage so you can securely check where tue link is going…
And if there’s a landing page, why not use it to show you great deals…would be sad to not use that real estate
That’s \s by the way
Unfortunately, the availability of “one time purchase” is not a guarantee anymore as more and more devs have killed existing versions sold with perpetual licences.
What helps a lot for apps with multiple config files:
Probably a bit more polished UX (especially for not too tech-savy people)
but I’d say the biggest difference is integrated multidevice support, either via their cloud or selfhosted…
In some Linux distributions it blocks you from installing system packages via pip, often there are then packages which can be installed via your distros package manager.
With arch for example:
sudo pacman -S python-'package'
Or, as others mentioned using venv.
You should just have received a text with a number on it, could you post that as well please?
Also, some tools have plugins to provide vim controls for them.
I know at least and use these:
There are probably more…
For me, it’s hardware support, i.e my laptops fingerprint sensor just isn’t supported, for the speakers to work I had to find a script that remapped the speakers, multiple desktops (especially with different resolutions) are a pain.
But the killer at the moment is a good solution to manage and post process my raw photos. Went from Lightroom to On1 Photo RAW…unfortunately DarkTable is still not there yet. Also still missing the affinity suite on Linux :-(
Also, sadly these tools also don’t run well in a VM
Same here, just stumbled across this issue yesterday when I tried to restructure my network to use .local
That would be an argument…IF it would be consistently 16 between each unit
Il leave this one here to see if it’s 16 every time: https://youtu.be/r7x-RGfd0Yk
Spoiler: it’s not!
Same here, it’s totally sufficient and never saw the reason to “upgrade” to the free business nodes
Jup, Im having an NTP issue on my win10 machine If you search for it you find the same 5 “solutions” from dozens of content farms.
I’m coding them down as plantuml network code and render them using a selfhosted plantuml Server.
In the end my whole admin guide resides in a obsidian notebook as markdown There is even a plugin that renders plantuml code within obsidian
The nice thing: everything is just code and can be moved to any other tool (had my documentation in a local gitlab repo, but I swapped gitlab out for gitea)
Yep, I went in this direction…until I gave in during a bare metal install of something…
Docker is not hassle free but usually most setup guides for apps are much much easier with docker
Worth a try, will try it when Im back home
I’ll try that one thanks
I changed the native vlan to ‘83’ and allowed all others
The isoöation is done with firewall rules blocking access from the IoT net to default, with some exceptions (dns, media nas (currently), etc.)
So if I understand this right you will need to change the network on the port attached to the synology in your UniFi configuration or set the vlan tag in the synology OS, I would do the former.
doesn’t the switch terminate any VLAN tagging at the port? so if I add the VLAN to the DSM configuration it doesn’t receive any tagged packages and refuses them?
It sounds like you just added a second network/vlan to the existing interface which means you actually created a trunk and are getting the old network untagged and the new network with vlan tags which the synology is dropping.
with all the other devices in the IoT subnet it works with setting the VLAN on the port of the switch. If I check back on the unifi site, I found this:
'Applying a VLAN to a Switch Port
Native VLAN
The Native VLAN is the VLAN assigned to "untagged" traffic passing through a switch port. Devices physically connected to a switch port will be placed on this Native VLAN.
Tagged Networks and Trunk Ports
Ports can be configured to allow traffic from other networks. Allowing specific networks/VLANs is referred to as “tagging” them on the switch port. You can see all ports’ VLAN tags in the VLAN Viewer, found in the Ports tab.
Ports that have been tagged to allow traffic from multiple VLANs are referred to as “trunk” ports. By default, all ports on UniFi Switches are trunked to allow all VLANs. '
if I understand that in combination with your comment correctly: I set the native VLAN to 83 so everything tagged with 83 is correctly forwarded to the NAS and accepted there, stuff tagged with 1 are non native, the tag stays on and the NAS doesn’t accept it?
But that would make the Synology NAS quite hard to use in any corporate setting with multiple VLANs which need to interconnect
and why does it work the other way around? while being in the default net 1 it does accept stuff from VLAN 83
Synology OS also doesn’t really support trunked ports through the UI (even though it does support a port that only uses a vlan tag) so it’s much easier to just leave them untagged.
which would mean, I can’t put it in the IoT net?
Maybe take a look at beancount, it’s a great tool for tracking and allows imports of different formats. There is no native way to do budgets, but there are plugins helping with it. Using fava it gives you a really nice UI to visualize your data I currently don’t use it for securities/portfolio but what I saw from the documentation, it definetly can handle it
https://beancount.github.io/