#futurerestore-help
1 messages · Page 181 of 1
yes ik, its some linux thing
i remember tanbeer googling it
roff is a language used for man pages 

seems like a false positive because I don't see a single man page for futurerestore
@green onyx i told you it was a text processing language
lmfao
man futurerestore
@frigid hare
my friend who thinks im some sort of hacker because i turned off a computer with command prompt
LOL
@zealous bridge on your 14.4 device, have you ever messed with nonce / generator after FutureRestoring
Someone on reddit FR'ed 14.0.1 -> 14.0.1 and generator stayed set
So if you haven't messed with nonce, can you check irecovery -q a few times to see if nonce stays the same and if it's your 0x1111 (or 0x42069??) nonce
i thought I connected too many things
oh yes I was curious about that too
Why is Xbox on there lol
lol not on there anymore
btw @lilac wren for the application is damaged error, does it only show up on big sur or something?
when u had the problem
Not sure but for me it was big sur, lemme see if the other guy said what os
because I was trying to test the solution u gave, and i never had the problem on catalina which is what I have
Yeah they were on Big Sur 11.2.3 as well
ah ok so it is probably a big sur thing
would u be able to try this and see if you still get the message?
weird
because I didn't use that trick last time
well ig there's no harm in using the trick just in case
Dead chat
Just got off work haha
just had someone with an ipad pro 9.7 on iOS 10.3.1 (freshly bought) @lilac wren
now they're returning it
they're returning it because "they don't like iOS 10 and they can't update it to 14"
pussy shit
indeed
imagine folks not knowing that you can change a users mac password by going into recovery and typing in resetpassword
since when do you need a password for recovery?
unless you firmware locked it
'tis why i never update

After futurerestoring my nonce has always been different
But if i disconnect right after Sending filesystem it stays the same
Any later and its reset
mine is 2016 
Since T2 I believe
Lol it is me, idek who the 2 are. Created to message a dev or something but they had DMs off
Yayy
Let's go
It says 4 for me
I'm so famous
Lol
From like shsh.host or something?
Eh the only way it'd be useful is if I read ecid from device to get their link
hi, i'm unjailbroken, i have iPhone 11 on iOS 14.4. Can I use the newest beta of blobsaver to save my blobs of iOS 14.4 ?
me 
yes
when force-revert happens the real rootfs is not mounted so it can't do that
the rootfs is a ramdisk at that moment
aka if you delete everything on the rootfs it's still going to work
Windows: https://github.com/libimobiledevice-win32/imobiledevice-net/releases
macOS: brew install --HEAD libimobiledevice libirecovery
Linux: https://cadoth.net/~nyuszika7h/libimobiledevice-static-linux/
Testing futurerestore lol
Joerestore
So do I
I needed a kanzi to fix it
I think it’s because I have a dualboot
I have triple boot
win mac and linux?
Yes
wish i had the storage capacity to do that
But I have to unplug Linux when I use windows
Because it blocks my 3080 airflow
I need to get a riser cable
Maybe I should do a USB hard drive boot lol
I’m not, I just spent a years paycheck like a dumbass
Wym how
My pc is more expensive than 3 iPhones
I’m low key stupid with money management
Gtg
lol idk then
ik
all of them support pwndfu
how do you even get the ipsw from the ota package? or do you just take the normal ipsw
normal ipsw
oh ok
doubt a pwndfu restore would succeed for me but good to know
lol its getting stuck at checking hashes
yeah id like to know why lol
do i need to replace the ipsw plist file with the ota one or what
why do you need plists
it’s supposed to verify the ota buildmanifest
so do i need to replace that one
no
so why would it fail on verifying it then
i got that kind of error when i checked if the blob some days ago
screenshot the error?
Go to the bottom
It checks all the buildidentities in the BuildManifest so it’s normal for the invalid ones to error out
Looks like log freeze to me
these r the last lines
Might wanna try CLI
before it freezes
yeah ig
ill try
Cleaning up...
[exception]:
what=getting keys failed with error: 13697039 (failed to get FirmwareJson from Server). Are keys publicly available?
code=31260689
line=477
file=futurerestore.cpp
well thats something new
what version are you using
of fr?
Yes
205
Download this file from a browser: https://api.ipsw.me/v2.1/firmwares.json/condensed (right-click, Save as), rename it from condensed.json to firmwares.json, then put it in C:\Users\USERNAME\AppData\Local\Temp\ (Windows) or /tmp/futurerestore/ (macOS/Linux).
By: Tanbeer#4750
ugh is there any tutorial on how to set up that wikiproxy
sudo python3 wikiproxy.py
ez
on linux you need sudo
and cd into where you git clone it
instead of homedir lol
my generator doesnt change while being in dfu mode for like 30 mins right
nah it shouldnt if it’s set in nvram
just go to recovery and check with irecovery -q
you can also just set the generator with irecovery after ipwndfu
just load ibss and run irecovery -c setenv com.apple.System.boot-nonce [generator]
then saveenv
@lilac wren quick question, will your fr work on a device with no sep
aka the iPhone 5
he didnt make fr lol
the gui...
the gui doesnt affect the functionality of fr at all
well heres the thing
it's gonna put in --latest-sep
but this device doesn't have sep
bro
its a fucking iPhone 5
if that has sep im 20 feet tall
use iOS-OTA-Downgrader instead of futurerestore
wait that works?
Yes
shiiiiiiiiiiiiiiiiiit
u right
it has a blobs selection
if this works ill love u forever @zealous bridge
no
its mac or linux
gl
thank u thank u
ok so what the hell is "ModuleNotFoundError: No module named 'flask'
"
pip install flask
module error?
this
Download this file from a browser: https://api.ipsw.me/v2.1/firmwares.json/condensed (right-click, Save as), rename it from condensed.json to firmwares.json, then put it in C:\Users\USERNAME\AppData\Local\Temp\ (Windows) or /tmp/futurerestore/ (macOS/Linux).
By: Tanbeer#4750
did you do this
keeping it running in the background?
yeah its on the first terminal, i opened a second one for fr
ok so i did it again and got a new error
Extracting iBSS.ipad7c.RELEASE.im4p...
payload decrypted
iBoot64Patch: Staring iBoot64Patch!
iBoot64Patch: Inited ibootpatchfinder64!
iBoot64Patch: Failed getting sigpatches!
Cleaning up...
[exception]:
what=assure failed
code=24903695
line=380
file=libipatcher.cpp
was that your error dabezt
@zealous bridge not sure what this means
Might have to edit the futurerestore version
replace it with the latest
Also it couldn’t find the ipsw
Maybe you have to download that yourself
that's odd
Yes you need the IPSW
i put it there
is that one of the "ipwndfu" issues that are currently out there?
Rename it to iPhone.zip cause that’s what it looks like it’s looking for?
Not dire
*sure
@zinc moon
good point
wait
was this ur error?
maybe it needs the ipsw not zipped
yeah
It’s calling unzip
So no
@zinc moon what was your patching error
@pseudo stump yeah it’s a known issue i think
I think you guys need Cryptic’s offsetfinder
Not that commit tho, latest commit is better
are you trying to restore to 14.5+
When all else fails, rewrite from scratch in clean-room or semi-clean-room format in a far superior and modern language 
-Cryptic, 2021
Just a hint to what my side projects are o.O
@zealous bridge wym ci is a rip
O_O
Tihmstar broke ci not me
i got this on mojave
lol what
sounds like an ObjC moment
Oh true
@modern thunder delete /tmp/futurerestore
this is ios ota downgrader?
in the ota downgrader?
cuz this is the lukezdgota downgrader
Idk man
lol looks like shit script possibly
where am i deleting tmp/futurerestore then
Hopefully sep bullshit gets fixed then v197 will be a mega pog release
accidentally triggered emergency call screen while working on passcode tweak 
I mean just do what it says
probably a boolean got converted to a string
@celest basalt do you care if I squash and merge or do you want your commits to be separate when I merge test
Did you even fix the “windows string buffer overflow” thing
I have nothing to do with breaking windows or even fixing it
eh it doesn't really matter but having builds with higher version numbers and then dropping down to a lower version can be confusing
but technically anything above v194 was a test build so meh
lol fair enough you put it on the issue tho
this lol, avoid having to change the version numbers if you can
the problem is tihmstar's dumbass versioning system
the version number shouldn't equal the number of commits
Another benefit to a modern language is that it will support all OS’s natively out of the box 😩... @zealous bridge @celest basalt
when you git clone --depth=1 you end up with futurerestore v1 
Are you trying to rewrite futurerestore or something
No comment
“Gettin' money really changed my mood”
bro someone post me their mac this sucks
why is everything mac only
uh what would i do with that or better how would i use that
lol being a n00b sucks
where did you get your 205 binary from
pins
You might have to compile manually or maybe if @celest basalt can make another static binary with the latest offsetfinder
ahh ok
doubt ill make it but i might try
i love trying new things
Is a wifi-ipad restore really that ‘special’?
well yes
And what’s wrong with using it for normal restores
More people have wifi-only ipads than you think
well, not many use it for ios 13 restores
most people probably do tbh

frr
Doesn’t matter
buying cellular is like idk just doesnt fit
A fix is a fix lol
and also it makes it even more expensive
Yeah if you have an iPhone
What’s the point of a Cellular iPad
yeah just use hotspot and are you really gonna take your ipad out that much
yeah
if it was like 50 dollars, 100 dollars more i’d kinda understand
but it’s like 200 dollars
i bring my ipad places 
bc im weird
and i dont like the dongle for using headphones
Oh shit qiix mem ed
congrats
Easy
lol rly
wasnt he in hospital a few days ago
Rust go brrrr
Oof taking a look at it it looks like hot shit without r/w and a pac bypass
maybe the dev has some exploits idk but it’s gonna be useless by itself
Apparently it’s copy pasted

lol var fuck
nice exploit
Hey
Had a failed future restore of iPhone X
From iOS 14.3 to 14.3
The iPhone cannot turn on
Now
Black screen
Tried all hardware keys combinations
Any clues
press vol up, press vol down, then hold side for as long as it takes
check if the device is detected in iTunes
No the device is not detected
In iTunes
I tried the volume up and vol down
But it fails to reboot
Can you give a screenshot of the error?
Now the error is not visible
As the iPhone is unable to boot
It was almost 80% of restore
Were you using the GUI or CLI?
i have a question about compiling tsschecker, if anyone can help with that
Cli
whats the problem
Can anyone help
You should be in recovery mode at the very least
There no Apple logo at al
i'm able to successfully compile tsschecker on my mac, but it uses libraries I have installed on my system, and I want it to use only the libraries I have installed in this prefix
do you see the connect to computer login
literally gonna kms bruh
14.5+?
Any other solutions @zealous bridge
!t dfu
How to enter DFU mode or enter Recovery Mode on each device
put the device in DFU mode
its in kdfu
Is it a timeout?
as in...
did kDFU timeout?
no
it is right after entering kdfu
what fr version?
That still works?
for this version
did you send the pwnedIBSS?
yes
idk it might be just a bug with odysseusota
which version of idevicerestore?
OH
lol
I know this error
Same shit happens with iOS 14 as well but it says something different
ERROR: Device did not reconnect in recovery mode. Possibly invalid iBEC. Reset device and try again.
!t ibec
Fix for error code 3, 8, and 10 aka the iBEC error in futurerestore
- Uninstall all apple drivers via device manager.
- Uninstall all apple products including itunes and apple device support stuff via control panel uninstall a program. MAKE SURE TO CHECK UNINSTALL DRIVER WHEN UNINSTALLING
- Unplug and replug device.
- Check device manager for more apple stuff and uninstall if so with same driver checkbox.
- Disconnect device.
- Install itunes64 exe from apple.com itself, no windows store bullshit. This is the best version: https://support.apple.com/kb/DL1816?locale=en_US (It will be labeled windows 7, 8 but install it on windows 10, it works fine)
- Plug in device in recovery.
- iboot (recovery) driver should show up under usb in device manager. Uninstall it and check the with software box.
- Run futurerestore.
- Unplug and replug your device.
- Run futurerestore again
Yeah it’s driver issues so trying it on a different PC should help
OdysseusWin
ill do it later
Also, this will NOT change your baseband. If you go too far up or down with iOS version, it may be that the version of iOS you restored to does not understand the baseband left behind by the prior version of iOS.
oh wow
how did i only read this today
Odysseus doesn’t change the baseband
So pwndfu only works until 14.0
F

Other perks
Full control and understanding
Nothing overlooked because the knowledge is known
@green onyx it's dying
its getting raided bruh
Yeah someone is raiding
wdym pinging me
Good luck to admins and mods
the fucl happened
lol

jesus my discord blew up
if the raiding mfs come here to this channel just know nobody loves you and you're a waste of air 
why would someone want to raid a jailbreak server
very nice 🙂
true
hyperstupid.com - im a waste of oxygen
And lock this
@celest basalt server is getting nuked
last message before channel is locked? nopw apparently not 
slow mode pagman
bro what a shit server you should have a commmand to lockdown all the channels at once
a channal that's not locked :d
oh no
a channel that’s not locked????
rangus!!!!!
yes
please block every channel, i dont want anymore pings :((( <@&355145545242902548>

the next dumb fuck that gives people custom perms in these channels
is gonna get slapped
ik
8015 is A11

say for an A13 device
it’ll be
08030-0[ECID]
yes
ECID is in HEX
in the UDID
to hex yes
what error
that’s a TSS request failure
May b
send a screenshot
sounds like an outdated futurerestore version
^
v194 should work because that log isn't even showing it trying to fallback to a newer version
V 194 for A11 throws fdr errors
you can try v204/v205 in the pins but it might not make a difference
And you thought using an older version would fix that?
makes absolutely zero difference
Then solution please guys
Restoring to 14.2?
14.3
sending a log of the FDR errors might help (GUI makes it easy, but you don't have to use it)
v194 is the latest
It stops at a stage that we have to restore the device all over again
Jaikbreak and set nonce
Again
2>./log.txt
ez
FDR?
No it doesn’t
is this a serious question
if it fails after sending filesystem
then big rip
I use dimentio
You probably tried to futurerestore from pwnrecovery lmfao
you need to stay in recovery after checkm8-nonce-setter, if you reboot the nonce will change there IIRC
oh weird
so it wasn't a nonce issue
is checkm8-nonce-setter even supposed to put you in recovery
yes
you run it from pwndfu, then it puts you in pwnrecovery and then normal recovery
After i send iBSS it says i’m in recovery but it looks like i’m still in DFU
i never see the recovery screen
black screen is pwnrecovery, it's supposed to go to normal recovery screen after
after irecovery ––reset?
yeah
never worked for me lol
i was tryna do it manually tho
so maybe it was timing issue
btw I updated the pins to be consistently Cryptic's v204 branch to avoid confusion, but v205 is basically the same
did you update the static to include the 14.5 fix for offsetfinder
should have it I think yes
at least Linux, I don't remember if Cryptic's macOS CI build was before or after
oh someone using it yesterday still had the old version
oh so u mean i should download the linux binary again and try again?
i had the file download from like 3-4 days ago
If it’s updated
ill just try again
lol
it’s fine the webkit is for 14.5.1 as well if you’re worried about that
Lol I have 14.5 onboards
yeah nvm AutoTSS has 14.5 we're good
why does AutoTSS save blobs with two different generators if it doesn't even use the standard generators 
What's autotss
Found device in Normal mode
Entering recovery mode...
ERROR: Unable to place device in recovery mode
futurerestore: failed with exception:
[exception]:
what=Unable to place device into recovery mode from Normal mode
code=10027025
line=153
file=futurerestore.cpp
commit count=204:
commit sha =bdcd10c028f994989011ec3e52ef93f1afce5613:
I thought this was fixed 
yeah but I'm compiling with latest libirecovery
even ideviceenterrecovery doesnt wotk
so in theory it should work?
Lol it doesn’t work for me even on latest
Checkra1n does but futurerestore doesn’t
I even ran idevicepair pair and FR still can't enter recovery... actually I guess it's using different pairing records
Probably
will just do it manually
nop same error
iBoot64Patch: Failed getting sigpatches!
Cleaning up...
[exception]:
what=assure failed
code=24903695
line=380
file=libipatcher.cpp
what version are you restoring to
nyuszika I have a pi with tsssaver for automatically saving blobs but do I need to update tsssaver manually to support newer firmwares?
How did I receive a call on a device that doesn’t even have a SIM wtf
im trying pwndfu from latest to 13.6 with the onboard blobs i saved
if you mean tsschecker then no you don't
Won’t work to 13.6
baseband incompat
Yeah it's tss checker thanks 😊
no its the wifi ipad
I have these settings
maybe offsets are broken for wifi ipads
if that is the latest version
@pseudo stump can you try to an iOS 14 version
Just as a test
idh any other onboard blobs for 14
even IPSW blobs work to test pwndfu
oh ok
oops
what would pwndfu need to patch then
if it’s IPSW already
I think it could patch update blobs to be restore or vice versa
but there's also just the freshnonce patch which takes care of setting the generator for you
like checkm8-nonce-setter
oh true
and bootargs patch to have verbose/serial restore
re-restoring?
nah just downgrading from 14.7 beta bc some tweaks are buggy
going to 14.5 with -u should in theory work
but it's past sending filesystems now so too late
just gonna go back to 14.7 to get my iCloud backup back and then -u ig
is it possible to tick both -u and pwndfu?
in theory yes but with OTA blobs it didn't accept it for me
with IPSW blobs it might
since those usually have both restore and update
that seems fine 🤔
wrong nonce tho
this is the script
i edited it a lot
oh wait what theres no sending ibss there
nvm
i don't need ibec just ibss right
gm
-_- you guys were so intent on blaming divise lol
Oh gm lol
Because ramiel always failed
iCloud probably
oh I think I know how to fix entering recovery on 14.5 for FR
the idevicerestore submodule needs to be updated, not libirecovery
ok back to 14.7
me when I'm indecisive and downgrade/upgrade between iOS versions every week
this wouldn't be an issue if I could go back to 14.3 
trying to downgrade from 14.7 to 14.5 but I forgot -u and I only have an iCloud backup
yes but they're OTA and pwndfu is broken
istg entering pwndfu only works once a day for me
i do it successfully once but i can never do it again
istg ryzen lol
Is ryzen a processor
Too many names
omg why does checkra1n crash after entering recovery
then when i open it again it wants me to go back to normal
are you using the static binary from the website
[exception]:
what=signing ticket file does not contain generator. But a generator is required for 64-bit pwnDFU restore
what the hell is this
i tried 2 diff blobs and i get the same error
lol
Do the blobs have a generator
bruh
Any tool to put idevice in recovery mode on Mac
AutoTSS only saves restore blobs
No but do the blobs actually have a generator key

LOL
libimobiledevice is probably easiest
!t libimobiledevice
Up to date libimobiledevice builds:
Windows: https://github.com/libimobiledevice-win32/imobiledevice-net/releases
macOS: brew install --HEAD libimobiledevice libirecovery
Linux: https://cadoth.net/~nyuszika7h/libimobiledevice-static-linux.tar.gz
im using apt version
oh i got that error cause i ticked -u too
now i got this
[exception]:
what=Device did not reconnect. Possibly invalid iBEC. Reset device and try again
code=35979281
well, it kinda works
bruh ipwndfu really only works once a day smh
nice
Thank you lol I was doing some stupid
ideviceenterrecovery $(idevice_id | ggrep -Po '.*(?= \(USB\))')
confirmed both AutoTSS blobs are restore only 
your mom
tsschecker saves both by default
when restoring to ios 13 u get the sigpatches error
why would they make it specifically restore only
i just tried some ios 14 restore and it got tru
tell us if the restore actually finishes
lol
btw instead of telling everyone to go to bios and select the usb stick for odysseyn1x
3 times the same error now
why dont we just tell them to boot the USB from Windows RE
wow lmao
just hold shift and press reboot
that’s way easier imo
wtf I think futurerestore is just broken
my 14.5.1 blob has an updateInstall field but it says "apticket can't be used for this restore"
AutoTSS blob has updateInstall too
are you going to discover what google is on the day of judgement
yep i think i have a cap on how many times i can use ipwndfu a day
bro ive tried everything
literally only works the first time i try it
just do a restore at this point lol
...
ugh why did i get ryzen
gonna buy an intel pc now
oof if i didnt take apart my hp stream i couldve used that
nc logic
I fixed it
yeah i give up too
the problem was @shy magnet's version of img4tool fucking things up
this annoys me lmaoo
ill just wait 4 more fixes ih
ig
@celest basalt what libusb version do you have on your linux install
theres 1.0-0 and 0.1-4
libusb-0.1-4/hirsute,now 2:0.1.12-32build1 amd64 [installed,automatic]
libusb-1.0-0/hirsute,now 2:1.0.24-3 amd64 [installed,automatic]
@shy magnet this commit https://github.com/m1stadev/img4tool/commit/b0572e90b820c5db8b0bbc30457d2358a5b025fe breaks updateInstall blobs btw
because it just always picks restore and then passes that on to FR
doesn't try to fallback to update
and FR just errors out on the mismatch
Just realised my 6s is not gonna be included in iOS 15
So sep/bb gonna be compat forever
tss saver back up wahey
back to 14.5 now
wait how did pwndfu work
oh
so OTA can get both RC and the next beta now, nice
I thought this feature was only on 14.6+
14.5+
use latest sep and latest baseband
wget doesn’t support extracting zip archives
you can use pzb
pzb -g Firmware/all_flash/sep-firmware-[config].im4p [URL]
for BuildManifests just cut off the last part of the URL and add BuildManifest.plist
works on 10 or 11+
bruh
you can't be this stupid
that's like saying "zsh doesn't have futurerestore"
it doesn't matter what shell you use, you have to install it separately
lol idk i told him this before
why is staff so rude in this server
@celest basalt this person is a geniusses tm
basically staf
r/ihadastroke
oh LMAO
I could probably just say "2.00" and list every update between release and 2.0
Haha the effort would be way too much just for making it look nice for one platform
Gm
gm
Gm
What level is dabezt now? 70?
meh, actually gonna go back to 14.4 again
bruh
Why
because I want to be on the lowest version for whatever drops in the future
upgrading is less painful than downgrading
since you can't downgrade from 14.5+ without data loss
might go back to ReProvision once my dev acc expires in September bc I need to save money 
Has anyone been successful with futurerestore with 14.5.1 ? I've got an iphone 6s+ and trying to go to 14.3. Nothing happens after FDR errors after hours of waiting, so I usually abort and try again with no luck.
good to be on 14.4 for that too bc it's broken on 14.5+ atm (though AltStore/AltDaemon works)
Oh, I'd have to try FR again later for that
probably using an old version of fr
nope. v194
i've tried the GUI and the manual method. both fail on me. I'll provide errors later when I can
is this channel muted for whitenames 
doesn't seem to be
it should be
this channel is just chill
since when was there a m1sta and snowball role
and a cryptic role
or is that individual perms
the raiders last time seemed to spam one channel, then go down one, then keep doing that

the dumbest shit is that this server is a discord partner
14.5+
this botter has the biggest balls
The webkit jb doesn’t work on 14.5-
yes
bruh
yep
gaming
yay
gaming
streaming gaming
no eta, be patient
no eta, be patient
no eta, be patient
- Im sure you know im gonna say thats not on topic.
- How would it know the context of the user saying the words?
mm the issue does specifically mention !t blobs so it does have a link to futurerestore lol
what if they say "is there a bypass for icloud" lol
Okay but if I say the same thing in a different way with more words how would it know if im asking or informing
I think tags suffice, its not like theres a time where there no users around who cant just type the tag quickly for anyone who needs it
Most times theres multiple people typing it
I doubt an auto message would alleviate that any
Well heres the thing, bot commands are supposed to be used in #bot-commands , if they were it would never be unnoticed. The fact that we allow them in other channels is just because people are lazy
yeah it'd be dumb to tell people "go run !t blobs in #bot-commands" lol
imo that’s dumb
I didnt say it was perfect, and as we all realized that, we dont have it that way do we?
yeah, but the fact you’re saying that “we allow them in other channels is just because people are lazy” is kinda dumb
^
Then in the same sense youre saying having Bot commands in the first place is dumb
Its what the channel is for
I think we allow them in other channels because that's their purpose lol
no lol, !adddevice shouldn't be used outside of bot commands
Tags are fine in channels
stuff like !t Odyssey for example are perfectly fine in channels imo
Do we not allow both in all channels except general?
Odysseyra1n is a modification for checkra1n which replaces the bootstrap with Procursus, the package manager with Sileo and the tweak injector with libhooker. This has benefits such as speed, battery life and security.
Tutorials:
macOS/Linux
Windows
Alternative installation method: Shortcut
Theres many of those that are useless and could be condense or combined
Lol
no !Xp shouldnt be used outside of bot cmds lol
Yes
wow three specific cases, wanna see how many more I can find?
@lilac wren why would we need those in normal channels tho
#general is for off-topic discussion. Please keep all jailbreak-related discussion in #jailbreak.
oh
gm
gm
I dont understand your point at all then , because my point was we dont need them
@full osprey what tags should be locked behind #bot-commands or combined
gm
tags are useful in channels
only commands that should be able to be used outside of frhelp is tags tbh
not because people are lazy
I never said any should, I said bot commands was made for bot commands
it's their intended purpose
I mean your initial point was quite literally tags should only be used in #bot-commands
which is uh
but also i am stepping into this convo without knowing any context

so
^
yeah questionable point lol
@stiff hazel No my point was instead of adding another way of helping users see a message, use the command in bot commands and it wouldnt be missed
Is that not what you said happens initially?
trust me I will go a day intentionally not using tags and we will see how that ends up working out

Personally I could care less
the farthest I'd go I think is have:
- GIR can DM the user with the tag it thinks is right for their question (and react on their message with 📬) and say "i think this can help" or something like that
- User can opt out with one reaction on that DM
Looking at the tag list I can see which are being used and are not, that was never my argument lol
And I never said the current ways are perfect, all I said is adding what was suggested would also be unnoticed
Then I’d ping those 6 people at the same time and get muted probably for mass pinging
yeah that's why I like the DM idea, users can see GIR answered the question bc of the 📬, + people can just ignore the question instead of cluttering the chat with !t jb or whatever
I sensed JTV being shown
How is the bot mentioning the user different from someone else pinging the user?
Lol
People ignore pings daily
nothing badly is happening here please go to your tv home
i guess no-one wants me here

Ive legit had people tell me they didnt know something was piracy after being warned when they get pinged and a dm
My point
let’s just warn them with the tag content as the reason
imagine stealing so much that it becomes habit and you forget what stealing is
People are gonna ignore what they want, and pay attention to what they want. No matter who or where it comes from
there’s a difference between trying and them still ignoring you and just not even trying and getting ignored
I mean, im just throwing out my thoughts. Hell if you feel strongly enough mention it to slim more
The former is usually out of lack of giving a shit on the side of the person pinged, the latter is usually the fault of both
factual
maybe some could be combined, but some are split because it would be a mess to try to fit the whole thing into one tag (like blobs and onboardblobs, and I also split out rootfs and rootfscli)
LOL
Dont get me wrong, I understand. Which is why I stopped bitching about it as much.
14.6 is likely to release tomorrow
wow look an iOS release that seems fine
oh bye jtv




