#phabricator — Public Fediverse posts

Ah yes, because nothing screams "informative" like a digital wild goose chase through URLs and robot policies 🤖📜. Seriously, who needs actual content when you can just link to a ticket on Phabricator? 🙄 #ContentGoals
https://en.wikipedia.org/wiki/Western_Sahara #digitalwildgoosechase #informative #contentgoals #Phabricator #robotpolicies #techhumor #HackerNews #ngated

🤖 Ah, the thrilling saga of the German Peasants' War, where the real battle was against Wikipedia's robot policy! Because nothing screams "historical conflict" quite like setting a user agent and navigating a labyrinthine link to #phabricator. 🥳🌾
https://en.wikipedia.org/wiki/German_Peasants%27_War #GermanPeasantsWar #WikipediaRobotPolicy #HistoricalConflict #UserAgent #HackerNews #ngated

Ah, the elusive 'Freeze-Casting' technique: apparently, it's a top-secret method only accessible to those who set their user agents correctly and offer sacrifices to the almighty Robot Policy gods 🚀🔒. Did you know it's also a favorite pastime of #squirrels on #Phabricator, T400119? 🌰💻 Clearly, the future of science relies on cryptic hyperlinks and a dash of mystery! 🧙‍♂️✨
https://en.wikipedia.org/wiki/Freeze-casting #FreezeCasting #RobotPolicy #MysteryScience #HackerNews #ngated

🍿 Oh, the irony! An article about "BLISS" that's more like a robot rebellion manifesto, complete with demands for #useragent #respect. Apparently, finding happiness now involves spelunking through URLs and deciphering #Phabricator tickets. 🤖✨
https://en.wikipedia.org/wiki/BLISS #BLISS #robotrebellion #irony #HackerNews #ngated

Ah, the thrilling world of PID controllers! 🌟 Who knew that setting a user agent was the secret to understanding this arcane sorcery? Clearly, the real #magic lies in navigating obscure wiki pages and deciphering #Phabricator tickets. 🧙‍♂️✨
https://en.wikipedia.org/wiki/PID_controller #PIDcontrollers #UserAgent #WikiWisdom #TechSorcery #HackerNews #ngated

It’s been over two years since I last submitted a #Wikimedia #Phabricator ticket, so I guess I should submit a new one for a weird bug on #WikimediaCommons involving structured data via #Wikibase. 😝

https://phabricator.wikimedia.org/T429008

Ah, the U.S. Army Corps of Engineers Bay Model: where the most thrilling adventure is navigating a broken link! 🙄 Why explore real-life engineering marvels when you can set a user agent for an epic journey through #phabricator pages? 🚀💤
https://en.wikipedia.org/wiki/U.S._Army_Corps_of_Engineers_Bay_Model #USArmyCorps #BayModel #EngineeringAdventure #BrokenLinks #UserAgentExploration #HackerNews #ngated

Bug 1950764: Work Around Crash on Intel Raptor Lake CPU

https://phabricator.services.mozilla.com/D301917

#HackerNews #BugFix #RaptorLake #IntelCPU #Mozilla #Phabricator #TechNews

Access denied

Is <https://reviews.freebsd.org/D53910/> not accessible for anyone other than me?

In a private browsing window – without logging in.

For me, it is:

A/ accessible at my sister's home

B/ not accessible at my home

C/ not accessible in Tor Browser.

(I assume that my home address is blacklisted.)

Postscript: explained at <https://mastodon.bsd.cafe/@grahamperrin/116598332566866701>.

#FreeBSD #Phabricator

🎬🤖 So, the #bot #police at #Wikipedia have gone full #Skynet, demanding user agents like it's the secret handshake to the nerd club. Meanwhile, #phabricator.page has become the ultimate rabbit hole for people who think "404" means "try again later." 🙄🔍
https://en.wikipedia.org/wiki/Colossus:_The_Forbin_Project #UserAgents #RabbitHole #HackerNews #ngated

I sometimes believe that Phabricator is AI

― active impediment.

Like, where documentation goes to die.

Process without progress.

<https://reviews.freebsd.org/D47996> et cetera.

#FreeBSD #documentation #Phabricator

@charlesrocket @meena @dch @trashheap

Ah, the #nostalgia of a London-Calcutta bus trip: 🌍🚍 a journey so riveting, even Wikipedia bots are blocking access to its secrets. 😱📵 But fear not, because #phabricator will definitely clear things up... if you ever decode its labyrinthine existence. 😂🔍
https://en.wikipedia.org/wiki/London%E2%80%93Calcutta_bus_service #London #Calcutta #BusTrip #WikipediaBots #HackerNews #ngated

💻 Ah, the formidable 'Pole of Inaccessibility'—where setting a user agent is the zenith of your exploration skills and respecting robot policies makes you a digital hero. 🦸‍♂️ Meanwhile, the wilds of #Phabricator are eagerly awaiting your next epic quest to nowhere. 🗺️🤖
https://en.wikipedia.org/wiki/Pole_of_inaccessibility #PoleOfInaccessibility #UserAgent #DigitalHero #EpicQuest #HackerNews #ngated

Whenever I search in #Phabricator and have to enter an item type I get annoyed that it does an API request to autocomplete. There are only 14 types, and they haven't changed for years, and they're only a couple of words each. Just load the data *with* the search form!

https://phabricator.wikimedia.org/typeahead/class/

@HeroOfDermwood many years ago I used @openproject and it worked just fine for a smaller org. It has greatly matured since then. It also comes with a Trello-like KanBan board feature:
https://www.openproject.org/docs/user-guide/agile-boards/

Alternatively, you might want to take a look at https://taiga.io/ - from the same people also behind @penpot

I'm still sad #Phabricator isn't actively developed anymore. The single best (even though heavily opinionated) fully integrated project management software I've ever used.

https://phabricator.wikimedia.org/maniphest/query/U2YI8v_t36_O/#R

#Phabricator

That's what you get for trying to be cute with examples instead of simply showing the #pronoun choices.

#Phabricator #webdev #PronounPicker

It's a few days late, But this year is our 10th anniversary of the #WikimediaFoundation started it's final steps in the #Bugzilla to #Phabricator migration, On the 2014-11-21 the import of the old Bugzilla archives into the Phabricator started, access to Phabricator to the public was reopened 2014-11-24.

"You know, I come to #Wikimania to find more bugs in my software, because there aren't enough in #Phabricator already"

#QOTD by James Forrester @jdforrester

@michaelgalassi @dexter Just one thing regarding #FreeBSD's #Phabricator. It is better to create an account earlier because the sign up process requires a manual approval from an admin I think.

@michaelgalassi @dexter It is definitely the right way. Sometimes, when the patch is larger and requires more code review, then it is good to post it to https://reviews.freebsd.org/ along opening a Problem Report on https://bugs.freebsd.org/. In other words, #Bugzilla is the source of truth. #Phabricator is just an extra service #FreeBSD uses for code review.

#foss #opensource

@cuddle thanks!

FreeBSD-related publications — including old covers of books, magazines, and CDs:

<https://people.freebsd.org/~grahamperrin/273360/273360-hacked-for-images.pdf> (PDF) was a July 2023 attempt to recreate a FreeBSD Project page that had suddenly disappeared.

<https://web.archive.org/web/20230419231932/https://www.freebsd.org/publish/> (HTML) captured an October 2021 edition that lacked important changes to the head of the page.

For posterity, a broader list of disappearing pages:

<https://old.reddit.com/r/freebsd/comments/1725uf6/for_posterity/>

Partial background to the disappearances: <https://reviews.freebsd.org/D41963#959831> (it seems that there was no review process for removal of the publications page, which was referenced from a copyright page). The subsequent commit was partly reverted by <https://github.com/freebsd/freebsd-doc/commit/486cc10e25df3f7e6190f18bc277bdd31e20a926> without reference to the problematic commit.

#FreeBSD #history #publications #books #magazines #CD #DVD #copyright #Phabricator #review #documentation #project #website #web

@hiroo3 @emaste The best idea is to post it on #FreeBSD #Phabricator for review (https://reviews.freebsd.org/). A subsequent email to hackers at freebsd.org announcing that the review is up and that you seek feedback would get community's attention. :) Nice work

@abbe98 @Ladsgroup It's not really about development itself but I am hopeful that the migration to #Gitlab will help, by making the contribution workflow more welcoming. But if I understood correctly #Phabricator will stay and I hope the integration between the two will be good enough

It's time again to complain about #Phabricator turning your uploaded patches into diffs that can't be `git am`-ed.

Seriously, #LLVM, how can you still force people to use that?!

::: SOLUS Linux back stronger than ever! :solus:

The new Solus team will be elaborated tomorrow 18.4. Tuesday.

* Process for a an alternative infrastructure for Solus has been initiated

* A new binary package repository server that has been validated

* A new server has been brought up

* Josh Strobl is back

=> https://teddit.net/r/SolusProject/comments/12ndrvt/righting_the_ship

#Solus #Linux #back #team #developers @JoshStrobl #news #infrastructure #development #server #Flarum #Phabricator #OpenCollective