Show more

@rysiek Coming from a company that aggressively filter out queer people and people who aren't conventionally beautiful from their front pages, I find it hard to imagine them being transparent about their own "algorithms"

Where your data is stored and who has access to it already matters, but it will matter more in future. Unless there's some serious pushback the problems with spying and manipulation by algorithms will continue to increase. The recent #HOPE talks about Amazon Ring are an indicator of the way things are going.

One of the strict advantages of #gemini over #gopher is its explicit support for Unicode text, which means it can be used to c̴̳͐̄o̵̦̞̭͊̂̈́̄n̷̺̈́̓ṿ̷̰̗̅̈̅̇ḛ̴̞̘̏̒̎̊y̸̖̰͓̱̽͛̄͝ ̴̼̺́̂͝͝ͅm̴̤̰̫͎̾̊e̴̛̝͉͠s̸̤̯͛͝s̴̱̄͋a̴͉̍̔ḡ̶̮͝͠e̴̮͓͂s̸̨͈̹͇̓̏̀͝ ̸̰̜́̎f̸͓̰̞̈̂̇́ͅr̷̫͗ó̵̺͖͔͇͐̽͘m̷͙͊͛̍ ̸̖̒b̵̛̤̂̀̑ḛ̷̼̥̙͂̔́͐y̵̙͈̭̳̌̅̐̚o̴̪͖̗͐̾́͘n̸̻̲͇͚̊ḑ̸̣̏͆͝ ̷̥͎̇͘t̴̖̖̾̽h̶͊͊̅ͅͅę̶̰̘̂͐̊ ̶̧̡̨͈̎̇Ȯ̶͈͙̪̗u̵̬͈̼͗t̴̜͂̐̊͛e̷͇̯̿̌̑r̵̨͙͔̃̃͊͠ ̴̧̱̮̜͊G̵̦̯̰͒ä̸̜t̵̪̲́ͅe̶̊̑̓͊͜s̷̒̔͒̾ͅ.̵̢̢͙̆.

@wolf480pl @alex because GTK markup does know nothing about paragraph HTML element 😔️

@alexcleac
Ok, but if you didn't delete it, your later regex would make it linebreak, no?
@alex

@wolf480pl @alex basically, yes. Here I presumed that <p> tags are followed by other <p> tags, so closing of paragraph creates line break which is needed to display the paragraph...

But I've just figured out that I should remove only leading <p> tag, while replacing every other with line break.

I think I've figured out, how to escape html tags in a way it does not break in #Olifant, when using #Pleroma. Not a good way IMO, but at least it is more or less easy to predict behavior 😄️

Just realised that I never really shared that I wrote a small npm package to send #WebMentions a while ago. It's automatically tested against the full webmention.rocks test suite, work in both Node and the browser, and includes type definitions.

This work was supported by @NGIZero and is currently used in production on plaudit.pub.

You can find it here: npmjs.com/package/webmen

Shadow attacks: hiding and replacing content in signed PDFs
pdf-insecurity.org/

(submitted by fanf2)

So I've often said that Google doesn't deserve credit for Go, and that Go is the product of a small number of language designers and derives from a history of system design which is external to Google. What Google has done with it since becoming its steward is, on the whole, more negative than positive. 

I can now hold up pkg.go.dev as more evidence of this fact. It's obviously a product of the dysfunctional Google corporate engineering culture rather than a product of the principles that underlie Go's design. The care and deliberacy which went into Go's engineering design choices is entirely absent from pkg.go.dev.

1. Was big old monolith born from Google's giant monorepo with no intentions of open sourcing until the community pressed the issue

2. Drops support for generating docs locally or hosting them off-site

3. Discussion hosted on a Slack channel

4. Hard-codes a list of centralized git hosts, despite being told that this is now how git works

5. Refuses to consider language-agnostic approaches to Go package hosting, instead forcing downstream git hosts to add Go-specific support

Basically, good engineering has been abandoned in favor of promoting Google's interests and a corporate, centralized view of the software ecosystem

...again.

is this a fucking joke, I literally cant see what the design community is saying

#GDPR and #CCPA are not the “ultimate” in #privacy.

Like building code, they should be seen as the minimum standards by which we protect personal information.

Always strive for a higher degree of data protection.

As a business or website owner, place your users privacy at least equal to your own needs as a minimum. Try to get and use the least amount of information possible to process their requests.

pkg.go.dev is more concerned with Google’s interests than good engineering

drewdevault.com/2020/08/01/pkg

Congrats to the #Linux kernel development community for refusing to compromise principles over convenience and refusing to mainline a module that interacts with a proprietary one.

lwn.net/SubscriberLink/827596/

Major props.

Show more
FLOSS.social

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).