#4d — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #4d, aggregated by home.social.
-
-
4D-печать: патенты в мире и в России
4D-печать – это технология производства, при которой 3D-печатные объекты могут трансформироваться со временем под воздействием внешних факторов, таких как тепло, свет, влага или магнитные поля (время даёт 4-е « измерение » в дополнении к 3D-печати, которую мы уже освещали в нашей статье на Хабре). Технология применяется в аэрокосмической отрасли, биомедицинской инженерии и производстве «умных» материалов, позволяя создавать самособирающиеся конструкции, адаптивную одежду и реконфигурируемые компоненты. Посмотрим, что происходит в этой сфере в России и мире с точки зрения патентов.
https://habr.com/ru/companies/onlinepatent/articles/1029404/
#4dпечать #4d #4d_печать #4d_принтеры #патентование #патенты #печать #3dпечать #3d #3dпринтер
-
La historia que os contamos sobre el mercader de #FakeNews Alex Jones en el último festival #4d por fin tiene un final o mejor aún una nueva temporada.
The Onion (ElMundoToday yanqui) ha comprado su página 😂
Suerte parodiando lo imparodiable!
https://www.them.us/story/infowars-licensed-the-onion-rainbow-logo -
numbercruncher has a new video out! It's gorgeous and gives a nifty explanation of Coxeter-Dynkin diagrams, showing off 4d polyhchora!
-
https://www.europesays.com/at/106409/ Maxon kündigt kostenlose Tools und die Erweiterung von ZBrush und Cinema 4D auf mobile Geräte an #3DWorkflows #4D #ARM #AT #Austria #Autograph #BAD #Cinema #Die #Einzelanwender #HOMBURG #ipad #NAB #Österreich #Rückkehr #Science #Science&Technology #sehen #Sie #Technik #Technology #Windows #Wissenschaft #Wissenschaft&Technik #ZBrush
-
#ScreenshotSaturday adding auroras spanning 8 color channels 🌌 🤔
(hopefully wiðout having to add 5d noise to get ðem moving🫠) -
🤔 4d voronoi tess based on a jittered 24-cell(which has 24 3d polyhedra as its surface)🍯honeycomb🐝 wiθ a star of arrows covering each (4d)cell (stateless 4d trees confirmed?)
(*actually just a 3d ✝️section of it)#TilingTuesday #hmmm #WIP #4d #animation #tiling #creativecoding #abstract #mathart #honeycomb
-
#KnowledgeByte: #4D #Printing is a manufacturing process that creates objects that can change their shape or properties over time in response to environmental stimuli.
This is achieved by incorporating materials that respond to changes in temperature, light, pH, or other factors.
https://knowledgezone.co.in/trends/browser?topic=4D-Printing
-
#screenshotsaturday 🐠🏫🎣🕸️
I'm starting to regret making entities, structures, terrain, & extra gradient data all exist in a single layer 🫠 -
xyz slice of ðe hopf-anti-buddha-brot(pick whatever order u want)(actually colored based on a mix of ðe anti- & normal buddhabrots, yes, ðe "normal" 1 has ðe usual streaks & surfaces) 🦊
-
🤔🫥 2→ 1s (using ðe same 6 color channels)🤔🤔🤔
-
xyz slice of ðe q^5/(1 + x^7 + iy^7 + jz^7) + c buddhabrot + anti-buddhabrot wiθ hopfbrot-like pow/division 🤔🤔(& escape r = 4)
#3d #fractal #animation #mathart #mastoart #creativecoding #4d #abstract #nebula
-
🤔 testing per color channel refraction/reflection(wiθ up to 15 color channels )
-
> super secret settings
-
El Gobierno deniega a García Caparrós la condición de víctima del terrorismo de Estado: "No tiene encaje en la ley" https://www.eldiario.es/andalucia/gobierno-deniega-garcia-caparros-condicion-victima-terrorismo-no-encaje-ley_1_13017507.html Daniel Cela #ManuelJoséGarcíaCaparrós #Andalucía #4D
-
46 years ago, Carl Sagan beautifully explained the fourth dimension using a sliced apple
-
#screenshotsaturday adding elemental transmutation(actually chemistry)(actually alchemy because fluids in your inventory ignore ðe law of conservation of mass & I've accidentally made it so 1 chalk = 1 sand = 1 gravel = 1 hypercubic meter of concrete = 1/5 hypercubic meters of chalk rock)
-
xyz slice of a 4d q^2 - q + c julia set looking (white = internal cavities but not rly)
#fractal #animation #3d #4d #mathart #abstract #creativecoding
-
"Zurich 4D": The most popular and freely accessible geodataset of the city of Zurich can now be represented virtually and easily #4d
https://www.stadt-zuerich.ch/de/stadtleben/stadtportraet/zuerich-digital/zuerich-vier-d.html
-
Un cop aquí, selecciono que sóc una persona ciutadana, i això m'envia a l'Administració Oberta de Catalunya, que al #4D de @X_net van explicar al 2025 que són majis i intenten simplificar burocràcia internament a la Gene.
Però si mirem la tècnica, ens entristim:
valid.aoc.cat: AS: 16509 (AMAZON-02)
Sí, el sistema d'autenticació de l'Administració Oberta de Catalunya (aoc.cat), està a AWS, a ca Amazon / Jeff Bezos, multinacional / oligarca del règim dels EEUUA.I és aquí on hi ha el desastre del captcha:
Si no permets que el teu dispositiu parli amb Google, per aquesta via no pots iniciar sessió a coses de l'administració.A part de les comunicacions a diverses CDNs al règim dels EEUUA.
-
#ScreenshotSaturday r e f r a c t i o n ? ? ?
(maybe a bit too much) -
Testing some new worldgen tech for generating more ordered(= not noise) non-intersecting structures(wiðout saving any data or checking oðer voxels)
(no, I'm still not adding 4d trees) -
#ScreenshotSaturday 🤔hmm yes clearly ðis punishing bird-‽non-infringing bird(happens to resemble but is legally distinct from ðe 🇰🇷 scp, sorry, abnormality) represents 🐍🎩 𓅱
what did ðe devs mean by ðis 🤔
-
-
ðe 6 orθogonal planes + color based on a 3rd axis(green = center, red/blue = average of ðe +/- segments), projected from a single 4d map
Soo, yeah, ig ðere's someθig to check out once we get terabytes of ram lol 𓅱(resolution^4 = 😔)
(or a GPU algoriðm ðat can share a single 3d map?)
((or quantum magic |⚛️>)) -
^article just dropped
https://uehapetsijque.substack.com/p/the-hopfbrot -
#ScreenshotSaturday adding lakes/swamps/mangrove "trees"
((& 🫁🪷)) -
4D physics in the 3-Body-Problem
#Tibees #dimentions #4D #physics
https://www.youtube.com/watch?v=7kvwu3lzTlE&list=UULF52kszkc08-acFOuogFl5jw&index=1
-
pov ur a tourist checking out ðe newly discovered 4d sponge reefs wiθ all ðese wacky 9d colors(projected to rgb spacetime waves ofc) but accidentally wondered off in a random direction 💀
-
The 4th Dimension (shorts)
Turning a sphere inside out
#Physics #4thDimension #4D #Dimension #Dimensions
https://www.youtube.com/watch?v=-TvllqLzb8M&list=PLATpsZGmpkg8PYPS8HEPehR0l9tZYwrCi&index=49
-
Hoy es #28F, el día en las andaluzas y los andaluces conmemoramos el referéndum con el que accedimos a la autonomía. Pero para muchas personas, entre las que me incluyo, el verdadero Día Nacional de Andalucía es el 4 de Diciembre.
En aquella fecha de 1977 dos millones de personas salieron a las calles de las ocho capitales de Andalucía para reclamar nuestros derechos como pueblo. Sin #4D ni hay 28F ni se entiende el actual modelo autonómico español.
En cualquier caso ¡Viva Andalucía Libre! 😊
-
(24/N) There are some best practices that will make it easier to answer threat modeling question #3, "What are you going to do about it?". These will help you protect a wide range of assets by taking care of your devices, so let's look at them first:
- Encrypt data at rest
- Bootstrap your workplace
- Actively maintain your devices
- Secure your devices
- Prepare for repair
1. Encrypt data at rest
What can you achieve with intermediate knowledge, without fully descending into the rat hole?
⚠️ Caveat: this is best done when setting up #Linux on a new device. Modifying an existing installation on your own IMHO isn't advisable if you're not a seasoned user. If you still decide to venture into it, make SURE you have backed up all your assets, before following "howtos on the internet". You have been warned.
Likening your device to a medieval city:
1) Full-Disk Encryption (FDE) is like locking the "city gate". Most popular Linux distributions offer FDE during the installation process. FDE is also your last line of defense when your device gets stolen, or your disk fails and cannot be safely wiped before disposing of it. Use FDE. (Yes, technically, "Full" is not absolutely accurate. We'll leave it at that.)
2) Within your "city", there will likely be at least two "houses": the home of the admin account, and your personal home. Using FDE alone, the "doors" of these homes won't have any locks of their own. Possibly not a big deal with respect to the administrative account, but admins being able to access any of your non-public assets, even when you're not logged in, is probably not what you want.
While the specific steps depend on your preferred Linux distro, a "portable" solution is to create a separate, encrypted disk partition, and have it mounted as your user home directory, when you log in. That solution is based on cryptsetup and the pam_mount module, a nice tutorial example is:
3) Within your "house", you may wish to have a locked "chest", e.g. for your #FYEO assets. There's essentially two options: a) a single, encrypted container file that acts as a "#vault" for your asset files; or b) an encrypted overlay file system that maintains an openly visible directory hosting your encrypted assets, including directory structures, in the background; and allows you to mount a decrypted counterpart, for working on your assets.
a) A "vault", being a single file, is easy to copy and carry around, on arbitrary storage media, e.g. USB sticks. It doesn't reveal too much about its contents, but resizing it takes a little effort. Also, you can't "incrementally backup" content changes, just copy the whole, changed vault.
A nice tutorial for creating and using a vault using plain, standard cryptsetup is https://opensource.com/article/21/4/linux-encryption by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt https://mhogomchungu.github.io/zuluCrypt/ – IMHO the app is still in need of a little polish, though.
b) An encrypted overlay file system allows for incrementally backing up changed assets, but exposes considerable metadata (rough file sizes, directory structures, modification dates).
The most widely used package for this is probably #gocryptfs. Its "HowTo" is literally a one-pager: https://nuetzlich.net/gocryptfs/quickstart/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(24/N) There are some best practices that will make it easier to answer threat modeling question #3, "What are you going to do about it?". These will help you protect a wide range of assets by taking care of your devices, so let's look at them first:
- Encrypt data at rest
- Bootstrap your workplace
- Actively maintain your devices
- Secure your devices
- Prepare for repair
1. Encrypt data at rest
What can you achieve with intermediate knowledge, without fully descending into the rat hole?
⚠️ Caveat: this is best done when setting up #Linux on a new device. Modifying an existing installation on your own IMHO isn't advisable if you're not a seasoned user. If you still decide to venture into it, make SURE you have backed up all your assets, before following "howtos on the internet". You have been warned.
Likening your device to a medieval city:
1) Full-Disk Encryption (FDE) is like locking the "city gate". Most popular Linux distributions offer FDE during the installation process. FDE is also your last line of defense when your device gets stolen, or your disk fails and cannot be safely wiped before disposing of it. Use FDE. (Yes, technically, "Full" is not absolutely accurate. We'll leave it at that.)
2) Within your "city", there will likely be at least two "houses": the home of the admin account, and your personal home. Using FDE alone, the "doors" of these homes won't have any locks of their own. Possibly not a big deal with respect to the administrative account, but admins being able to access any of your non-public assets, even when you're not logged in, is probably not what you want.
While the specific steps depend on your preferred Linux distro, a "portable" solution is to create a separate, encrypted disk partition, and have it mounted as your user home directory, when you log in. That solution is based on cryptsetup and the pam_mount module, a nice tutorial example is:
3) Within your "house", you may wish to have a locked "chest", e.g. for your #FYEO assets. There's essentially two options: a) a single, encrypted container file that acts as a "#vault" for your asset files; or b) an encrypted overlay file system that maintains an openly visible directory hosting your encrypted assets, including directory structures, in the background; and allows you to mount a decrypted counterpart, for working on your assets.
a) A "vault", being a single file, is easy to copy and carry around, on arbitrary storage media, e.g. USB sticks. It doesn't reveal too much about its contents, but resizing it takes a little effort. Also, you can't "incrementally backup" content changes, just copy the whole, changed vault.
A nice tutorial for creating and using a vault using plain, standard cryptsetup is https://opensource.com/article/21/4/linux-encryption by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt https://mhogomchungu.github.io/zuluCrypt/ – IMHO the app is still in need of a little polish, though.
b) An encrypted overlay file system allows for incrementally backing up changed assets, but exposes considerable metadata (rough file sizes, directory structures, modification dates).
The most widely used package for this is probably #gocryptfs. Its "HowTo" is literally a one-pager: https://nuetzlich.net/gocryptfs/quickstart/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(24/N) There are some best practices that will make it easier to answer threat modeling question #3, "What are you going to do about it?". These will help you protect a wide range of assets by taking care of your devices, so let's look at them first:
- Encrypt data at rest
- Bootstrap your workplace
- Actively maintain your devices
- Secure your devices
- Prepare for repair
1. Encrypt data at rest
What can you achieve with intermediate knowledge, without fully descending into the rat hole?
⚠️ Caveat: this is best done when setting up #Linux on a new device. Modifying an existing installation on your own IMHO isn't advisable if you're not a seasoned user. If you still decide to venture into it, make SURE you have backed up all your assets, before following "howtos on the internet". You have been warned.
Likening your device to a medieval city:
1) Full-Disk Encryption (FDE) is like locking the "city gate". Most popular Linux distributions offer FDE during the installation process. FDE is also your last line of defense when your device gets stolen, or your disk fails and cannot be safely wiped before disposing of it. Use FDE. (Yes, technically, "Full" is not absolutely accurate. We'll leave it at that.)
2) Within your "city", there will likely be at least two "houses": the home of the admin account, and your personal home. Using FDE alone, the "doors" of these homes won't have any locks of their own. Possibly not a big deal with respect to the administrative account, but admins being able to access any of your non-public assets, even when you're not logged in, is probably not what you want.
While the specific steps depend on your preferred Linux distro, a "portable" solution is to create a separate, encrypted disk partition, and have it mounted as your user home directory, when you log in. That solution is based on cryptsetup and the pam_mount module, a nice tutorial example is:
3) Within your "house", you may wish to have a locked "chest", e.g. for your #FYEO assets. There's essentially two options: a) a single, encrypted container file that acts as a "#vault" for your asset files; or b) an encrypted overlay file system that maintains an openly visible directory hosting your encrypted assets, including directory structures, in the background; and allows you to mount a decrypted counterpart, for working on your assets.
a) A "vault", being a single file, is easy to copy and carry around, on arbitrary storage media, e.g. USB sticks. It doesn't reveal too much about its contents, but resizing it takes a little effort. Also, you can't "incrementally backup" content changes, just copy the whole, changed vault.
A nice tutorial for creating and using a vault using plain, standard cryptsetup is https://opensource.com/article/21/4/linux-encryption by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt https://mhogomchungu.github.io/zuluCrypt/ – IMHO the app is still in need of a little polish, though.
b) An encrypted overlay file system allows for incrementally backing up changed assets, but exposes considerable metadata (rough file sizes, directory structures, modification dates).
The most widely used package for this is probably #gocryptfs. Its "HowTo" is literally a one-pager: https://nuetzlich.net/gocryptfs/quickstart/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(24/N) There are some best practices that will make it easier to answer threat modeling question #3, "What are you going to do about it?". These will help you protect a wide range of assets by taking care of your devices, so let's look at them first:
- Encrypt data at rest
- Bootstrap your workplace
- Actively maintain your devices
- Secure your devices
- Prepare for repair
1. Encrypt data at rest
What can you achieve with intermediate knowledge, without fully descending into the rat hole?
⚠️ Caveat: this is best done when setting up #Linux on a new device. Modifying an existing installation on your own IMHO isn't advisable if you're not a seasoned user. If you still decide to venture into it, make SURE you have backed up all your assets, before following "howtos on the internet". You have been warned.
Likening your device to a medieval city:
1) Full-Disk Encryption (FDE) is like locking the "city gate". Most popular Linux distributions offer FDE during the installation process. FDE is also your last line of defense when your device gets stolen, or your disk fails and cannot be safely wiped before disposing of it. Use FDE. (Yes, technically, "Full" is not absolutely accurate. We'll leave it at that.)
2) Within your "city", there will likely be at least two "houses": the home of the admin account, and your personal home. Using FDE alone, the "doors" of these homes won't have any locks of their own. Possibly not a big deal with respect to the administrative account, but admins being able to access any of your non-public assets, even when you're not logged in, is probably not what you want.
While the specific steps depend on your preferred Linux distro, a "portable" solution is to create a separate, encrypted disk partition, and have it mounted as your user home directory, when you log in. That solution is based on cryptsetup and the pam_mount module, a nice tutorial example is:
3) Within your "house", you may wish to have a locked "chest", e.g. for your #FYEO assets. There's essentially two options: a) a single, encrypted container file that acts as a "#vault" for your asset files; or b) an encrypted overlay file system that maintains an openly visible directory hosting your encrypted assets, including directory structures, in the background; and allows you to mount a decrypted counterpart, for working on your assets.
a) A "vault", being a single file, is easy to copy and carry around, on arbitrary storage media, e.g. USB sticks. It doesn't reveal too much about its contents, but resizing it takes a little effort. Also, you can't "incrementally backup" content changes, just copy the whole, changed vault.
A nice tutorial for creating and using a vault using plain, standard cryptsetup is https://opensource.com/article/21/4/linux-encryption by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt https://mhogomchungu.github.io/zuluCrypt/ – IMHO the app is still in need of a little polish, though.
b) An encrypted overlay file system allows for incrementally backing up changed assets, but exposes considerable metadata (rough file sizes, directory structures, modification dates).
The most widely used package for this is probably #gocryptfs. Its "HowTo" is literally a one-pager: https://nuetzlich.net/gocryptfs/quickstart/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(24/N) There are some best practices that will make it easier to answer threat modeling question #3, "What are you going to do about it?". These will help you protect a wide range of assets by taking care of your devices, so let's look at them first:
- Encrypt data at rest
- Bootstrap your workplace
- Actively maintain your devices
- Secure your devices
- Prepare for repair
1. Encrypt data at rest
What can you achieve with intermediate knowledge, without fully descending into the rat hole?
⚠️ Caveat: this is best done when setting up #Linux on a new device. Modifying an existing installation on your own IMHO isn't advisable if you're not a seasoned user. If you still decide to venture into it, make SURE you have backed up all your assets, before following "howtos on the internet". You have been warned.
Likening your device to a medieval city:
1) Full-Disk Encryption (FDE) is like locking the "city gate". Most popular Linux distributions offer FDE during the installation process. FDE is also your last line of defense when your device gets stolen, or your disk fails and cannot be safely wiped before disposing of it. Use FDE. (Yes, technically, "Full" is not absolutely accurate. We'll leave it at that.)
2) Within your "city", there will likely be at least two "houses": the home of the admin account, and your personal home. Using FDE alone, the "doors" of these homes won't have any locks of their own. Possibly not a big deal with respect to the administrative account, but admins being able to access any of your non-public assets, even when you're not logged in, is probably not what you want.
While the specific steps depend on your preferred Linux distro, a "portable" solution is to create a separate, encrypted disk partition, and have it mounted as your user home directory, when you log in. That solution is based on cryptsetup and the pam_mount module, a nice tutorial example is:
3) Within your "house", you may wish to have a locked "chest", e.g. for your #FYEO assets. There's essentially two options: a) a single, encrypted container file that acts as a "#vault" for your asset files; or b) an encrypted overlay file system that maintains an openly visible directory hosting your encrypted assets, including directory structures, in the background; and allows you to mount a decrypted counterpart, for working on your assets.
a) A "vault", being a single file, is easy to copy and carry around, on arbitrary storage media, e.g. USB sticks. It doesn't reveal too much about its contents, but resizing it takes a little effort. Also, you can't "incrementally backup" content changes, just copy the whole, changed vault.
A nice tutorial for creating and using a vault using plain, standard cryptsetup is https://opensource.com/article/21/4/linux-encryption by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt https://mhogomchungu.github.io/zuluCrypt/ – IMHO the app is still in need of a little polish, though.
b) An encrypted overlay file system allows for incrementally backing up changed assets, but exposes considerable metadata (rough file sizes, directory structures, modification dates).
The most widely used package for this is probably #gocryptfs. Its "HowTo" is literally a one-pager: https://nuetzlich.net/gocryptfs/quickstart/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(17/N) Finally, two threat types that refer to security more than privacy:
An adversary destroys, withdraws, steals or misappropriates information, access, or resources. The obstruction can be temporary or permanent, partial or total. Obstructing can also occur unintentionally, with the “adversary” being deterioration, malfunction, or disaster.
An adversary deliberately corrupts the integrity or authenticity of information, resources, processes, or interactions. The respective information, resources, processes, or interactions aren’t necessarily controlled or owned by the persons that are affected, and may also be fabricated. Interfering can also occur unintentionally, with the “adversary” being deterioration, malfunction, or disaster.
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(15/N) Two more threat types defined:
Undesirable non-repudiation or repudiation
#Repudiation (plausible denial) of what somebody has said / done / known / possessed becomes impossible because an adversary has managed to collect enough evidence to establish undesirable non-repudiation. In other words: the adversary can prove beyond reasonable doubt that "it" happened.
Alternatively, #NonRepudiation (proof beyond reasonable doubt) cannot be established because an adversary has managed to suppress or destroy enough evidence to gain the option of repudiation (plausible denial). In other words: the adversary can plausibly deny "it" happened.
Detecting
An adversary can check for the presence or absence of specific data items, which are tell-tale indicators for something else.
(to be continued)
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(14/N) Having familiarized ourselves with categories of adversaries, their main goals and their respective, overall "modus operandi", let's look at the types of threats posed by them.
Again, it pays to focus on types of threats: We don't want to become mainly alert-triggered, but proactive. There are several frameworks we can borrow ideas from, most notably the LINDDUN framework that is geared toward threats to privacy, and can be extended a bit to cover more ground.
First, our list of threat types:
- #Linking (spotting connections and relationships)
- #Identifying (mapping to identities)
- Undesirable #NonRepudiation or #repudiation
- #Detecting (absence or presence of indicators)
- Data #disclosure (to the unauthorized)
- Manufacturing cooperation (disguised or imposed bad consequences)
- #Obstructing (access, information, resources)
- #NonCompliance
- #Interfering (with information, resources, processes, interactions)
Our definitions of these, for our context:
Linking
An adversary can figure out connections and relationships between formerly isolated items of interest.
Identifiying
An adversary can link items of interest directly to a natural person.
(to be continued)
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865LINDDUN:
https://linddun.org/ -
#4D
#Andalucismo
Pero sólo vale si soluciona los problemas del día a día de las andaluzas y andaluces, mejorando sus condiciones de vida.
Todo un reto para hacer una política diferente.
💚🤍💚 -
(6/N) A final set of prompts, for three more categories. Add the related data "assets" that come to your mind to your spreadsheet:
#Geospatial data
- Current #position
- Place of residence
- GNSS-precision tracks
- Appointment #calendars
- #Ticket purchases
- Room #reservations…
- Email & Messaging (including content)
- Social media
- Cloud
- Pseudonyms & personas…
Remember many data "assets" will fall into multiple categories. For every asset, leave a checkmark in all applicable category columns.
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
(4/N) Having reflected a bit on your abstract assets, try to brainstorm as many of your related data and device assets as possible. Most of them will fall into one or more of the following categories:
- Personally Identifiable Information (#PII)
- Social graphs
- Data and metadata
- #Geospatial data
- Infrastructure
- #Accounts and #handles
For instance, your smartphone photo collection "asset" probably contains geospatial data (#GPS coordinates in #EXIF); data and metadata (phone brand and model, in EXIF); potentially also information about your social graph, in case your family, friends or acquaintances are on your photos.
It's probably best to track your data and device assets in a spreadsheet, with the above categories as additional columns, so you can place a checkmark, where appropriate. I'd also suggest to add a column to track where the data is stored / the device is located.
Here's a little list of Personally Identifiable Information (PII), to get you started (other categories in next posts):
- Any kind of identity document
- Dates of significant life events
- #Biometric data
- #Health data
- #DNA test results
- #Genealogy data…
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865 -
#4dToys: a #Box of #Four #Dimensional #Toys
We've shared this #video before, but it's one of our favorites on the problem of #visualizing or #conceptualizing higher #dimensional #geometries. The 4th dimension is not always #Time, but is perpendicular to the lower 3. Watch as these objects slip in & out of our #World, like #TimeTravelers!
🔗 https://www.youtube.com/watch?v=0t4aKJuKP0Q 02 Jun 2017
🔗 https://Wikipedia.org/wiki/Four-dimensional_space#Community #TimeTravel #Research #4d #vr #tesseract #hypercube #hypersphere #KrononautMoon
-
#4dToys: a #Box of #Four #Dimensional #Toys
We've shared this #video before, but it's one of our favorites on the problem of #visualizing or #conceptualizing higher #dimensional #geometries. The 4th dimension is not always #Time, but is perpendicular to the lower 3. Watch as these objects slip in & out of our #World, like #TimeTravelers!
🔗 https://www.youtube.com/watch?v=0t4aKJuKP0Q 02 Jun 2017
🔗 https://Wikipedia.org/wiki/Four-dimensional_space#Community #TimeTravel #Research #4d #vr #tesseract #hypercube #hypersphere #KrononautMoon
-
#4dToys: a #Box of #Four #Dimensional #Toys
We've shared this #video before, but it's one of our favorites on the problem of #visualizing or #conceptualizing higher #dimensional #geometries. The 4th dimension is not always #Time, but is perpendicular to the lower 3. Watch as these objects slip in & out of our #World, like #TimeTravelers!
🔗 https://www.youtube.com/watch?v=0t4aKJuKP0Q 02 Jun 2017
🔗 https://Wikipedia.org/wiki/Four-dimensional_space#Community #TimeTravel #Research #4d #vr #tesseract #hypercube #hypersphere #KrononautMoon
-
#4dToys: a #Box of #Four #Dimensional #Toys
We've shared this #video before, but it's one of our favorites on the problem of #visualizing or #conceptualizing higher #dimensional #geometries. The 4th dimension is not always #Time, but is perpendicular to the lower 3. Watch as these objects slip in & out of our #World, like #TimeTravelers!
🔗 https://www.youtube.com/watch?v=0t4aKJuKP0Q 02 Jun 2017
🔗 https://Wikipedia.org/wiki/Four-dimensional_space#Community #TimeTravel #Research #4d #vr #tesseract #hypercube #hypersphere #KrononautMoon
-
#4dToys: a #Box of #Four #Dimensional #Toys
We've shared this #video before, but it's one of our favorites on the problem of #visualizing or #conceptualizing higher #dimensional #geometries. The 4th dimension is not always #Time, but is perpendicular to the lower 3. Watch as these objects slip in & out of our #World, like #TimeTravelers!
🔗 https://www.youtube.com/watch?v=0t4aKJuKP0Q 02 Jun 2017
🔗 https://Wikipedia.org/wiki/Four-dimensional_space#Community #TimeTravel #Research #4d #vr #tesseract #hypercube #hypersphere #KrononautMoon
