31 Matching Annotations
  1. Sep 2025
    1. Perhaps we should expect to see more elections that are eitherextremely close or extremely lopsided from here on out. If opposingSiren Servers are well run, they might achieve parity, while if one isbetter than the other, its advantage ought to be dramatic. It’s too earlyto say, since big data and politics haven’t mixed long enough togenerate much data as yet. It’s like climate change was for a long time—not enough data yet to really say—though it does look like we’reseeing this pattern.

      are we seeing patterns? who/what are the big influencers?

    2. In our digital revolution, we might depose an old sort ofdysfunctional center of power only to erect a new one that is equallydysfunctional. The reason is that online opposition to traditional powertends to promote new Siren Servers that in the long run are unlikely tobe any better.
    3. While we have yet to see how Google’s book scanning will play out, amachine-centric vision of the project might encourage software that treats books as grist for the mill,decontextualized snippets in one big database, rather than separate expressions from individual writers. Inthis approach, the contents of books would be atomized into bits of information to be aggregated, and theauthors themselves, the feeling of their voices, their differing perspectives, would be lost. Needless to say,this approach would hide its tracks so that it would be hard to send a nanopayment to an author who hadbeen aggregated.

      Alternately, where is the value in a slip box?

    4. It’s not always necessary that the data be made absolutelyunavailable; sometimes data can just be decontextualized enough tobecome less valuable. Facebook provides a fine example. If a greatdeal of personal creativity and life experience has been added to thesite, it’s hard to give all that up. Even if you capture every little thingyou had uploaded, you can’t save it in the context of interactions withother people. You have to lose a part of yourself to leave Facebookonce you become an avid user. If you leave, it will become difficult forsome people to contact you at all.
  2. Feb 2025
  3. Aug 2024
  4. Jun 2024
  5. Jul 2021
  6. May 2021
    1. I want to avoid nginx overhead (especially if they have tons of alias and rewrites) for in-server communication. Basically, you can have sveltekit server, backend server and nginx server, in that case, communicate inside your internal network will be very expensive like: browser->nginx server(10.0.0.1)->sveltekit server(10.0.0.3)->nginx server(10.0.0.1)->backend server(10.0.0.2) instead just: browser->nginx server(10.0.0.1)->sveltekit server(10.0.0.3)->backend server(10.0.0.2)
  7. Feb 2021
  8. Oct 2020
  9. Aug 2020
  10. Mar 2020
    1. The fastest way to preventively block the scripts that require prior consent is to install a module on your own server that we have developed for Apache, IIS and NGNIX. After the initial configuration, the module will autonomously block all the resources that are subject to prior consent, on all sites on that server that are using the Cookie Solution.
  11. Feb 2020
  12. Oct 2019
  13. Nov 2018
    1. n the Advanced Security Settings dialog box, make sure that SELF is listed under Permission entries. If SELF is not listed, click Add, and then add SELF.Under Permission entries, click SELF, and then click Edit.In the Permission Entry dialog box, click the Properties tab.On the Properties tab, click This object only in the Apply onto list, and then click to select the check boxes for the following permissions under Permissions:Read servicePrincipalNameWrite servicePrincipalName

      Permissions needed for AD account to write SPN name

    1. The client and server computers must be part of the same Windows domain, or in trusted domains. A Service Principal Name (SPN) must be registered with Active Directory, which assumes the role of the Key Distribution Center in a Windows domain. The SPN, after it is registered, maps to the Windows account that started the SQL Server instance service. If the SPN registration has not been performed or fails, the Windows security layer cannot determine the account associated with the SPN, and Kerberos authentication will not be used.

      2 main criteria for linked servers to pass through AD credentials

      1. be on the same domain
      2. have an SPN registered for the AD account running the SQL service