Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL So 28.07.2024 00:00:03 44.194 +6 4.532.806 102,6 troet.cafe - Mastodon 4.2.8 500 Sa 27.07.2024 00:00:07 44.188 +9 4.527.587 102,5 troet.cafe - Mastodon 4.2.8 500 Fr 26.07.2024 00:00:04 44.179 +6 4.522.208 102,4 troet.cafe - Mastodon 4.2.8 500 Do 25.07.2024 00:00:02 44.173 +6 4.516.980 102,3 troet.cafe - Mastodon 4.2.8 500 Mi 24.07.2024 00:00:03 44.167 +8 4.511.807 102,2 troet.cafe - Mastodon 4.2.8 500 Di 23.07.2024 00:00:02 44.159 +12 4.506.313 102,0 troet.cafe - Mastodon 4.2.8 500 Mo 22.07.2024 00:00:06 44.147 +7 4.501.220 102,0 troet.cafe - Mastodon 4.2.8 500 So 21.07.2024 00:00:02 44.140 +5 4.495.698 101,9 troet.cafe - Mastodon 4.2.8 500 Sa 20.07.2024 00:00:03 44.135 +5 4.491.275 101,8 troet.cafe - Mastodon 4.2.8 500 Fr 19.07.2024 14:00:09 44.130 0 4.488.188 101,7 troet.cafe - Mastodon 4.2.8 500
Mⱺ℠ (@nevali) · 11/2022 · Tröts: 10.545 · Folger: 644
So 28.07.2024 16:14
because i went to the trouble of mapping all of the standard LDAP attributes and classes into my schema infrastructure i automatically have broadly-understood interface definitions and accompanying client classes for a whole bunch of things, many of which are pretty straightforward to layer on top of standard APIs once the basic infra's in place
this posixAccount class for example, from the NIS-LDAP mappings, would be trivial to implement atop getpwent()
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Web