#userid — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #userid, aggregated by home.social.
-
European social platform W is coming. Will users leave X for it?
Europe is planning to launch its own social media platform, W, marketed to help fight disinformation and serve as a better alternative to X.
It will require user identity verification to prevent bots, which have been a driving force of disinformation in Europe.
-
European social platform W is coming. Will users leave X for it?
Europe is planning to launch its own social media platform, W, marketed to help fight disinformation and serve as a better alternative to X.
It will require user identity verification to prevent bots, which have been a driving force of disinformation in Europe.
-
European social platform W is coming. Will users leave X for it?
Europe is planning to launch its own social media platform, W, marketed to help fight disinformation and serve as a better alternative to X.
It will require user identity verification to prevent bots, which have been a driving force of disinformation in Europe.
-
European social platform W is coming. Will users leave X for it?
Europe is planning to launch its own social media platform, W, marketed to help fight disinformation and serve as a better alternative to X.
It will require user identity verification to prevent bots, which have been a driving force of disinformation in Europe.
-
European social platform W is coming. Will users leave X for it?
Europe is planning to launch its own social media platform, W, marketed to help fight disinformation and serve as a better alternative to X.
It will require user identity verification to prevent bots, which have been a driving force of disinformation in Europe.
-
"Lets add support for fetching a single #steam game and add it to our existing json it'll be easy"
clicky
Steam: :hacker_h: :hacker_a: :hacker_h: :hacker_a:You will bow before my #rules muahha
* no hashicon if you don't supply a #apikey #userid AND #own the game hahahahahah
* header icons from
imgSrc = `https://cdn.cloudflare.steamstatic.com/steam/apps/${game.appid}/header.jpg`;
} else {
imgSrc = `http://cdn.akamai.steamstatic.com/steam/apps/${game.appid}/header.jpg`;
}
?? We don't do that here..
tsk tsk tsk.
I added new hashes to my images so you have to fetch em at runtime poor mortal
Ah yes.
I'm having fun :blobcatfacepalm:
#repost •acws #acws #CodeAlcea -
"Lets add support for fetching a single #steam game and add it to our existing json it'll be easy"
clicky
Steam: :hacker_h: :hacker_a: :hacker_h: :hacker_a:You will bow before my #rules muahha
* no hashicon if you don't supply a #apikey #userid AND #own the game hahahahahah
* header icons from
imgSrc = `https://cdn.cloudflare.steamstatic.com/steam/apps/${game.appid}/header.jpg`;
} else {
imgSrc = `http://cdn.akamai.steamstatic.com/steam/apps/${game.appid}/header.jpg`;
}
?? We don't do that here..
tsk tsk tsk.
I added new hashes to my images so you have to fetch em at runtime poor mortal
Ah yes.
I'm having fun :blobcatfacepalm:
#repost •acws #acws #CodeAlcea -
VPN включил — подозрение получил: анонимность становится красным флагом
Раньше VPN был как шапка-невидимка. А теперь — как табличка на лбу: «Я скрываюсь, спросите меня за что». В России готовится закон: поиск запрещенных материалов + VPN = отягчающее . Это значит, что мы подходим к черте когда сам факт анонимности будет поводом для расследования. В будущем мы будем платить за то, чтобы оставаться анонимными . На примере "Моя борьба" разберем примеры запросов, за которые тебе ничего не будет , и случаи, когда за ту же тему могут наказать. В статье: – Какие формулировки в поиске считаются "плохими" – Как написать «Mein Kampf» так, чтобы не словить протокол – Как извне определить , что ты используешь VPN ? ТОП-бонус внутри: Технические данные для распознавания VPN , как построить твой уникальный UserID: пример кода и логика работы.
-
VPN включил — подозрение получил: анонимность становится красным флагом
Раньше VPN был как шапка-невидимка. А теперь — как табличка на лбу: «Я скрываюсь, спросите меня за что». В России готовится закон: поиск запрещенных материалов + VPN = отягчающее . Это значит, что мы подходим к черте когда сам факт анонимности будет поводом для расследования. В будущем мы будем платить за то, чтобы оставаться анонимными . На примере "Моя борьба" разберем примеры запросов, за которые тебе ничего не будет , и случаи, когда за ту же тему могут наказать. В статье: – Какие формулировки в поиске считаются "плохими" – Как написать «Mein Kampf» так, чтобы не словить протокол – Как извне определить , что ты используешь VPN ? ТОП-бонус внутри: Технические данные для распознавания VPN , как построить твой уникальный UserID: пример кода и логика работы.
-
VPN включил — подозрение получил: анонимность становится красным флагом
Раньше VPN был как шапка-невидимка. А теперь — как табличка на лбу: «Я скрываюсь, спросите меня за что». В России готовится закон: поиск запрещенных материалов + VPN = отягчающее . Это значит, что мы подходим к черте когда сам факт анонимности будет поводом для расследования. В будущем мы будем платить за то, чтобы оставаться анонимными . На примере "Моя борьба" разберем примеры запросов, за которые тебе ничего не будет , и случаи, когда за ту же тему могут наказать. В статье: – Какие формулировки в поиске считаются "плохими" – Как написать «Mein Kampf» так, чтобы не словить протокол – Как извне определить , что ты используешь VPN ? ТОП-бонус внутри: Технические данные для распознавания VPN , как построить твой уникальный UserID: пример кода и логика работы.
-
VPN включил — подозрение получил: анонимность становится красным флагом
Раньше VPN был как шапка-невидимка. А теперь — как табличка на лбу: «Я скрываюсь, спросите меня за что». В России готовится закон: поиск запрещенных материалов + VPN = отягчающее . Это значит, что мы подходим к черте когда сам факт анонимности будет поводом для расследования. В будущем мы будем платить за то, чтобы оставаться анонимными . На примере "Моя борьба" разберем примеры запросов, за которые тебе ничего не будет , и случаи, когда за ту же тему могут наказать. В статье: – Какие формулировки в поиске считаются "плохими" – Как написать «Mein Kampf» так, чтобы не словить протокол – Как извне определить , что ты используешь VPN ? ТОП-бонус внутри: Технические данные для распознавания VPN , как построить твой уникальный UserID: пример кода и логика работы.
-
Here's how to check the certificate expiry for the Palo Alto User-ID Agent and the Terminal Server Agent
https://thedxt.ca/2024/10/palo-alto-user-id-and-terminal-server-agent-certificates/
-
Here's how to check the certificate expiry for the Palo Alto User-ID Agent and the Terminal Server Agent
https://thedxt.ca/2024/10/palo-alto-user-id-and-terminal-server-agent-certificates/
-
Here's how to check the certificate expiry for the Palo Alto User-ID Agent and the Terminal Server Agent
https://thedxt.ca/2024/10/palo-alto-user-id-and-terminal-server-agent-certificates/
-
Here's how to check the certificate expiry for the Palo Alto User-ID Agent and the Terminal Server Agent
https://thedxt.ca/2024/10/palo-alto-user-id-and-terminal-server-agent-certificates/
-
Here's how to check the certificate expiry for the Palo Alto User-ID Agent and the Terminal Server Agent
https://thedxt.ca/2024/10/palo-alto-user-id-and-terminal-server-agent-certificates/
-
Here's how to upgrade the Palo Alto TS Agent
-
Here's how to upgrade the Palo Alto TS Agent
-
Here's how to upgrade the Palo Alto TS Agent
-
Here's how to upgrade the Palo Alto TS Agent
-
#Shellprogramming skills are pretty portable between #Linux, #BSD, and #macOS, but some of the underpinnings of macOS are non-standard. It helps to remind yourself that macOS is not a standard #BSD #Unix variant; Apple's #Darwin based systems do a lot of embrace-and-extend under the hood. Here's a practical example that comes up often in the enterprise.
Most #Linux systems export the current user's login name to the LOGNAME environment variable (often via sourcing /etc/profile) and may also export the user's default shell from the user's #GECOS record in /etc/passwd to the preferred shell (set by an application or the user) as the SHELL environment variable. The canonical way to get access to the user's default shell on most Unix-like systems is by parsing /etc/password or another NSS database with the getent utility, e.g.
getent passwd "$LOGNAME" | cut -d: -f7.There are other means to do this on Linux too, but macOS doesn't provide this common #POSIX compatible userspace utility. Instead, Darwin relies on opendirectory(8) for storing and accessing GECOS records, requiring other tools to retrieve the information. You can query a user's GECOS record on Darwin like so:
# directly from the Open Directory service, local or remote
dscl . -read "/Users/$(id -un)" shell | awk '/^shell:/ {print $2}'
# from the directory service's cache on the local system
dscacheutil -q user -a uid "$(id -u)" | awk '/^shell:/ {print $2}'Be aware that there are other ways to do this, too, but old school utilities like whoami have been deprecated in favor of
id -un, and finger as implemented on most systems (e.g. via [x]inetd, or reading various #dotfiles from users' directories locally or over the network) is considered a security risk.In containers, especially with non-standard shells, or with centralized #IAM using #LDAP or #ActiveDirectory, you may have to match the local #userID to a remote #LDIF record to before grepping for the data you need. In addition, nsswitch.conf, PAM modules, NIS+, or other less-common data sources may need to be consulted and each will generally have specific utilities for looking up the stored or cached information that is equivalent to what's normally provided in the 7th GECOS field for each user on standard Linux and Unix systems.
As always, your mileage may vary based on use case or implementation details. On the plus side, problems are rarely insoluble when you know where to dig for a solution!
-
#Shellprogramming skills are pretty portable between #Linux, #BSD, and #macOS, but some of the underpinnings of macOS are non-standard. It helps to remind yourself that macOS is not a standard #BSD #Unix variant; Apple's #Darwin based systems do a lot of embrace-and-extend under the hood. Here's a practical example that comes up often in the enterprise.
Most #Linux systems export the current user's login name to the LOGNAME environment variable (often via sourcing /etc/profile) and may also export the user's default shell from the user's #GECOS record in /etc/passwd to the preferred shell (set by an application or the user) as the SHELL environment variable. The canonical way to get access to the user's default shell on most Unix-like systems is by parsing /etc/password or another NSS database with the getent utility, e.g.
getent passwd "$LOGNAME" | cut -d: -f7.There are other means to do this on Linux too, but macOS doesn't provide this common #POSIX compatible userspace utility. Instead, Darwin relies on opendirectory(8) for storing and accessing GECOS records, requiring other tools to retrieve the information. You can query a user's GECOS record on Darwin like so:
# directly from the Open Directory service, local or remote
dscl . -read "/Users/$(id -un)" shell | awk '/^shell:/ {print $2}'
# from the directory service's cache on the local system
dscacheutil -q user -a uid "$(id -u)" | awk '/^shell:/ {print $2}'Be aware that there are other ways to do this, too, but old school utilities like whoami have been deprecated in favor of
id -un, and finger as implemented on most systems (e.g. via [x]inetd, or reading various #dotfiles from users' directories locally or over the network) is considered a security risk.In containers, especially with non-standard shells, or with centralized #IAM using #LDAP or #ActiveDirectory, you may have to match the local #userID to a remote #LDIF record to before grepping for the data you need. In addition, nsswitch.conf, PAM modules, NIS+, or other less-common data sources may need to be consulted and each will generally have specific utilities for looking up the stored or cached information that is equivalent to what's normally provided in the 7th GECOS field for each user on standard Linux and Unix systems.
As always, your mileage may vary based on use case or implementation details. On the plus side, problems are rarely insoluble when you know where to dig for a solution!
-
#Shellprogramming skills are pretty portable between #Linux, #BSD, and #macOS, but some of the underpinnings of macOS are non-standard. It helps to remind yourself that macOS is not a standard #BSD #Unix variant; Apple's #Darwin based systems do a lot of embrace-and-extend under the hood. Here's a practical example that comes up often in the enterprise.
Most #Linux systems export the current user's login name to the LOGNAME environment variable (often via sourcing /etc/profile) and may also export the user's default shell from the user's #GECOS record in /etc/passwd to the preferred shell (set by an application or the user) as the SHELL environment variable. The canonical way to get access to the user's default shell on most Unix-like systems is by parsing /etc/password or another NSS database with the getent utility, e.g.
getent passwd "$LOGNAME" | cut -d: -f7.There are other means to do this on Linux too, but macOS doesn't provide this common #POSIX compatible userspace utility. Instead, Darwin relies on opendirectory(8) for storing and accessing GECOS records, requiring other tools to retrieve the information. You can query a user's GECOS record on Darwin like so:
# directly from the Open Directory service, local or remote
dscl . -read "/Users/$(id -un)" shell | awk '/^shell:/ {print $2}'
# from the directory service's cache on the local system
dscacheutil -q user -a uid "$(id -u)" | awk '/^shell:/ {print $2}'Be aware that there are other ways to do this, too, but old school utilities like whoami have been deprecated in favor of
id -un, and finger as implemented on most systems (e.g. via [x]inetd, or reading various #dotfiles from users' directories locally or over the network) is considered a security risk.In containers, especially with non-standard shells, or with centralized #IAM using #LDAP or #ActiveDirectory, you may have to match the local #userID to a remote #LDIF record to before grepping for the data you need. In addition, nsswitch.conf, PAM modules, NIS+, or other less-common data sources may need to be consulted and each will generally have specific utilities for looking up the stored or cached information that is equivalent to what's normally provided in the 7th GECOS field for each user on standard Linux and Unix systems.
As always, your mileage may vary based on use case or implementation details. On the plus side, problems are rarely insoluble when you know where to dig for a solution!
-
#Shellprogramming skills are pretty portable between #Linux, #BSD, and #macOS, but some of the underpinnings of macOS are non-standard. It helps to remind yourself that macOS is not a standard #BSD #Unix variant; Apple's #Darwin based systems do a lot of embrace-and-extend under the hood. Here's a practical example that comes up often in the enterprise.
Most #Linux systems export the current user's login name to the LOGNAME environment variable (often via sourcing /etc/profile) and may also export the user's default shell from the user's #GECOS record in /etc/passwd to the preferred shell (set by an application or the user) as the SHELL environment variable. The canonical way to get access to the user's default shell on most Unix-like systems is by parsing /etc/password or another NSS database with the getent utility, e.g.
getent passwd "$LOGNAME" | cut -d: -f7.There are other means to do this on Linux too, but macOS doesn't provide this common #POSIX compatible userspace utility. Instead, Darwin relies on opendirectory(8) for storing and accessing GECOS records, requiring other tools to retrieve the information. You can query a user's GECOS record on Darwin like so:
# directly from the Open Directory service, local or remote
dscl . -read "/Users/$(id -un)" shell | awk '/^shell:/ {print $2}'
# from the directory service's cache on the local system
dscacheutil -q user -a uid "$(id -u)" | awk '/^shell:/ {print $2}'Be aware that there are other ways to do this, too, but old school utilities like whoami have been deprecated in favor of
id -un, and finger as implemented on most systems (e.g. via [x]inetd, or reading various #dotfiles from users' directories locally or over the network) is considered a security risk.In containers, especially with non-standard shells, or with centralized #IAM using #LDAP or #ActiveDirectory, you may have to match the local #userID to a remote #LDIF record to before grepping for the data you need. In addition, nsswitch.conf, PAM modules, NIS+, or other less-common data sources may need to be consulted and each will generally have specific utilities for looking up the stored or cached information that is equivalent to what's normally provided in the 7th GECOS field for each user on standard Linux and Unix systems.
As always, your mileage may vary based on use case or implementation details. On the plus side, problems are rarely insoluble when you know where to dig for a solution!
-
#Shellprogramming skills are pretty portable between #Linux, #BSD, and #macOS, but some of the underpinnings of macOS are non-standard. It helps to remind yourself that macOS is not a standard #BSD #Unix variant; Apple's #Darwin based systems do a lot of embrace-and-extend under the hood. Here's a practical example that comes up often in the enterprise.
Most #Linux systems export the current user's login name to the LOGNAME environment variable (often via sourcing /etc/profile) and may also export the user's default shell from the user's #GECOS record in /etc/passwd to the preferred shell (set by an application or the user) as the SHELL environment variable. The canonical way to get access to the user's default shell on most Unix-like systems is by parsing /etc/password or another NSS database with the getent utility, e.g.
getent passwd "$LOGNAME" | cut -d: -f7.There are other means to do this on Linux too, but macOS doesn't provide this common #POSIX compatible userspace utility. Instead, Darwin relies on opendirectory(8) for storing and accessing GECOS records, requiring other tools to retrieve the information. You can query a user's GECOS record on Darwin like so:
# directly from the Open Directory service, local or remote
dscl . -read "/Users/$(id -un)" shell | awk '/^shell:/ {print $2}'
# from the directory service's cache on the local system
dscacheutil -q user -a uid "$(id -u)" | awk '/^shell:/ {print $2}'Be aware that there are other ways to do this, too, but old school utilities like whoami have been deprecated in favor of
id -un, and finger as implemented on most systems (e.g. via [x]inetd, or reading various #dotfiles from users' directories locally or over the network) is considered a security risk.In containers, especially with non-standard shells, or with centralized #IAM using #LDAP or #ActiveDirectory, you may have to match the local #userID to a remote #LDIF record to before grepping for the data you need. In addition, nsswitch.conf, PAM modules, NIS+, or other less-common data sources may need to be consulted and each will generally have specific utilities for looking up the stored or cached information that is equivalent to what's normally provided in the 7th GECOS field for each user on standard Linux and Unix systems.
As always, your mileage may vary based on use case or implementation details. On the plus side, problems are rarely insoluble when you know where to dig for a solution!
-
Here's how to upgrade the Palo Alto User-ID Agent
-
Here's how to upgrade the Palo Alto User-ID Agent
-
Here's how to upgrade the Palo Alto User-ID Agent
-
Here's how to upgrade the Palo Alto User-ID Agent
-
Als ich heute eine Paketquellenaktualisierung in @fdroidorg gemacht habe, war das lang erwartete @simplex Upgrade verfügbar. Dieser #Messenger ohne Notwendigkeit einer #UserID ist bei der Sparsamkeit von #Metadaten mein Favorit. :hacker:
Wer mehr über die Funktionsweise erfahren möchte, findet Erläuterungen unter https://simplex.chat/#how-simplex-works sowie im umfangreichen aber gut verständlichen 📄 Whitepaper https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md
-
Als ich heute eine Paketquellenaktualisierung in @fdroidorg gemacht habe, war das lang erwartete @simplex Upgrade verfügbar. Dieser #Messenger ohne Notwendigkeit einer #UserID ist bei der Sparsamkeit von #Metadaten mein Favorit. :hacker:
Wer mehr über die Funktionsweise erfahren möchte, findet Erläuterungen unter https://simplex.chat/#how-simplex-works sowie im umfangreichen aber gut verständlichen 📄 Whitepaper https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md
-
Als ich heute eine Paketquellenaktualisierung in @fdroidorg gemacht habe, war das lang erwartete @simplex Upgrade verfügbar. Dieser #Messenger ohne Notwendigkeit einer #UserID ist bei der Sparsamkeit von #Metadaten mein Favorit. :hacker:
Wer mehr über die Funktionsweise erfahren möchte, findet Erläuterungen unter https://simplex.chat/#how-simplex-works sowie im umfangreichen aber gut verständlichen 📄 Whitepaper https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md
-
Signal Messenger and Phone Number
I appreciate Meredith Whittaker’s views on surveillance, privacy, security and encryption.
In the same context of privacy, I keep wondering about the rationale behind Signal Messenger to depend only on phone number or mobile number as its digital identity. Why does Signal Messenger not provide multiple alphanumeric user identities internally mapped to the phone number and enable users to only share the user id without disclosing the phone number? It would be better if Signal Messenger can discard usage of phone number.
#SignalApp #Signal #Privacy #UserIdentity #UserID
cc: @Mer__edith, @signalapp @srijit
-
Signal Messenger and Phone Number
I appreciate Meredith Whittaker’s views on surveillance, privacy, security and encryption.
In the same context of privacy, I keep wondering about the rationale behind Signal Messenger to depend only on phone number or mobile number as its digital identity. Why does Signal Messenger not provide multiple alphanumeric user identities internally mapped to the phone number and enable users to only share the user id without disclosing the phone number? It would be better if Signal Messenger can discard usage of phone number.
#SignalApp #Signal #Privacy #UserIdentity #UserID
cc: @Mer__edith, @signalapp @srijit
-
Signal Messenger and Phone Number
I appreciate Meredith Whittaker’s views on surveillance, privacy, security and encryption.
In the same context of privacy, I keep wondering about the rationale behind Signal Messenger to depend only on phone number or mobile number as its digital identity. Why does Signal Messenger not provide multiple alphanumeric user identities internally mapped to the phone number and enable users to only share the user id without disclosing the phone number? It would be better if Signal Messenger can discard usage of phone number.
#SignalApp #Signal #Privacy #UserIdentity #UserID
cc: @Mer__edith, @signalapp @srijit
-
Signal Messenger and Phone Number
I appreciate Meredith Whittaker’s views on surveillance, privacy, security and encryption.
In the same context of privacy, I keep wondering about the rationale behind Signal Messenger to depend only on phone number or mobile number as its digital identity. Why does Signal Messenger not provide multiple alphanumeric user identities internally mapped to the phone number and enable users to only share the user id without disclosing the phone number? It would be better if Signal Messenger can discard usage of phone number.
#SignalApp #Signal #Privacy #UserIdentity #UserID
cc: @Mer__edith, @signalapp @srijit
-
Signal Messenger and Phone Number
I appreciate Meredith Whittaker’s views on surveillance, privacy, security and encryption.
In the same context of privacy, I keep wondering about the rationale behind Signal Messenger to depend only on phone number or mobile number as its digital identity. Why does Signal Messenger not provide multiple alphanumeric user identities internally mapped to the phone number and enable users to only share the user id without disclosing the phone number? It would be better if Signal Messenger can discard usage of phone number.
#SignalApp #Signal #Privacy #UserIdentity #UserID
cc: @Mer__edith, @signalapp @srijit
-
Sudo Error on Ubuntu: Fixing 'unknown uid 1000: Who are you?'
https://techdirectarchive.com/2022/02/24/sudo-error-on-ubuntu-fixing-unknown-uid-1000-who-are-you/
#Linux, #LinuxOS, #RootAccount, #Ubuntu, #UserAccount, #UserID
-
CW: transphobic scam alert
@PsyChuan got any #lab data and details on it?
Cuz I do think providing more detailed info would be good.
If you have #WaybackMachine screenshots and details that said account with the same #UserID is basically a "submarine" that would gladly help as well...
We need to spread awareness...
-
CW: transphobic scam alert
@PsyChuan got any #lab data and details on it?
Cuz I do think providing more detailed info would be good.
If you have #WaybackMachine screenshots and details that said account with the same #UserID is basically a "submarine" that would gladly help as well...
We need to spread awareness...
-
CW: transphobic scam alert
@PsyChuan got any #lab data and details on it?
Cuz I do think providing more detailed info would be good.
If you have #WaybackMachine screenshots and details that said account with the same #UserID is basically a "submarine" that would gladly help as well...
We need to spread awareness...
-
-
