mirror of
https://github.com/pxdg-afk/paxad.git
synced 2026-08-23 03:01:08 -04:00
Compare commits
10 Commits
40f94955c3
...
v5
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1427bcd616 | ||
|
|
252184e1e4 | ||
|
|
b5e3c2b762 | ||
|
|
8908ee8e1f | ||
|
|
120f6bef30 | ||
|
|
a2464a05ef | ||
|
|
d686ca3fe3 | ||
|
|
8b60e3a0a4 | ||
|
|
5098abcfdb | ||
|
|
03be7bd6c2 |
8
.obsidian/types.json
vendored
Normal file
8
.obsidian/types.json
vendored
Normal file
@@ -0,0 +1,8 @@
|
|||||||
|
{
|
||||||
|
"types": {
|
||||||
|
"aliases": "aliases",
|
||||||
|
"cssclasses": "multitext",
|
||||||
|
"tags": "tags",
|
||||||
|
"date": "date"
|
||||||
|
}
|
||||||
|
}
|
||||||
76
content/fnn/BARQ Public Statement.md
Normal file
76
content/fnn/BARQ Public Statement.md
Normal file
@@ -0,0 +1,76 @@
|
|||||||
|
---
|
||||||
|
date: 2026-07-15
|
||||||
|
publish: true
|
||||||
|
tags:
|
||||||
|
- furry
|
||||||
|
- barq
|
||||||
|
- babyfurs
|
||||||
|
- furry-drama-cycle
|
||||||
|
- anthrocon-2026
|
||||||
|
---
|
||||||
|
|
||||||
|
Full text of the public statement, as posted to Twitter July 15, 2026, at 10:14 AM EDT:
|
||||||
|
|
||||||
|
> Apologies for the long wait.
|
||||||
|
> We want to give some clarification on what happened last week with the posting and removal of our statements regarding Flame and the babyfur community.
|
||||||
|
>
|
||||||
|
> At Anthrocon, the BARQ!Cast held a panel where Flame was invited as a guest. After that panel we saw Flame making hateful comments toward the babyfur community on X. Because this goes against everything BARQ! stands for, we decided to quickly put out a statement distancing ourselves from Flame.
|
||||||
|
>
|
||||||
|
> This was agreed upon by our social media team and directors. Looking back at the first statement, we felt it was too vague. We decided to post a second one, which was also agreed upon by all involved.
|
||||||
|
>
|
||||||
|
> A day later we found out the second statement was only posted on Bluesky. We tried to fix that apparent mistake by posting it on X too. When our social media team noticed the new posts, they told us they hadn't posted it to X on purpose and in a panic, they deleted both statements from X and Bluesky.
|
||||||
|
>
|
||||||
|
> What followed was a lot of confusion, both within the team and our community. We decided to pause posting anything on this matter and discuss / reflect on what happened first. We found the biggest factor in this was that we never talked about who is responsible for what, and that some decisions were made without consulting the others who are involved.
|
||||||
|
>
|
||||||
|
> We want to make it clear we still stand behind both statements, and that babyfurs are part of the community and welcome on BARQ! just as every other furry. We agreed on clearer responsibilities and clear lines of communication to make sure this will not happen again.
|
||||||
|
> Discrimination has no place on BARQ!
|
||||||
|
>
|
||||||
|
> - BARQ! Directors
|
||||||
|
|
||||||
|
Some things of note:
|
||||||
|
|
||||||
|
> Looking back at the first statement, we felt it was too vague. ==We decided to post a second one, which was also agreed upon by all involved.==
|
||||||
|
|
||||||
|
Was the *decision to make a post* agreed upon or the *content of the post itself*?
|
||||||
|
|
||||||
|
> A day later ==we found out the second statement was only posted on Bluesky. We tried to fix that apparent mistake by posting it on X too.==
|
||||||
|
|
||||||
|
So you okayed the post with the social media team, gave them the go-ahead on posting, but they independently chose to only post to Bluesky...
|
||||||
|
|
||||||
|
> \[... the social media team] told us ==they hadn't posted it to X on purpose== ...
|
||||||
|
|
||||||
|
...why? Were they attempting to tailor different messages for each platform? Why not just post the same message to both? It's a public statement disavowing a person with negative views toward a sizable segment of the community...wouldn't you want to post this literally everywhere?
|
||||||
|
|
||||||
|
> \[...] we ==never talked about who is responsible for what== ...
|
||||||
|
|
||||||
|
If I were working for your company on the social media team, I would think my team would be the ones responsible for...social media. Including making and releasing public statements that affect the company's public image. Otherwise, if there were a Public Relations person or department or a designated public company spokesperson, I'd defer to them.
|
||||||
|
|
||||||
|
> \[...] some decisions were made ==without consulting the others who are involved==.
|
||||||
|
|
||||||
|
Social media team's director went rogue and decided to only post the message to Bluesky because they didn't want to moderate the potential wave of negativity that posting the same exact message on X might cause?
|
||||||
|
|
||||||
|
p.s. Who is Flame anyway?
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
https://x.com/flamethefawn
|
||||||
|
- 20
|
||||||
|
|
||||||
|
> this is the last time i'm going to speak on this issue, anything i have said is not a reflection on @barqOfficial as a company, it is strictly my own opinion.
|
||||||
|
>
|
||||||
|
> i stated in my initial apology that i regretted my wording and calling for violence, which is true i do regret that. i also would like to say that yes, i have made generalizations in response to generalizations and personal attacks made against me which was also not right. the world isn't black or white and i believe that i was wrong for letting that worldview bleed into my comments
|
||||||
|
>
|
||||||
|
> fuck pedophilia, wherever it lays. i see a glaring issue within the furry community with how we turn a blind eye to these predators that prey on our own community members. they are terrible people and it deeply upsets me.
|
||||||
|
>
|
||||||
|
> not every person who has an abdl kink or who is a babyfur is a bad person and i don't believe we should be violent towards people who are into things that you may not be into. i want to make my position clear on that.
|
||||||
|
>
|
||||||
|
> i am not sorry for having my own opinions, if you dissent them then that is totally fine as well. babyfurs and furries as a whole need to do better rooting out pedophilia, \[zoophilia], and other aspects of our community that are morally abhorrent
|
||||||
|
> [source](https://x.com/flamethefawn/status/2077426761751756988)
|
||||||
|
|
||||||
|
> i think people don't realize how influential this new young wave of furries my age are, and how awesome the changes we are going to bring will be :3
|
||||||
|
|
||||||
|
not sure what this even means, but not sure i want to be here for it either.
|
||||||
|
|
||||||
|
i can see why there's a trend recently for new conventions to be 21+.
|
||||||
|
|
||||||
|
as long as you're not a puritanical dickhead, I think we'll get along fine. that "morally abhorrent" language veers mighty close to "degenerate" if you ask me. *but that's just my opinion.*
|
||||||
@@ -1,15 +1,26 @@
|
|||||||
---
|
---
|
||||||
|
publish: true
|
||||||
aliases:
|
aliases:
|
||||||
- tailtag
|
- tailtag
|
||||||
|
created: 2026-07-12T17:55:57.560-04:00
|
||||||
|
modified: 2026-07-12T18:24:12.896-04:00
|
||||||
tags:
|
tags:
|
||||||
- furry
|
- furry
|
||||||
- AI
|
- AI
|
||||||
- vibe-coding
|
- vibe-coding
|
||||||
publish: false
|
description: "tl;dr: TailTag (fursuit \"catching\" app to promote socialization with suiters) had backend access open to normal users, some of whom were able to view other users' email addresses and private posts. The app is offline until patches can be applied."
|
||||||
---
|
---
|
||||||
several online sources have indicated that the recently popular Pokémon GO-like app "[TailTag](https://www.playtailtag.com)" has been breached and had user information leaked to the public internet.
|
|
||||||
|
|
||||||
> props & excellent thread discussing this incident: https://bsky.app/profile/highlysuspect.agency/post/3mqhuc6bwds2r
|
> [!warning] Update - 7/13/2026
|
||||||
|
> Finn posted a [final response](https://x.com/FinnThePanther/status/2076675644755505535) and a [postmortem report](https://docs.google.com/document/d/17dEvlj6qy71u9dNB_yyk9bH6ywOdj5PpET3bqc8X-RI/edit?pli=1&tab=t.0#heading=h.8gfmgngubb2w) detailing what happened and the steps that will be taken to delete the app data. Finn says he will not move forward with rebuilding the application unless members of the community help out.
|
||||||
|
|
||||||
|
not a journalist, just a dog who went to school for it (kind of) and collated the work done by several others; links included with information as well as in footnotes below the article
|
||||||
|
|
||||||
|
[**TailTag**](https://www.playtailtag.com), a recently released furry social app, was breached on July 11, 2026, leading app creator Finn the Panther to shut down the app temporarily while security issues are being addressed.
|
||||||
|
|
||||||
|
> [!tip]+ sources, yo
|
||||||
|
> super props & excellent thread discussing this incident:
|
||||||
|
> [quat's (@highlysuspect.agency) thread about TailTag on bsky](https://bsky.app/profile/highlysuspect.agency/post/3mqhuc6bwds2r)
|
||||||
|
|
||||||
users were first made aware of the breach when they received a strange push notification from the app titled "IMPORTANT ANNOUNCEMENT" with the message body consisting primarily of "meows" and other cat noises.
|
users were first made aware of the breach when they received a strange push notification from the app titled "IMPORTANT ANNOUNCEMENT" with the message body consisting primarily of "meows" and other cat noises.
|
||||||
|
|
||||||
@@ -21,13 +32,13 @@ Finn's response:
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
twitter user **@twnlink** did a lot of digging on this and discovered some rather alarming configuration errors:
|
twitter user **@twnlink** did a lot of digging on this and discovered backend access was not entirely restricted to admins:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
twitter user [**@Benaclejames**](https://x.com/Benaclejames) posted the following technical write-up of the vulnerabilities discovered on their Notion page: https://app.notion.com/p/TailTag-Vulnerabilities-39bd16d9d17180fa9279ec92bbe19549
|
twitter user [**@Benaclejames**](https://x.com/Benaclejames) posted the following technical write-up of the vulnerabilities discovered on their Notion page: https://app.notion.com/p/TailTag-Vulnerabilities-39bd16d9d17180fa9279ec92bbe19549
|
||||||
|
|
||||||
[**@FloppyMinty**](https://x.com/FloppyMinty) was able to confirm the app's backend information was still publicly accessible as of 11AM EDT on June 12th.[^2][^6] While no user passwords were compromised, just about every other bit of personally identifiable information that users entered into the application is publicly accessible. With proper tools, a malicious actor could view information uploaded to the application in real-time and could theoretically then determine the physical location of specific users and/or the fursuiters they photograph.[^1]
|
[**@FloppyMinty**](https://x.com/FloppyMinty) was able to confirm the app's backend information was still publicly accessible as of June 12th.[^2] Finn did later state in a separate post that the applied fix to the notifications issue should have fixed the access control issues as well.[^6] while no user passwords were compromised, just about every other bit of personally identifiable information that users entered into the application is publicly accessible, including email addresses and photos.[^1] as of writing, other than the publicly disclosed accesses of backend information already mentioned, there is no evidence any others have accessed or posted any data from the application.
|
||||||
|
|
||||||
on July 12, 2026, Finn posted the following response:
|
on July 12, 2026, Finn posted the following response:
|
||||||
|
|
||||||
@@ -42,11 +53,15 @@ on July 12, 2026, Finn posted the following response:
|
|||||||
> \[in later tweets in reply to this original image post]:
|
> \[in later tweets in reply to this original image post]:
|
||||||
> If you would like to assist with future security, access control, or any other parts of the app, please reach out. I am happy to discuss how you can help.[^4]
|
> If you would like to assist with future security, access control, or any other parts of the app, please reach out. I am happy to discuss how you can help.[^4]
|
||||||
|
|
||||||
In the interim, TailTag has been **taken offline** until further notice.[^5]
|
in the interim, TailTag has been **taken offline** until further notice.[^5]
|
||||||
|
|
||||||
most of the comments in response to Finn's own statement were questions about the amount of AI assistance used in the creation of the app. Finn did say "LLMs were involved in the implementation of designs \[he] wrote in English."[^7]
|
most of the comments in response to Finn's own statement were questions about the amount of AI assistance used in the creation of the app. Finn did say "LLMs were involved in the implementation of designs \[he] wrote in English."[^7]
|
||||||
|
|
||||||
[^1]: @BenacleJames: *TailTag Vulnerabilities* - https://app.notion.com/p/TailTag-Vulnerabilities-39bd16d9d17180fa9279ec92bbe19549
|
TailTag's website is still online as of writing. Updates to both the site and application are likely, though no timetable has been announced.
|
||||||
|
|
||||||
|
change your passwords, folks, you'll be alright.
|
||||||
|
|
||||||
|
[^1]: @BenacleJames: _TailTag Vulnerabilities_ - https://app.notion.com/p/TailTag-Vulnerabilities-39bd16d9d17180fa9279ec92bbe19549
|
||||||
|
|
||||||
[^2]: @FloppyMinty: "PSA: If you used TailTag, your email among other metadata has been compromised." https://x.com/FloppyMinty/status/2076320147233493306
|
[^2]: @FloppyMinty: "PSA: If you used TailTag, your email among other metadata has been compromised." https://x.com/FloppyMinty/status/2076320147233493306
|
||||||
|
|
||||||
|
|||||||
15
content/movies/Dune/Butlerian Jihad.md
Normal file
15
content/movies/Dune/Butlerian Jihad.md
Normal file
@@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
publish:
|
||||||
|
tags:
|
||||||
|
- dune/lore
|
||||||
|
---
|
||||||
|
|
||||||
|
> Thou shalt not make a machine in the likeness of a human mind.
|
||||||
|
> *Orange Catholic Bible*
|
||||||
|
|
||||||
|
Ask Gurney Halleck about what the OCB says about thinking machines. Remember, he's supposed to be a "warrior-poet" type character - equally skilled in combat and literature - with one of his favorite tomes being the *Orange Catholic Bible*, naturally. Of all the characters we interact with, he's the one who can quote entire passages verbatim.
|
||||||
|
|
||||||
|
It was the Butlerians who led the charge in the ancient war against the thinking machines. Remember: Paul's story begins in the year **10,191 A.G.** - that is, nearly 10,200 years *after* the formation of the Spacing Guild. Humanity's ability to exist in the vastness of space *relies* on the Spacing Guild's existence.
|
||||||
|
|
||||||
|
> The eye that looks ahead to the safe course is closed forever.
|
||||||
|
|
||||||
@@ -1,19 +0,0 @@
|
|||||||
sometimes a song gets stuck in your head for a long time.
|
|
||||||
|
|
||||||
sometimes it leaves and then comes back a long while down the road.
|
|
||||||
|
|
||||||
these are the latter.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Seventh Wonder - "Alley Cat"
|
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Volbeat - "Fallen"
|
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
super sad lyrics, poignant. with an extremely good and memorable riff.
|
|
||||||
@@ -1,6 +1,6 @@
|
|||||||
# yaml-language-server: $schema=./quartz/plugins/quartz-plugins.schema.json
|
# yaml-language-server: $schema=./quartz/plugins/quartz-plugins.schema.json
|
||||||
configuration:
|
configuration:
|
||||||
pageTitle: "pax.ad"
|
pageTitle: pax.ad
|
||||||
pageTitleSuffix: ""
|
pageTitleSuffix: ""
|
||||||
enableSPA: true
|
enableSPA: true
|
||||||
enablePopovers: true
|
enablePopovers: true
|
||||||
@@ -98,7 +98,7 @@ plugins:
|
|||||||
renderEngine: katex
|
renderEngine: katex
|
||||||
order: 80
|
order: 80
|
||||||
- source: github:quartz-community/citations
|
- source: github:quartz-community/citations
|
||||||
enabled: true
|
enabled: false
|
||||||
order: 85
|
order: 85
|
||||||
- source: github:quartz-community/hard-line-breaks
|
- source: github:quartz-community/hard-line-breaks
|
||||||
enabled: true
|
enabled: true
|
||||||
|
|||||||
Reference in New Issue
Block a user